Welcome to Synthiam!

The easiest way to program the most powerful robots. Use technologies by leading industry experts. ARC is a free-to-use robot programming software that makes servo automation, computer vision, autonomous navigation, and artificial intelligence easy.

Get Started
Asked — Edited
Resolved Resolved by Rich!

Movement Scripting Help Please?≫

Can anyone help with scripting? I need to be able to have the speed of the G-Bot be ramped up and down rather than full on/off or there is a serious risk it will topple.
Right now I have the sabertooth control set up as in the attached photo. I have joystick 1 of the joystick control controlling it but I only get full on or off or full clockwise or counterclockwise rotation. Also, the joystick is 90 degrees off what I'd like( '3 o'clock' = forward, '9 o'clock' = reverse, '12 o'clock' = clockwise in place, '6 o'clock' = counterclockwise in place - but I can live with that for now if I have too).
I've been reading and watching tutorials and it seems like the movement scripting control is designed to do this but the input lines are different between the movement script control and the sabertooth control(stop, forward, reverse, left right versus 'left forward', 'right forward', 'left turn left', 'right turn left', 'left turn right', 'right turn right', 'left reverse', 'right reverse') and I have no idea how to write a script command to appropriately include a variable to do what I'm trying to do (OMG, that high school curse had come true! It comes down to algebra! doesn't it? Oh noooo!)
Can anyone take mercy on us and our Halloween plans and suggest some script to try and tell me which lines should go where?

PLEASE, PLEASE, PLEASE?

Thank you, Gwen
User-inserted image


ARC Pro

Upgrade to ARC Pro

Harnessing the power of ARC Pro, your robot can be more than just a simple automated machine.

AI Support Bot
Related Content
Synthiam
Based on your post activity, we found some content that may be interesting to you. Explore these other tutorials and community conversations.
PRO
Synthiam
#1  
There is no support for sabertooth speed ramping - I will have to add that.

I'll add it to the list:)
#2  
OMG! DJ... Is that something that could happen quickly? How long is your list?

If not, is there a work around? Can I use another control to control the sabertooth that might support ramping?
PRO
Synthiam
#3  
There are a little over 300 items in the list. The priority of each item depends on what section of the code i'm working on
#4  
You can achieve a type of ramping (I think I mentioned this before) if you use serial commands (to the sabertooth) and the custom Movement Panel instead of the pre defined sabertooth movement panel... Or you can just use it in any script to achieve your ramping with a joystick... You assign variables to use as speed of your sabertooth... These variables can be easily change on the fly to simulate ramping... When using the custom Movement Panel write your code in the scripts available behind the forward, left, right and reverse command in the control...

something like below is serial commands to tell the sabertooth to move forward (depending on your motor wiring... loop this a few times changing the variable values will give you your ramping to some extent

Code:


$leftMotorSpeed=35 #about 50% power 63 is stop
$rightMotorSpeed=227 #about 50% power 192 is stop


SendSerial(D23,38400,$leftMotorSpeed) #any value from 1 to 127 = left motor
SendSerial(D23,38400,$rightMotorSpeed # any value from 128 to 255 = Right motor


Changing the values of $leftMotorSpeed and $rightMotorSpeed) will either slow, speed up or reverse the corresponding motor...
United Kingdom
#5  
As Richard has pointed out, the values will affect the speed of the motors.

I posted a quick example of a ramping script a while ago, I've no idea what topic it was in though and it's probably quicker if I throw up another quick example of how to gradually increase or decrease a variable...

As always, this is an example so will need to be tailored to your project and probably used as part of a larger script.

Code:


# Speed ramp forwards direction of motor 1 (left) from slow to full speed
$startspeed = 65 # Check this value - I do not have a sabertooth to try it with
$endspeed = 1
$speedsteps = 1 # Change this to change the ramping speed

# Set up the variable for the serial command
$newspeed = $startspeed

# Looping code to gradually increase the speed
RepeatUntil($newspeed = $endspeed)

# Send the command to the sabertooth
SendSerial(D23,38400,$newspeed)

# Increase the speed by 1
$newspeed = $newspeed - $speedsteps

# Reduce load on CPU
Sleep(100)

# Loop back
EndRepeatUntil

# Speed should now be at $endspeed and script will stop


I haven't tested it and it was written straight in to the forum so there may be some syntax errors (there shouldn't be but there may be).

You could take the first 3 variables out of this script and save the script as a ramping control script triggered by ControlCommand() from another script. Have the script which triggers this one set the start speed, end speed and speed steps and it'll save you having to rewrite it over and over if you need ramping for other actions.

If that last paragraph doesn't make sense I'll knock up a quick Example Project which would explain it clearer, just ask.

Hope that's of some help:)
#6  
Hi Rich, Thanks for your response. I'm sure this is my work around and I know you did mention this before. I guess I just don't know enough about the syntax of the scripting to manipulate it with any skill.

Is anything after # a comment?

I have the script manual but it doesn't seem to include a primer or rules on syntax. I am unsure how to loop etc. Do I separate commands with commas? Do successive commands need to be on separate lines? Is there a 'loop' command etc?

I will experiment with this as I'm sure its my best option to get something going soon.

Is there anything like a scripting primer?

Thanks so much for giving me something to work with anyway!

Gwen
#7  
@Rich... LOL...It's funny. I can usually get most of my coding to achieve the same results as you do (I mean with a little thought and some time on my part). However, my code still ends up being clunkier (not a word, I know) and bloated compared to yours dude...:P

@Gwen yes, the # is a comment out marker same as // is to C
United Kingdom
#8  
Yes anything with a # is a comment (put there to explain what each part does so you can understand it and follow it).

The loop is the RepeatUntil() part and ends at the EndRepeatUntil. If you wanted a constant, forever loop you could use a :label and Goto() to achieve this or set a RepeatUntil() to have an impossible statement i.e. RepeatUntil(1>2)

You don't need to change much in my example I posted (however refresh the page as I noticed I made a mistake and had the code incrementing from 65 to 127 not decreasing from 65 to 1). Just the start point, end point and number of steps per loop of the code.

To move the other direction the script will need modification as far as the following goes;

Code:

# Increase the speed by 1
$newspeed = $newspeed - $speedsteps


To increase in reverse (for motor 1) it needs to add $speedsteps to $newspeed not subtract it so change the - to a +

Motor 2 works the other way... the Sabertooth likes to get confusing to follow:)

As for separating commands. They are separated on a new line. The scripts run stupidly fast (like thousands of lines of code per second) so if you set one line to move motor 1 then another to move motor 2 both would appear to move at the same time, the delay in starting is so small it's not worth even trying to think about.

