Port Closed in Roborun
9 years 2 months ago #29529023
by jetonski
Port Closed in Roborun was created by jetonski
My Roboteq controller is connected via serial to a bluetooth module. In both Windows and OSX I'm able to pair with that bluetooth module and open a serial connection to the controller in any serial terminal emulator, or via my own software. This meets almost all of my needs, but...
I would like to upload new scripts or firmware via Roborun. And Roborun, as I've seen in several other forum posts, does not like COM ports that do not open and reply very quickly. Opening this COM port takes a few seconds, due to the devices reconnecting when you open the port. I suspect two possible timeouts interfering here: 1- when Roborun attempts to open a port. 2- when Roborun pings for a device. (If they're not in fact the same) In my case, I suspect that 1 is the issue, but being able to configure both would be helpful. I'm not the first person trying to do this, clearly.
I found instructions to upload new firmware via YMODEM, which I expect I can get working with a little trial and error. Is it possible to upload a new script without Roborun? The Build button outputs human readable btyecode, and I assume Export HEX exports binary without all the comments? Is that even close to correct? Is it possible to take the output of either of those and send it via a serial terminal in some ad-hoc way?
Thanks,
Jacob
I would like to upload new scripts or firmware via Roborun. And Roborun, as I've seen in several other forum posts, does not like COM ports that do not open and reply very quickly. Opening this COM port takes a few seconds, due to the devices reconnecting when you open the port. I suspect two possible timeouts interfering here: 1- when Roborun attempts to open a port. 2- when Roborun pings for a device. (If they're not in fact the same) In my case, I suspect that 1 is the issue, but being able to configure both would be helpful. I'm not the first person trying to do this, clearly.
I found instructions to upload new firmware via YMODEM, which I expect I can get working with a little trial and error. Is it possible to upload a new script without Roborun? The Build button outputs human readable btyecode, and I assume Export HEX exports binary without all the comments? Is that even close to correct? Is it possible to take the output of either of those and send it via a serial terminal in some ad-hoc way?
Thanks,
Jacob
Please Log in or Create an account to join the conversation.
- Griffin Baker
9 years 2 months ago #29529025
by Griffin Baker
Replied by Griffin Baker on topic Port Closed in Roborun
What is the brand and model of your USB-BT dongle that plugs in the PC, and the USB-Serial that plugs into the controller.
Have you tried a recent roborun and that you can force the COM port number. In the upper left hand corner of the browser where it says comports. It is by default set to auto, but the drop down box menu will show you all the available ports that it sees and you can assign it one of those ports.
Have you tried a recent roborun and that you can force the COM port number. In the upper left hand corner of the browser where it says comports. It is by default set to auto, but the drop down box menu will show you all the available ports that it sees and you can assign it one of those ports.
Please Log in or Create an account to join the conversation.
9 years 2 months ago #29529026
by jetonski
Replied by jetonski on topic Port Closed in Roborun
Thanks Griffin,
The bluetooth module on the controller side is a SparkFun Bluetooth Mate (www.sparkfun.com/products/12576).
The actual setup is Roboteq VBL2350 -> Max3232 (RS-232 to TTL) -> Teensy3.1 (Arduino compatible microController) with code exclusively handling echo to -> BlueTooth Mate Silver
On the computer side, it's the builtin bluetooth device on a MacBookPro running bootcamp / windows 7 (dual-boot, not a virtual machine).
I'm running Roborun 1.2, downloaded today, and have tried manually selecting the COM port with no luck.
The bluetooth module on the controller side is a SparkFun Bluetooth Mate (www.sparkfun.com/products/12576).
The actual setup is Roboteq VBL2350 -> Max3232 (RS-232 to TTL) -> Teensy3.1 (Arduino compatible microController) with code exclusively handling echo to -> BlueTooth Mate Silver
On the computer side, it's the builtin bluetooth device on a MacBookPro running bootcamp / windows 7 (dual-boot, not a virtual machine).
I'm running Roborun 1.2, downloaded today, and have tried manually selecting the COM port with no luck.
Please Log in or Create an account to join the conversation.
- Griffin Baker
9 years 2 months ago #29529027
by Griffin Baker
Replied by Griffin Baker on topic Port Closed in Roborun
It says not to plug this directly into the serial port. Perhaps you should get a RS232 shifter.
www.sparkfun.com/products/449
www.sparkfun.com/products/449
Please Log in or Create an account to join the conversation.
9 years 2 months ago #29529028
by jetonski
Replied by jetonski on topic Port Closed in Roborun
Griffin, that's exactly what the MAX3232 chip listed above does. The setup works fine with any other software that opens the serial port.
Well, I should clarify - the Bluetooth Mate sometimes fails to connect successfully on any given attempt, so sometimes it takes a few open attempts for the port to open successfully, but after an attempt or three, it works, and once the port is opened the data flows flawlessly.
The issue with Roborun seems to lie in how the software opens the port, maybe in the timing of it all?
If you think there may be other hardware matters I haven't considered, please do let me know.
Any ideas on Roborun timeouts when it's searching for a controller? How about when a port is manually selected?
I'm wondering if you have any answers to the questions about compiling scripts and uploading via other serial communication methods? That would give me a workaround for now...
Well, I should clarify - the Bluetooth Mate sometimes fails to connect successfully on any given attempt, so sometimes it takes a few open attempts for the port to open successfully, but after an attempt or three, it works, and once the port is opened the data flows flawlessly.
The issue with Roborun seems to lie in how the software opens the port, maybe in the timing of it all?
If you think there may be other hardware matters I haven't considered, please do let me know.
Any ideas on Roborun timeouts when it's searching for a controller? How about when a port is manually selected?
I'm wondering if you have any answers to the questions about compiling scripts and uploading via other serial communication methods? That would give me a workaround for now...
Please Log in or Create an account to join the conversation.
Moderators: tonysantoni
Time to create page: 0.064 seconds