
steve.neal
I'm not sure if this normal or not but its always happened to me, whenever I first run the initiation script, the motors with encoders, (radar & waist), both running with Sabertooth/kangaroos, need to "home" to the limit switch so the motors know their position, but one or both don't start "homing". They just sit there. I then stop the script and restart it and the second time they will home. Everything else in the script will run each time I start it, It's just the motors with encoders. Does anybody else have this problem?
Also, I have two EZBs. Most times I need to scan for their address so I can select them and the Init script can connect them. Nearly every time, (from one day to the next) the addresses are different from the last time I connected them. Is there a way to fix this as well?
Steve
I know you have been using Sabertooth motor controllers for some time now, do you have any thoughts on the encoder homing problem or ever experienced something similar?
I home several encoders for Roos in my int scrip for my b9. Download my latest project from the cloud and have a look. Maybe you'll see something that helps. Post your project so we can take a look.
I had a read of your Init script, awesome by the way, and I'm fairly certain that my issue is, as you suggested, not enough sleep before the motors try homing, I will re-wright my script and see if that works
Thanks Dave
The new Init script with more sleep worked perfectly. I basically copied yours and modified to suit my configuration and omitted the stuff I don't have yet, Like arms
Works first time, every time.
Thanks Dave.
Did you get your connection issues fixed yet with the rolling IP address and having to rescan all the time? I hope Richard's suggestion helped.