What's a "scripting primer"? (I guess that means no lol)
United Kingdom
#9  
@Richard, you haven't seen some of my scripts! Some are very bloated and clunky. I'll often rewrite them with simpler methods after I first write them and take a look at what's written (I kind of auto pilot when writing scripts). Just look at my PingRoam examples and even the topic where I posted my methods of improving it:)
#10  
Awesome guys! Thanks. I'll be working on this tonight and tomorrow. I'l post when I get it working.
PRO
Synthiam
#11  
Gwen, there is also a folder included in your ARC installation called "EXAMPLES".

1) Load ARC

2) Press the OPEN button from the project tab under FILE

3) Press the EXAMPLES button

4) Select either EZ-Script Examples or EZ-Script Function Syntax

EZ-Script Function Syntax: This is a folder with examples of every EZ-Script function. For example, if you search for the word repeat in this folder, you will find an example that shows how to use repeat

EZ-Script Examples: This is a folder with examples on how to write code to perform some things. As well as demonstrating some syntax, this folder is more "functional" examples than syntax examples.

Additionally, the EZ-Script Examples Lesson will be of use to you. Here is the link: http://www.ez-robot.com/Tutorials/Lesson/22
#12  
Ok, I've been experimenting with trying to get my sabertooth to ramp up and down in speed with linited success. Here is the code I came up with that makes my robot slowly accelerat forward:

Code:


# Speed ramp forward direction of Robot from slow to full speed
SendSerial(D7,38400,65)
SendSerial(D7,38400,191)
SLEEP(20)
SendSerial(D7,38400,66)
SendSerial(D7,38400,190)
SLEEP(20)
SendSerial(D7,38400,67)
SendSerial(D7,38400,189)
SLEEP(20)
SendSerial(D7,38400,68)
SendSerial(D7,38400,188)
SLEEP(20)
SendSerial(D7,38400,69)
SendSerial(D7,38400,187)
SLEEP(20)
SendSerial(D7,38400,70)
SendSerial(D7,38400,186)
SLEEP(20)
SendSerial(D7,38400,71)
SendSerial(D7,38400,185)
SLEEP(20)
SendSerial(D7,38400,72)
SendSerial(D7,38400,184)
SLEEP(20)
SendSerial(D7,38400,73)
SendSerial(D7,38400,183)
SLEEP(20)
SendSerial(D7,38400,74)
SendSerial(D7,38400,182)
SLEEP(20)
SendSerial(D7,38400,75)
SendSerial(D7,38400,181)
SLEEP(20)
SendSerial(D7,38400,76)
SendSerial(D7,38400,180)
SLEEP(20)
SendSerial(D7,38400,77)
SendSerial(D7,38400,179)
SLEEP(20)
SendSerial(D7,38400,78)
SendSerial(D7,38400,178)
SLEEP(20)
SendSerial(D7,38400,79)
SendSerial(D7,38400,177)
SLEEP(20)
SendSerial(D7,38400,80)
SendSerial(D7,38400,176)
SLEEP(20)
SendSerial(D7,38400,81)
SendSerial(D7,38400,175)
SLEEP(20)
SendSerial(D7,38400,82)
SendSerial(D7,38400,174)
SLEEP(20)
SendSerial(D7,38400,83)
SendSerial(D7,38400,173)
SLEEP(20)
SendSerial(D7,38400,84)
SendSerial(D7,38400,172)
SLEEP(20)
SendSerial(D7,38400,85)
SendSerial(D7,38400,171)
SLEEP(20)
SendSerial(D7,38400,86)
SendSerial(D7,38400,170)
SLEEP(20)
SendSerial(D7,38400,87)
SendSerial(D7,38400,169)
SLEEP(20)
SendSerial(D7,38400,88)
SendSerial(D7,38400,168)
SLEEP(20)
SendSerial(D7,38400,89)
SendSerial(D7,38400,167)
SLEEP(20)
SendSerial(D7,38400,90)
SendSerial(D7,38400,166)
SLEEP(20)
SendSerial(D7,38400,91)
SendSerial(D7,38400,165)
SLEEP(20)
SendSerial(D7,38400,92)
SendSerial(D7,38400,164)
SLEEP(20)
SendSerial(D7,38400,93)
SendSerial(D7,38400,163)
SLEEP(20)
SendSerial(D7,38400,94)
SendSerial(D7,38400,162)
SLEEP(20)
SendSerial(D7,38400,95)
SendSerial(D7,38400,161)
SLEEP(20)
SendSerial(D7,38400,96)
SendSerial(D7,38400,160)
SLEEP(20)
SendSerial(D7,38400,97)
SendSerial(D7,38400,159)
SLEEP(20)
SendSerial(D7,38400,98)
SendSerial(D7,38400,158)
SLEEP(20)
SendSerial(D7,38400,99)
SendSerial(D7,38400,157)
SLEEP(20)
SendSerial(D7,38400,100)
SendSerial(D7,38400,156)
SLEEP(20)
SendSerial(D7,38400,101)
SendSerial(D7,38400,155)
SLEEP(20)
SendSerial(D7,38400,102)
SendSerial(D7,38400,154)
SLEEP(20)
SendSerial(D7,38400,103)
SendSerial(D7,38400,153)
SLEEP(20)
SendSerial(D7,38400,104)
SendSerial(D7,38400,152)
SLEEP(20)
SendSerial(D7,38400,105)
SendSerial(D7,38400,151)
SLEEP(20)
SendSerial(D7,38400,106)
SendSerial(D7,38400,150)
SLEEP(20)
SendSerial(D7,38400,107)
SendSerial(D7,38400,149)
SLEEP(20)
SendSerial(D7,38400,108)
SendSerial(D7,38400,148)
SLEEP(20)
SendSerial(D7,38400,109)
SendSerial(D7,38400,147)
SLEEP(20)
SendSerial(D7,38400,110)
SendSerial(D7,38400,146)
SLEEP(20)
SendSerial(D7,38400,111)
SendSerial(D7,38400,145)
SLEEP(20)
SendSerial(D7,38400,112)
SendSerial(D7,38400,144)
SLEEP(20)
SendSerial(D7,38400,113)
SendSerial(D7,38400,143)
SLEEP(20)
SendSerial(D7,38400,114)
SendSerial(D7,38400,142)
SLEEP(20)
SendSerial(D7,38400,115)
SendSerial(D7,38400,141)
SLEEP(20)
SendSerial(D7,38400,116)
SendSerial(D7,38400,140)
SLEEP(20)
SendSerial(D7,38400,117)
SendSerial(D7,38400,139)
SLEEP(20)
SendSerial(D7,38400,118)
SendSerial(D7,38400,138)
SLEEP(20)
SendSerial(D7,38400,119)
SendSerial(D7,38400,137)
SLEEP(20)
SendSerial(D7,38400,120)
SendSerial(D7,38400,136)
SLEEP(20)
SendSerial(D7,38400,121)
SendSerial(D7,38400,135)
SLEEP(20)
SendSerial(D7,38400,122)
SendSerial(D7,38400,134)
SLEEP(20)
SendSerial(D7,38400,123)
SendSerial(D7,38400,133)
SLEEP(20)
SendSerial(D7,38400,124)
SendSerial(D7,38400,132)
SLEEP(20)
SendSerial(D7,38400,125)
SendSerial(D7,38400,131)
SLEEP(20)
SendSerial(D7,38400,126)
SendSerial(D7,38400,130)
SLEEP(20)
SendSerial(D7,38400,127)
SendSerial(D7,38400,129)
SLEEP(20)
SendSerial(D7,38400,128)


