Send motor controller commands w/ Flowstone
Posted: Thu Jan 20, 2011 6:48 amI have been trying to successfully create a Flowstone configuration that would let me control a rover with a Bot Board II (w/ AtomPro 28) connected to a motorcontroller (RoboClaw) set to hardware serial and mixed control. First I am testing the use of a serial cable, then using a Cat5e (virtual com port) for long distance (300') control.
I feel I have been getting strange behavior from Flowstone. I did something in an earlier FSM configuration and as soon as I input 08100, the motors turned (command = 8, speed = 100). If I hit backspace, it stopped. As long as there were 2 valid digits for the command and 3 valid digits for the speed, the motors would turn as they should. It was awesome, but short-lived. Then, after making no changes to the Flowstone configuration, it stopped working. For comparison, I can immediately switch to a terminal program that sends a string macro when I press F1.
I am not sure what I am missing with the Flowstone configuration, but I had everything working for about 20 minutes and then it stopped, reason unknown. I recall trying to introduce a component on the left side of the Com Port module, hoping that would somehow stream the command string data. The attached FSM is my latest attempt to create a simple configuration that will send the command string to the waiting tracked rover. I know the rover will accept the commands based on the testing with a terminal program. Again, as soon as I close Flowstone (and Com) and send a command string (example 08084) using a Terminal Program...motors turn. That's why I think it's flowstone. Flowstone has also been crashing when there is no delay on the repetition of the send. I received some assistance in the Lynxmotion forum, but I felt it was a good idea to reach out to you about your product.
The code loaded onto the AtomPro28 is listening for the command string (command = 2 digits and speed = 3 digits) at 38400. That's why 08084.
Considering the attached Flowstone configuration...
1) How can I get the attached or similar Flowstone configuration to successfully be sent to the Rover?
2) How can I receive a broadcast string ("Hello") from the rover?
3) Considering a future goal to use Cat5e, are there any common errors I should be looking for when configuring the virtural com port? Beside the obvious like baud, stopbits, etc.
4) Does Flowstone support virtual com ports (specifically for a Wiznet RS323/RJ45 converter)? Bummer if it doesn't. That would mean no Cat5e for me.
It really is unfortunate that I can't replicate the working behavior I had that day. As soon as I would add the last digit to the input string component, motors would turn. As soon as I hit backspace, they would stop. By the way, I have a hault command built in so the robot needs to receive the command over and over again to keep the rover moving or else it stops. This is my safety feature in case communication is lost with the rover.
Thx
Mike
I feel I have been getting strange behavior from Flowstone. I did something in an earlier FSM configuration and as soon as I input 08100, the motors turned (command = 8, speed = 100). If I hit backspace, it stopped. As long as there were 2 valid digits for the command and 3 valid digits for the speed, the motors would turn as they should. It was awesome, but short-lived. Then, after making no changes to the Flowstone configuration, it stopped working. For comparison, I can immediately switch to a terminal program that sends a string macro when I press F1.
I am not sure what I am missing with the Flowstone configuration, but I had everything working for about 20 minutes and then it stopped, reason unknown. I recall trying to introduce a component on the left side of the Com Port module, hoping that would somehow stream the command string data. The attached FSM is my latest attempt to create a simple configuration that will send the command string to the waiting tracked rover. I know the rover will accept the commands based on the testing with a terminal program. Again, as soon as I close Flowstone (and Com) and send a command string (example 08084) using a Terminal Program...motors turn. That's why I think it's flowstone. Flowstone has also been crashing when there is no delay on the repetition of the send. I received some assistance in the Lynxmotion forum, but I felt it was a good idea to reach out to you about your product.
The code loaded onto the AtomPro28 is listening for the command string (command = 2 digits and speed = 3 digits) at 38400. That's why 08084.
Considering the attached Flowstone configuration...
1) How can I get the attached or similar Flowstone configuration to successfully be sent to the Rover?
2) How can I receive a broadcast string ("Hello") from the rover?
3) Considering a future goal to use Cat5e, are there any common errors I should be looking for when configuring the virtural com port? Beside the obvious like baud, stopbits, etc.
4) Does Flowstone support virtual com ports (specifically for a Wiznet RS323/RJ45 converter)? Bummer if it doesn't. That would mean no Cat5e for me.
It really is unfortunate that I can't replicate the working behavior I had that day. As soon as I would add the last digit to the input string component, motors would turn. As soon as I hit backspace, they would stop. By the way, I have a hault command built in so the robot needs to receive the command over and over again to keep the rover moving or else it stops. This is my safety feature in case communication is lost with the rover.
Thx
Mike
