H.Berserk
Hi everyone, I have been following you for some time and first of all I wanted to thank this forum and the fantastic Ez Robot because you have allowed me to learn many things. I started building a hexapod around an ez board v4 and I played a bit with AutoPosition but I have a strange problem with the speed of the servos. When I turn on the ez board v4 for the first time I have to turn on the PC camera even for a second and then turn it off otherwise the movements are slow, I don't understand why I didn't set anything in the camera device. I tried to turn on the ez camera instead of the camera pc but the movements remain slow. Same problem with the mobile app. I thought of resetting all the movements without ever turning on the pc camera, but maybe I'm missing something? I inserted a video that maybe will explain better than my English "google".
Here's a build with ability to enable the variable speed modifier on any frame in any action: https://synthiam.com/Software/Release/Beta-Release-2019-04-11-00-17981
Dj Sures, i don't know what to say.. Less than 24 hours to release the new build!! You awesome! cool
Excuse me again. I need clarification with fast movement modifiers. For example if I create an action with these values:
When the setSpeed value is 255 I should have 10delay 5steps 1speed, but unfortunately the + 3steps of the fast movement modifiers are not added, and the result is 10delay 2step. Does anyone have the same problem as me?
I'll take a look this weekend and see if there's anything outstanding. Far as i know the calculated values are correct because there hasn't been a report otherwise.
in fact I imagined I only had this problem because I use lewansoul servos "for now" but finally "robotshop europe" has recently put ezrobot servo hd on sale .. so as soon as I can buy 18 i make the leap in quality! cool
That'll be a big difference for sure. The LewanSoul servos aren't that great - they had potential when you read the documentation and promotion, but the final product in practical application ends up disappointing. Mostly the challenge with software and hardware is real-world vs software. What we write in code has to interact with a real world, and there's a ton of physics involved dealing from power, heat, weight, gearing, etc... and that's just for motors, not including sensor data.
So moving things in the real world can sometimes be tricky, but we're working on that