And here is the code that makes my robot slowly accelerate in reverse:

Code:


# Speed ramp Reverse direction of Robot from slow to full speed
SendSerial(D7,38400,63)
SendSerial(D7,38400,193)
SLEEP(20)
SendSerial(D7,38400,62)
SendSerial(D7,38400,194)
SLEEP(20)
SendSerial(D7,38400,61)
SendSerial(D7,38400,195)
SLEEP(20)
SendSerial(D7,38400,60)
SendSerial(D7,38400,196)
SLEEP(20)
SendSerial(D7,38400,59)
SendSerial(D7,38400,197)
SLEEP(20)
SendSerial(D7,38400,58)
SendSerial(D7,38400,198)
SLEEP(20)
SendSerial(D7,38400,57)
SendSerial(D7,38400,199)
SLEEP(20)
SendSerial(D7,38400,56)
SendSerial(D7,38400,200)
SLEEP(20)
SendSerial(D7,38400,55)
SendSerial(D7,38400,201)
SLEEP(20)
SendSerial(D7,38400,54)
SendSerial(D7,38400,202)
SLEEP(20)
SendSerial(D7,38400,53)
SendSerial(D7,38400,203)
SLEEP(20)
SendSerial(D7,38400,52)
SendSerial(D7,38400,204)
SLEEP(20)
SendSerial(D7,38400,51)
SendSerial(D7,38400,205)
SLEEP(20)
SendSerial(D7,38400,50)
SendSerial(D7,38400,206)
SLEEP(20)
SendSerial(D7,38400,49)
SendSerial(D7,38400,207)
SLEEP(20)
SendSerial(D7,38400,48)
SendSerial(D7,38400,208)
SLEEP(20)
SendSerial(D7,38400,47)
SendSerial(D7,38400,209)
SLEEP(20)
SendSerial(D7,38400,46)
SendSerial(D7,38400,210)
SLEEP(20)
SendSerial(D7,38400,45)
SendSerial(D7,38400,211)
SLEEP(20)
SendSerial(D7,38400,44)
SendSerial(D7,38400,212)
SLEEP(20)
SendSerial(D7,38400,43)
SendSerial(D7,38400,213)
SLEEP(20)
SendSerial(D7,38400,42)
SendSerial(D7,38400,214)
SLEEP(20)
SendSerial(D7,38400,41)
SendSerial(D7,38400,215)
SLEEP(20)
SendSerial(D7,38400,40)
SendSerial(D7,38400,216)
SLEEP(20)
SendSerial(D7,38400,39)
SendSerial(D7,38400,217)
SLEEP(20)
SendSerial(D7,38400,38)
SendSerial(D7,38400,218)
SLEEP(20)
SendSerial(D7,38400,37)
SendSerial(D7,38400,219)
SLEEP(20)
SendSerial(D7,38400,36)
SendSerial(D7,38400,220)
SLEEP(20)
SendSerial(D7,38400,35)
SendSerial(D7,38400,221)
SLEEP(20)
SendSerial(D7,38400,34)
SendSerial(D7,38400,222)
SLEEP(20)
SendSerial(D7,38400,33)
SendSerial(D7,38400,223)
SLEEP(20)
SendSerial(D7,38400,32)
SendSerial(D7,38400,224)
SLEEP(20)
SendSerial(D7,38400,31)
SendSerial(D7,38400,225)
SLEEP(20)
SendSerial(D7,38400,30)
SendSerial(D7,38400,226)
SLEEP(20)
SendSerial(D7,38400,29)
SendSerial(D7,38400,227)
SLEEP(20)
SendSerial(D7,38400,28)
SendSerial(D7,38400,228)
SLEEP(20)
SendSerial(D7,38400,27)
SendSerial(D7,38400,229)
SLEEP(20)
SendSerial(D7,38400,26)
SendSerial(D7,38400,230)
SLEEP(20)
SendSerial(D7,38400,25)
SendSerial(D7,38400,231)
SLEEP(20)
SendSerial(D7,38400,24)
SendSerial(D7,38400,232)
SLEEP(20)
SendSerial(D7,38400,23)
SendSerial(D7,38400,233)
SLEEP(20)
SendSerial(D7,38400,22)
SendSerial(D7,38400,234)
SLEEP(20)
SendSerial(D7,38400,21)
SendSerial(D7,38400,235)
SLEEP(20)
SendSerial(D7,38400,20)
SendSerial(D7,38400,236)
SLEEP(20)
SendSerial(D7,38400,19)
SendSerial(D7,38400,237)
SLEEP(20)
SendSerial(D7,38400,18)
SendSerial(D7,38400,238)
SLEEP(20)
SendSerial(D7,38400,17)
SendSerial(D7,38400,239)
SLEEP(20)
SendSerial(D7,38400,16)
SendSerial(D7,38400,240)
SLEEP(20)
SendSerial(D7,38400,15)
SendSerial(D7,38400,241)
SLEEP(20)
SendSerial(D7,38400,14)
SendSerial(D7,38400,242)
SLEEP(20)
SendSerial(D7,38400,13)
SendSerial(D7,38400,243)
SLEEP(20)
SendSerial(D7,38400,12)
SendSerial(D7,38400,244)
SLEEP(20)
SendSerial(D7,38400,11)
SendSerial(D7,38400,245)
SLEEP(20)
SendSerial(D7,38400,10)
SendSerial(D7,38400,246)
SLEEP(20)
SendSerial(D7,38400,9)
SendSerial(D7,38400,247)
SLEEP(20)
SendSerial(D7,38400,8)
SendSerial(D7,38400,248)
SLEEP(20)
SendSerial(D7,38400,7)
SendSerial(D7,38400,249)
SLEEP(20)
SendSerial(D7,38400,6)
SendSerial(D7,38400,250)
SLEEP(20)
SendSerial(D7,38400,5)
SendSerial(D7,38400,251)
SLEEP(20)
SendSerial(D7,38400,4)
SendSerial(D7,38400,252)
SLEEP(20)
SendSerial(D7,38400,3)
SendSerial(D7,38400,253)
SLEEP(20)
SendSerial(D7,38400,2)
SendSerial(D7,38400,254)
SLEEP(20)
SendSerial(D7,38400,1)
SendSerial(D7,38400,255)


