Asked
— Edited
Hi guys,
I am currently trying to use a sabertooth 2x32 but am unable to get it to work and think it might be related the the DIP switches?
just for background: -I have updated to the latest ARC -the signal and ground of D0 are connected to s1 and ground of the sabertooth -i have tried using both the sabertooth Movement Panel and custom Movement Panel using serial commands and have read how the interval 0-255 affects the motor coding. -I have tried many combinations of DIP switches but I either get the motors spinning out of control (without command from the movement panel) or no movement at all
I am sure that it is something simple and figured someone has come across this in the past
Thank you for any input possible!
Aaron
ok... it has been a long day... but I finally got it to work! I had the exact same code that @bhouston had written except for the braud rate of 9600. I changed the braud rate and re-configured the DIP switches to what I would have expected them to be and now it works perfectly!
thank you to everyone that helped me out it was really appreciated
Aaron
Good deal, glad to see you got it working.
Wow robot 56 very nice I like your robot
So, you got it to work by changing the baud rate and dip switches. It’s not clear to what you changed them to. Could you please tell us?
@Dave Schulpius sorry i was just excited to see it move. i used a custom Movement Panel with the code changed to a 9600 braud rate.
the DIP switches I used was:
1-4 off 5-6 on
Just a curious question what determines the braud rate I was looking at the data sheet and it said nothing about that braud rate that I could find it was a quick glance if memory serves me right Richard R and BHouston have the same board and I believe Richard R is set to 38400 I'm just curious what determines that thanks
I don't know what determines to Baud Rate but I was having trouble with a motor not starting when it should and not shutting off when it should. It was totally random and effected both motors. It was suggested by Richard to change the Baud rate from 38400 to 9600 and it fixed things up. I don't know if this is a coincidence or not but I had been running the EZB that controls the motors in AP mode and it seemed like my problems started when I started running the EZB in Client Mode.
@BHouston, thanks for the edit** explanation, I am going to change mine to 9600 too, because mine seems to do that every once in a while too. Again thanks for the explanation .
@robot56, didn't mean to hijack your thread, is there a way you can get more lighting on your video your R2-D2? is very cool thanks