when I insert these sets of code into the movement script in the appropriate 'Forward' and Reverse' boxes, the robot gently accelerates forward and reverse when using the respective onscreen control buttons. but its difficult to control this way.

When I have the joystick control the movement script, the acceleration is nice but there is no way to decelerate. I have to reverse direction which if done from full speed is herky, jerky. There is no way to ramp down. and there is no stop when the joystick is in the middle. It stays on in either direction. The only thing i could think of was to enter a stop command in the stop line of the movement script control

Code:


SendSerial(d7,38400,0)
# 0 is a special case serial command for sabertooth in
# simple serial mode = shutdown both motors


That sure stops the robot. Stops dead from any speed when the joystick hits the middle... Not good.

I figure this is solvable but am pretty sure this would be complicated and way beyond my primitive scripting abilities at this point.

Any suggestions are welcome...
United Kingdom
#13  
You could use scripting and take the joystick Y axis variable to determine the speed.

You'll need to do some calculations, and possibly throw an IF in there to avoid a sudden stop, something like;

Code:


IF($Joystick1Y < 10)
# Ramp down code
EndIF


However this would lose the ability to suddenly stop it if there is a problem, you would need to add an emergency stop command somewhere.


Also, you can greatly reduce the lines of code for ramping with a simple counter and repeat.

This

Code:

# Speed ramp forward direction of Robot from slow to full speed
SendSerial(D7,38400,65)
SendSerial(D7,38400,191)
SLEEP(20)
SendSerial(D7,38400,66)
SendSerial(D7,38400,190)
SLEEP(20)
SendSerial(D7,38400,67)
SendSerial(D7,38400,189)
SLEEP(20)
SendSerial(D7,38400,68)
SendSerial(D7,38400,188)
SLEEP(20)
SendSerial(D7,38400,69)
SendSerial(D7,38400,187)
SLEEP(20)
SendSerial(D7,38400,70)
SendSerial(D7,38400,186)
SLEEP(20)
SendSerial(D7,38400,71)
SendSerial(D7,38400,185)
SLEEP(20)
SendSerial(D7,38400,72)
SendSerial(D7,38400,184)
SLEEP(20)
SendSerial(D7,38400,73)
SendSerial(D7,38400,183)
SLEEP(20)
SendSerial(D7,38400,74)
SendSerial(D7,38400,182)
SLEEP(20)
SendSerial(D7,38400,75)
SendSerial(D7,38400,181)
SLEEP(20)
SendSerial(D7,38400,76)
SendSerial(D7,38400,180)
SLEEP(20)
SendSerial(D7,38400,77)
SendSerial(D7,38400,179)
SLEEP(20)
SendSerial(D7,38400,78)
SendSerial(D7,38400,178)
SLEEP(20)
SendSerial(D7,38400,79)
SendSerial(D7,38400,177)
SLEEP(20)
SendSerial(D7,38400,80)
SendSerial(D7,38400,176)
SLEEP(20)
SendSerial(D7,38400,81)
SendSerial(D7,38400,175)
SLEEP(20)
SendSerial(D7,38400,82)
SendSerial(D7,38400,174)
SLEEP(20)
SendSerial(D7,38400,83)
SendSerial(D7,38400,173)
SLEEP(20)
SendSerial(D7,38400,84)
SendSerial(D7,38400,172)
SLEEP(20)
SendSerial(D7,38400,85)
SendSerial(D7,38400,171)
SLEEP(20)
SendSerial(D7,38400,86)
SendSerial(D7,38400,170)
SLEEP(20)
SendSerial(D7,38400,87)
SendSerial(D7,38400,169)
SLEEP(20)
SendSerial(D7,38400,88)
SendSerial(D7,38400,168)
SLEEP(20)
SendSerial(D7,38400,89)
SendSerial(D7,38400,167)
SLEEP(20)
SendSerial(D7,38400,90)
SendSerial(D7,38400,166)
SLEEP(20)
SendSerial(D7,38400,91)
SendSerial(D7,38400,165)
SLEEP(20)
SendSerial(D7,38400,92)
SendSerial(D7,38400,164)
SLEEP(20)
SendSerial(D7,38400,93)
SendSerial(D7,38400,163)
SLEEP(20)
SendSerial(D7,38400,94)
SendSerial(D7,38400,162)
SLEEP(20)
SendSerial(D7,38400,95)
SendSerial(D7,38400,161)
SLEEP(20)
SendSerial(D7,38400,96)
SendSerial(D7,38400,160)
SLEEP(20)
SendSerial(D7,38400,97)
SendSerial(D7,38400,159)
SLEEP(20)
SendSerial(D7,38400,98)
SendSerial(D7,38400,158)
SLEEP(20)
SendSerial(D7,38400,99)
SendSerial(D7,38400,157)
SLEEP(20)
SendSerial(D7,38400,100)
SendSerial(D7,38400,156)
SLEEP(20)
SendSerial(D7,38400,101)
SendSerial(D7,38400,155)
SLEEP(20)
SendSerial(D7,38400,102)
SendSerial(D7,38400,154)
SLEEP(20)
SendSerial(D7,38400,103)
SendSerial(D7,38400,153)
SLEEP(20)
SendSerial(D7,38400,104)
SendSerial(D7,38400,152)
SLEEP(20)
SendSerial(D7,38400,105)
SendSerial(D7,38400,151)
SLEEP(20)
SendSerial(D7,38400,106)
SendSerial(D7,38400,150)
SLEEP(20)
SendSerial(D7,38400,107)
SendSerial(D7,38400,149)
SLEEP(20)
SendSerial(D7,38400,108)
SendSerial(D7,38400,148)
SLEEP(20)
SendSerial(D7,38400,109)
SendSerial(D7,38400,147)
SLEEP(20)
SendSerial(D7,38400,110)
SendSerial(D7,38400,146)
SLEEP(20)
SendSerial(D7,38400,111)
SendSerial(D7,38400,145)
SLEEP(20)
SendSerial(D7,38400,112)
SendSerial(D7,38400,144)
SLEEP(20)
SendSerial(D7,38400,113)
SendSerial(D7,38400,143)
SLEEP(20)
SendSerial(D7,38400,114)
SendSerial(D7,38400,142)
SLEEP(20)
SendSerial(D7,38400,115)
SendSerial(D7,38400,141)
SLEEP(20)
SendSerial(D7,38400,116)
SendSerial(D7,38400,140)
SLEEP(20)
SendSerial(D7,38400,117)
SendSerial(D7,38400,139)
SLEEP(20)
SendSerial(D7,38400,118)
SendSerial(D7,38400,138)
SLEEP(20)
SendSerial(D7,38400,119)
SendSerial(D7,38400,137)
SLEEP(20)
SendSerial(D7,38400,120)
SendSerial(D7,38400,136)
SLEEP(20)
SendSerial(D7,38400,121)
SendSerial(D7,38400,135)
SLEEP(20)
SendSerial(D7,38400,122)
SendSerial(D7,38400,134)
SLEEP(20)
SendSerial(D7,38400,123)
SendSerial(D7,38400,133)
SLEEP(20)
SendSerial(D7,38400,124)
SendSerial(D7,38400,132)
SLEEP(20)
SendSerial(D7,38400,125)
SendSerial(D7,38400,131)
SLEEP(20)
SendSerial(D7,38400,126)
SendSerial(D7,38400,130)
SLEEP(20)
SendSerial(D7,38400,127)
SendSerial(D7,38400,129)
SLEEP(20)
SendSerial(D7,38400,128)


Becomes something like

Code:


$motor1speed_start = 65
$motor1speed_end = 127
$motor2speed_start = 191
$motor2speed_end = 129

# Work out the direction for steps

IF($motor1speed_start < $motor1speed_end)
$motor1steps = 1
Else
$motor1steps = -1
EndIf

IF($motor2speed_start < $motor2speed_end)
$motor2steps = 1
Else
$motor2steps = -1
EndIf

RepeatUntil($motor1speed = $motor1speed_end AND $motor2speed = $motor2speed_end)
SendSerial(D7,38400,$motor1speed)
SendSerial(D7,38400,$motor2speed)
$motor1speed = $motor1speed + $motor1steps
$motor2speed = $motor2speed + $motor2steps
SLEEP(20)
EndRepeatUntil
#14  
@Rich is on the case! I was just starting to noodle through this. I think you also want to set some global varuables so each script knows what the last was doing. Ie, if you are ramping up forward, set a variable that says you are going forward, so when you center the joystick it starts ramping down from the current forward speed, and the opposite if you are ramping up backwards. Also your rampdown needs a variable that the forward and reverse can see so that you don't have to drop all the way to 0 before starting to move again (and then we need to also use those variables as interupts to stop the current script and take over with the new one so they aren't fighting each other). Not sure yet how this effects turns. I think your left and right need to know current speed and condition as well to know what speed settings to execute.

I think you may want more than one emergency stop button. One that ramps quickly (maybe just sets your speed increment variable higher) and one full stop. With something top heavy like a B9 I would be concerned that a full stop at full speed might tip over, but you still want the ability to full stop for emergencies since it is so heavy and those motors are so strong. Don't want to run over children/pets/etc.

Alan
#15  
OMG, this is going to take hours of experimentation.... Not sure if I'll have enough time before Halloween to get it done... *stress*.

I may just have to control the sabertooth with my Futaba R/C for now. :( Shame...

Any scripting gurus want to write the code for me and help me work it out via Skype today?

I dont have a ton of $ but coud PayPal a small consulting fee ($50)...
United Kingdom
#16  
When I get home I'll throw together a quick project which will demonstrate the whole joystick position to sabertooth speed control idea which you should be able to follow, understand and modify if necessary.

I don't have a sabertooth to test with but I'm confident that it'll work.

No consulting fee required, helping is it's own reward.:)
#17  
That's very nice of you @Rich

Thanks
United Kingdom
#18  
It's what I do, I'm more than happy to help when it comes to writing scripts and solving problems:) However, I do make you work a little bit for it.

Since I don't use a joystick I wasn't aware that you couldn't map scripts to directions and since (at least my joystick) sends the joystick x and y values all over the place when centred (very sensitive I guess) my original plan didn't quite work however, mapped to buttons works, possibly better.

I also don't have a sabertooth to test with. Using the custom graph I think I've got it all around the right way but a real sabertooth test is needed.

I've uploaded an example set of scripts and joystick control with mapped buttons (xbox controller, A and Y are forwards and reverse). You can download it here

What it does is this...
On connection the init script must be run (set up on the connection control in the example project). This defines the motor speed variables. Without it being run it will fail on error as the variables don't exist.

The ramping script is called with control command. See the Test script for examples. However before using ControlCommand() you need to set the desired end speeds. Simply set the $motor1speed_end and $motor2speed_end variables before the control command. For instance, if you wanted to ramp to full speed forwards you would use this code

Code:


$motor1speed_end = 1
$motor2speed_end = 128
ControlCommand("Movement Controls", ScriptStart, "Ramp Speed")


If it's part of a sequence or larger script change ScriptStart to ScriptStartWait to hold the script calling the command until the ramping is complete.

With the joystick buttons similar is done. Set the two speed variables as before and call the ramp speed script to run.

The ramp speed script simply increases or decreases the speed as required based on the current speed. This also means that if you suddenly need to go from forwards to reverse it wont stop quickly but ramp down then back up.

You may want to add in some emergency stop command though, as previously mentioned, just in case as ramping to stop positions may take some time, and in that time you may end up with a robot covered in furniture or a very squashed small child.

I didn't have time to comment the code properly but there isn't much that needs changing. Also it made it more difficult for me to follow when I was putting notes in it. Since it's easier to add these notes after making the script I'll do it now by annotating the main ramp code below


The ramp code is as follows;

Code:


# Script commands for gradual ramping to desired speeds using Sabertooth
# motor controller connected in simple serial mode on port D7 of EZ-B 0

# Author: Rich
# Version: 2014.10.28.00

# Desired speeds set elsewhere. This script is called with ControlCommands

$rampdelay = 20 # Adjust to suit speed increase

# Do not modify beyond this point unless you know what you are doing
# Any changes may cause the script to run incorrectly.

# Work out which direction the values need to go, i.e. increase or decrease
IF ($motor1speed < $motor1speed_end)
$motor1steps = 1
ELSE
$motor1steps = -1
ENDIF

IF ($motor2speed < $motor2speed_end)
$motor2steps = 1
ELSE
$motor2steps = -1
ENDIF


# A repeatuntil will avoid over 350 lines of extra code

# We repeat increasing the speed of the motors until both motors are at the desired speed
REPEATUNTIL($motor1speed = $motor1speed_end AND $motor2speed = $motor2speed_end)

# Send the serial commands to move the motors at the required speed
SendSerial(D7,38400,$motor1speed)
SendSerial(D7,38400,$motor2speed)

# Check if the motors are up to speed, if not increase it (or decrease it) by 1
IF ($motor1speed = $motor1speed_end)
Print("Motor1 Up To Speed")
ELSE
$motor1speed = $motor1speed + $motor1steps
ENDIF
# Increase motor 2's speed if required
IF ($motor2speed = $motor2speed_end)
Print("Motor2 Up To Speed")
ELSE
$motor2speed = $motor2speed + $motor2steps
ENDIF

# Delay a little to reduce cpu load and to smooth out the ramping
SLEEP($rampdelay)
ENDREPEATUNTIL


That's pretty much all there is to it.

Just set the desired speed to ramp to (variables $motor1speed_end and $motor2speed_end)
Run a controlcommand
ARC does the rest and smoothly ramps from the current speed to the desired speed.

Check the sabertooth direction values, I didn't double check them.

Hopefully that's at least enough to copy & paste and get it up and running by halloween. It can be improved though and I'd be happy to revisit it when we both have a little more time.

Ask any questions you have, I'm always around to answer them (except for on the 31st when I'll be busy with my own Halloween stuff)
#19  
@Rich,

To script the joystick positions (as opposed to buttons), you use a custom movement panel, and script the movement directions there. A joystick will automatically drive the Movement Panel directions and center/stop (as will the arrow keys on the keyboard).

Alan
United Kingdom
#20  
Thanks (see I don't know everything :)) I'll update the project file in a bit to use the movement panel, I don't know why I didn't include a Movement Panel to begin with to be honest, too focused on making the script work without any sudden starting and stopping I guess.

Thanks Alan!
United Kingdom
#21  
Looks like I had a major brain fart on that one... I did know about the joystick moving the movement panel, I even unchecked the box for it!..

Project updated on the cloud, also fixed a couple of other things (such as the forward and reverse values) and added in ramping for turning too, however I'd be interested in knowing if the method works...

Also renamed the two graphs (the hard way - sidenote: DJ, any chance of having that in a future update? It would be really handy to know which graph does what)

Same link to the project as before or click here
#22  
I know you are helping... OMG ;)


So I'm trying to sort this out... Your download link opens an .xml file which confuses me greatly. OMG more code. Sorting code from code... Oh my...

I tried to grab the relevant code from it. I will parse it bellow. Can you describe (as explicitly as possible *blush*:D ) please exactly where to place which pieces of code?

Sorry I'm so obtuse with this... Nuclear medicine is easy, this,... isn't.... lol

I could assign the code to the cross joystick Not sure if that's what you call it but the ARCs software see its four deflections as buttons with the possibility of commands being issued when its depressed and when its released) on the game controller.

Code:


# Test ramping up and down

Print("Move forward")
$motor1speed_end = 1
$motor2speed_end = 128

ControlCommand("Movement Controls", ScriptStartWait, "Ramp Speed")

Sleep(1000)

Print("Move reverse")
$motor1speed_end = 129
$motor2speed_end = 255

ControlCommand("Movement Controls", ScriptStartWait, "Ramp Speed")

Sleep(1000)

Print("Stop")
$motor1speed_end = 64
$motor2speed_end = 192

ControlCommand("Movement Controls", ScriptStartWait, "Ramp Speed")

Sleep(1000)

Print("Move forwards")
$motor1speed_end = 1
$motor2speed_end = 128

ControlCommand("Movement Controls", ScriptStartWait, "Ramp Speed")

Sleep(1000)

Print("Stop")
$motor1speed_end = 64
$motor2speed_end = 192

ControlCommand("Movement Controls", ScriptStartWait, "Ramp Speed")

Sleep(1000)

Print("Move reverse")
$motor1speed_end = 129
$motor2speed_end = 255

ControlCommand("Movement Controls", ScriptStartWait, "Ramp Speed")

Sleep(1000)

Print("Stop")
$motor1speed_end = 64
$motor2speed_end = 192

ControlCommand("Movement Controls", ScriptStartWait, "Ramp Speed")

Sleep(1000)


Code:


# Script commands for gradual ramping to desired speeds using Sabertooth
# motor controller connected in simple serial mode on port D7 of EZ-B 0

# Author: Rich
# Version: 2014.10.28.00

# Desired speeds set elsewhere. This script is called with ControlCommands

$rampdelay = 20 # Adjust to suit speed increase

# Do not modify beyond this point unless you know what you are doing
# Any changes may cause the script to run incorrectly.

IF ($motor1speed < $motor1speed_end)
$motor1steps = 1
ELSE
$motor1steps = -1
ENDIF

IF ($motor2speed < $motor2speed_end)
$motor2steps = 1
ELSE
$motor2steps = -1
ENDIF

REPEATUNTIL($motor1speed = $motor1speed_end AND $motor2speed = $motor2speed_end)
SendSerial(D7,38400,$motor1speed)
SendSerial(D7,38400,$motor2speed)
IF ($motor1speed = $motor1speed_end)
Print("Motor1 Up To Speed")
ELSE
$motor1speed = $motor1speed + $motor1steps
ENDIF
# Increase motor 2's speed if required
IF ($motor2speed = $motor2speed_end)
Print("Motor2 Up To Speed")
ELSE
$motor2speed = $motor2speed + $motor2steps
ENDIF

SLEEP($rampdelay)
ENDREPEATUNTIL


Code:


JoystickScriptsDown><string>$motor1speed_end = 1
$motor2speed_end = 128
ControlCommand("Movement Controls", ScriptStart, "Ramp Speed")</string><string/><string/><string>$motor1speed_end = 127
$motor2speed_end = 255
ControlCommand("Movement Controls", ScriptStart, "Ramp Speed")


Code:


JoystickScriptsUp><string>$motor1speed_end = 64
$motor2speed_end = 192
ControlCommand("Movement Controls", ScriptStart, "Ramp Speed")</string><string/><string/><string>$motor1speed_end = 64
$motor2speed_end = 192
ControlCommand("Movement Controls", ScriptStart, "Ramp Speed")


Code:


ControlCommand("Movement Controls", ScriptStart, "Init (Run First)")
ControlCommand("Graph", ScriptStart)


User-inserted image



:P:P
#23  
ok, I have to go out soon so I wont be able to decipher more and experiment until later tonight (~9:30pm or so ET)

Why when I click the link you provide do I get .xml with even more code to work through?

Also @thetechguru, when I was experimenting with my previously listed verbose ramping script, I did enter it into a custom movement script control and it seemed to ramp and function as expected when executed but when I tried to move it with the joystick it didn't work. I wasn't sure why I was using a clean project for experimentation..
United Kingdom
#24  
The download should download a .ezb file (which yes, is an xml file if you want to get technical). It should open in ARC though, don't try to understand it or copy it from a text editor, that's how problems happen:)

If you struggle to open it from downloading via the forum it's on the cloud so try opening it from within ARC.
Under the File ribbon menu on the right is the EZ-Cloud. Click Open
Then choose Public Library at the top of the dialogue that pops up
In Catagory choose EZ-Script Examples
In User select Rich (currently has a 32 after it)
Hit search
It should be the top one, sabertooth ramping

Open it. Save it locally

You can then merge the required controls. These would be...

Custom Movement Panel
Movement Controls

Note: If you have a Movement Panel already you must remove it before merging.

Then, in your connection control click on the gear icon for the config
In the top box 0 - Connection Established Cmd: put

Code:

ControlCommand("Movement Controls", ScriptStart, "Init (Run First)")



An even better option, attach your current project to this topic, I'll download it and add in the required "bits" that are needed and upload it.

Yes you could add it to the d-pad (the cross joystick) provided it is seen as buttons by ARC.

Provided you have merged the script manager (renamed to Movement Controls) in to the project just use the following code snippets.

All of these are on button down.

Forward/Up

Code:

$motor1speed_end = 1
$motor2speed_end = 255

ControlCommand("Movement Controls", ScriptStart, "Ramp Speed")


Reverse/Down

Code:

$motor1speed_end = 127
$motor2speed_end = 129

ControlCommand("Movement Controls", ScriptStart, "Ramp Speed")


Left

Code:

$motor1speed_end = 1
$motor2speed_end = 129

ControlCommand("Movement Controls", ScriptStart, "Ramp Speed")


Right

Code:

$motor1speed_end = 127
$motor2speed_end = 255

ControlCommand("Movement Controls", ScriptStart, "Ramp Speed")



Now on all of those On Button Up needs to be

Code:

$motor1speed_end = 64
$motor2speed_end = 192

ControlCommand("Movement Controls", ScriptStart, "Ramp Speed")
United Kingdom
#25  
Or download this zip file
SabertoothRamping3.zip

Extract it to My Documents/ARC/My Projects
You should then find a project in your projects called Sabertooth Ramping 3.ezb
#26  
OMG, I just figured out how to find your examples from the public area in the EZ Cloud! This is too awesome!

There may yet be hope...:P
#27  
is that the same as if I open your most recent from the cloud?
United Kingdom
#28  
Yes
#29  
@Rich... dude, you should get 2 credits for this one....:)
#30  
OMG! Happy Dance! It works!




You are the UNDISPUTED MASTER OF THE SCRIPT! WWWWOOOOOOO HOOOOOOO!


The movements are great!

You are right about the ramping up and down not stopping quickly. There is a little lag when starting, stopping and changing direction but WAY F'ING COOLLLLL!

Would it be too difficult to make the following changes:

Change the direction of the joystick control for forward and backward? Right now, forward deflection (12 o'clock) of the joystick makes the robot go in reverse and rear deflection (6'oclock) makes it go forward. BUT THE TURN DIRECTIONS ARE SPOT ON.

Change the max speed of turns down a bit to maybe 80%?

OMG....... I am sooo exicted! Up until now I've been afraid to take him out of the garage. There is a small bump leaving from the concrete pad to the asphalt and I was worried he'd go over if I tried to have him go over it fully assembled and at full speed.

OMG, Ill do some testing with him outside tomorrow! (getting dark now and I really have to be somewhere soon.)

Woooooooooooooo Hoooooooooooo! @Rich is THE MASTER!:D

:D:D:D:D:D:D:):):):):):):):):)
#31  
OMG, MORE THAN TWO CREDITS FOR SURE!



HAPPY, HAPPY JOY, JOY!
United Kingdom
#32  
Changes are easy... change the values in each of the scripts for the Movement Panel (it's why I use variables, it makes minor changes so simple).

Click on the gear icon on the custom movement panel
Click on the small pencil to the right of the box that says Multiline Script for whichever direction you want to change
You will see lines 1 and 2 are something like this

Code:

$motor1speed_end = 1
$motor2speed_end = 255


Adjust the numbers to suit.

So for forwards change them to 127 and 129
For reverse change to 1 and 255
For turning just tweak the numbers down a bit (you may need to play around with them).

I think these are right (Richard R will correct them if wrong, I'm sure he knows them)
Motor 1 full forwards the value is 1
Motor 1 stop the value is 64
Motor 1 full reverse the value is 127
Motor 2 full forwards the value is 255
Motor 2 stop the value is 192
Motor 2 full reverse the value is 129

If you need to make it ramp slower you need to edit the Ramp Speed script, just adjust the variable $rampdelay on line 9. Increase it for a slower speed ramping, decrease it for a quicker speed ramping. The shorter the delay the faster the speed will increase, the longer the delay the slower it will increase.

If you have slower turning speeds than forward and reverse speeds the script will automatically ramp down to the slower speed too.
#33  
AWESOMENESS ABOUNDS!


@Rich, I can't thank you enough!


:)
#34  
First time I have ever corrected @Rich LOL.... Although, I think you erred on purpose...:P

Motor 1 full forwards the value is 1
Motor 1 stop the value is 64
Motor 1 full reverse the value is 127
Motor 2 full forwards the value is 255
Motor 2 stop the value is 192
***Motor 2 full reverse the value is 129 needs to be 128 not 129****
#35  
Great work Rich. I'll be using this in my dog robot too. I wasn't looking forward to figuring it all out myself. I had the right direction, but mine would have been needlessly more complex.

Alan
United Kingdom
#37  
@Richard, I had my suspicions that something was wrong with the values as 128 wasn't assigned to either motor in my example however knowing you know the values from memory it was easier to let you correct me than for me to look it up (yes, I am lazy).

@Alan, funnily enough when I started the script I over complicated it. It's amazingly simple how it works which is great however it did take me 3 attempts to get it right (and I suspect there are one or two things that could be written better).

@Gwen, I'm happy to help out. Writing scripts is an escape and despite me claiming I was going to stop spoon feeding and force people to get the end result themselves it's always good to get stuck in to a useful script:)
#38  
Anyone have any ideas on a way to have the robot automatically stop if the EZB controling it looses its connection? Right now, i think i have a setup for a runaway robot? Hmmmm.

Im thinking an e switch on the power to the sabertooth but am not sure how to make it cut out in the event of a disconnect. The e switch might have to flip a relay too beacause of the current. I don't have an amp meter but i know its drawing over 20 amps at startup...

Any thoughts?
#39  
Now that i think of it, it actually already happened when i did my first testing outdoors with only the lower half. Had to run after him and tackle his power switch... It would be really cool to be able to just grab his power pack but it only interupts the upper half
United Kingdom
#40  
On disconnection you wont be able to send commands to the sabertooth so it will need to be some kind of auto disconnect/stop circuit such as a relay inline with the batteries supplying the motors.

The good news is, the digital ports on the EZ-B will go low on disconnection so you could use this to de-energize the relay. You would need to set the digital port to high/on in some kind of init script though otherwise the power to the motors will be cut until it's set high.
#41  
Following on Rich's comment, it is important that you still have connection for power to go back to your battery from the Sabertooth. Dave S has a circuit with a diode in one of the Sabertooth discussions (not sure if you were involved in that conversation or not, it was recent).

edit: here is the thread: sabertooth one-way cutoff

The Sabertooth has regenerative charging, so if you are pushing the bot around so that the motors spin, they will act like generators, that the Sabertooth will push voltage back to the batteries. If there is no where for that voltage to go, the Sabertooth can be damaged.

So, absolutely need an emergency cutoff, but should be designed so that it only stops flow from battery to sabertooth, but not from sabertooth to the battery.

Alan
United Kingdom
#42  
I need a sabertooth, there's much I don't know about it:)

So a relay which switches between straight through connection to the motors from the battery (for normal operation) and switches to the same but with diodes to only allow flow from sabertooth to battery to happen for when emergency shut off?

Quick and dirty schematic time:)

User-inserted image


When energised it works as normal. When power is cut it allows current flow in only one direction (i.e. regenerative)
I realise I have the relay backwards and I may even have the diode backwards, it's not meant as a proper schematic but an aid to my description above;) Honest...



P.S. Don't judge me on the schematic, I did say it was quick and dirty:)
#43  

Quote:

I need a sabertooth, there's much I don't know about it


If you are short of discretionary cash, but are serious about wanting to get one, I have two thoughts for you.

1) The 2x12 is functionally identical to the 2x25 but costs about 1/3 less.

2) If you want either, and still have copious EZ-Robot credit, you could order me some EZ bits that I need and I'll order you a Sabertooth, so you get the Sabertooth as a thank you for answering so many questions, and I still get the bits I would be buying anyway.

Alan
United Kingdom
#44  
It's not so much the lack of funds, there are a few things holding me off (the main one being the sabertooth would mean I need decent motors, then encoders, then the kangaroo, then a robot to put it all in... it's a vicious cycle, kind of like drugs lol)

I also have a large pile of things I have been wanting to get through for a while now and it's getting bigger. BlinkM, TellyMate (all variants), LCD displays, I2C communication with other controllers, JD, Six, a bunch of EZ-Bits... I think I need to clear at least some of that pile before I add more to it:)

Thanks for the offers and advice as always though.
#45  
OMG, took him outside for the first time with him full built up... Nerve racking to say the least...

The bad new: He ended up off the driveway in a ditch tipping JUUUUSSSST shy of going over... wheww... The control is a bit unnatural due to the lag and the way the ramping seems to continue for a time after input stops. Add to that my driveway is uneven and mildly inclined plus, my notebook seemed to be working hard. There seemed to be a com delay too.

Note to self: Do not wear flip flops while experimenting with a 300 lb robot and NEVER get the front of one under a tread...

Note to self two: Get a wireless game controller and NEVER let the cord of the current one get under a tread... Very bad...

It was much better when I got him into our street which is level. One of my neighbors drove by and stopped next to him. The G-Bot escorted him down the street for a short bit... very cool.

The good news: He DIDN'T go over and my and my neighbors had some great fun!

I'll do some more practice with him tomorrow when my Son will be home. That should be fun and hopefully we'll figure out enough to get a few Trick or Treaters going on Friday...

I'll put up a short vid later tonight
#46  
Very exciting. Looking forward to seeing the video.

Alan
#47  
Fell asleep last night...


Here is the video from yesterday's testing...
@thetechguru
@rich
@Richard
@Richard R

More next week after the dust from Halloween settles...

Enjoy

Thanks for all your help guys!



:D:D:D:D:D:D:D
#48  
What's more impressive than that amazing b9 is the way you casually dematerialized at the 10:19 mark. Forget EZ-Robot, how'd you do that ;)
#49  
@pacowang.... EZ Robot did that too.... Yes, it's that good....
#50  
@Rich Had a chance to try your mods to the code. Works great as far as slowing to a stop sooner. Its definitely an improvement.

Not sure if its the code or com or my cpu but sometimes there is a long lag, like several seconds before the robot begins to move again.

either way its definitely an improvement and its ingestion merged into the rest of the Halloween routine!

Thanks again Rich!
#51  
Oops maybe not, just got the error in the screencapture bellow. The console is scrolling the message ; "Control named 'Motor 2 speed' does not exist; Cannot send command 'SetValue'
User-inserted image
#52  
Have no idea what the script is doing. After reloading after the bug, the joystick seems to do nothing for a long time (15 20 seconds or more) then after a while it will briefly begin to move then no response then it begins to respond...

I think it doesn't like multiple joystick inputs. Seems to paralyze it. Not really sure though.
United Kingdom
#53  
Just remove the graphs and graph script, take the ControlCommand() for the hraph our of the on connection script. You dont need the graphs.

I would do it but I'm away now until the end of the weekend.
#54  
I think if you hit the start buttons in the two scripts in the "movement controls" object, it will set up the missing variables (I know you need the first one, I think the second one).

Alan
#55  
I didn't know to initialize both. Works great now! Thanks!
#56  
Gwen, I'm glad you have this working to your liking. These guys are wonderful with helping to find a way to get ezb to work for you. I'm sure the script they provided is the way to go to get the controller to work. However as far as the ramping issue I really believe that you are going to have to use the DESCRIBE software and use it to get into the Sabertooth to change some settings. Sabertooth has built in ramping control that you can adjust and fine tune. You can also set it to respond to either RC or analog signal. I think you'll get better and smoother control if you can figure out how to make these adjustments work for you.
#57  
Sounds like an area to research for sure @Dave
#58  
Well, actually the new script isn't working. Something about a 'motor 2 endspeed not defined' I didnt notice before. I don't even know where to look.

No worries though, I have the G-Bot set up with v1 of the ramping code and am ready to go...

The G-Bot's Halloween 2014 development phase if officially closed. Its showtime!
#59  
Have fun and don't forget to give us a front seat for the show!
#60  
@gwen Good luck... and try not to kill any of the trick or treaters with that thing.... LOL
#61  
No dead children tonight (at least not by the treads of the G-bot) Lol... I'll post a nice update late tomorrow and video as soon as I have some time tom put something together.

Lots of lessons learned ... Lots of fun...

Scared the heck out of my grandson... ;)