rcchavez
Registered: 11/13/08
Posts: 3
|
|
| |
Reply with quote | #1 |
I'm attempting to establish communication between the AX2850 and a Mini-ITX EMB-852T computer via RS-232. The computer is running Windows XP SP3. The computer has several serial ports available.
Roborun shows that COM1 port is active and it says that communication is established. However, it does not display information about the Roboteq, i.e. Controller ID, Firmware Version. When I attempt to change parameters and save to controller, I cannot connect to the controller and a Run Time 401 error is displayed.
I have spent quite a bit of time ensuring that the com port is configured correctly with the corresponding baud rate, transfer bits, and parity. I have tried using each com port with no success. I have tested the com ports on the computer through hyper-terminal and they are functioning correctly. I can connect to the Roboteq through a USB to serial dongle but I would like to make use of the available serial ports.
Any suggestions?
|
| Loading... | | |
cosma
Moderator
Registered: 04/10/04
Posts: 533
|
|
| |
Reply with quote | #2 |
Click on the cosole tab. This will show you the raw data that is seen on the com port. You can also send data on the com port that way.
If you see nothing, then try shorting pins 2 and 3 on the com connector of your PC. This will feed the TxData into the RxData. With the roborun console try sending something. You should see it echoed on the screen. If nothting, then chances are the com port is not working.
|
| Loading... | | |
rcchavez
Registered: 11/13/08
Posts: 3
|
|
| |
Reply with quote | #3 |
Thanks for replying. I started Roborun and entered the console tab. From the Roboteq controller I can see on the console that it is sending "wW" to the PC. Roborun says the com port is active and communication is established but I cannot transmit anything to the Roboteq.
I shorted pins 2 and 3 of the com port on the PC as you had suggested and what ever I enter is echoed on the Roborun console. This makes me think the com port on the PC is working properly.
Have there ever been any issues with hardware compatibility?
|
| Loading... | | |
cosma
Moderator
Registered: 04/10/04
Posts: 533
|
|
| |
Reply with quote | #4 |
the repeated W means that the controller is in RS232 mode with Watchdog enabled.
Unless you have modified the settings, the controller starts up in RC mode and needs to received specific commands (sent when roborun starts) for it to switch to RS232 mode.
In this case, it would mean that it can receive ok. The W's you see, mean that it can send OK as well.
The echo you see shorting the pins on the PC's com port are also a good sign.
So, it would appear that everything works independently, but not together.
Try again your USB adapter to make sure the controller is OK. Try connecting another device to your com1 port to make sure it is OK.
|
| Loading... | | |
rcchavez
Registered: 11/13/08
Posts: 3
|
|
| |
Reply with quote | #5 |
I tried using the USB to serial adapter again. I am able to establish communication and control the Roboteq using the adapter.
I tested the com port on the Mini-ITX with a laptop, a null modem cable, and hyper terminal. I can communicate on both ends just fine this way.
So for some reason the Mini-ITX cannot communicate with the Roboteq through the onboard serial port. As you suggested everything works independently, but not together. I will try and check voltage levels on the com port of the Mini-ITX. Maybe it is not reaching levels that the Roboteq can respond to.
|
| Loading... | | |
cosma
Moderator
Registered: 04/10/04
Posts: 533
|
|
| |
Reply with quote | #6 |
You can try determine wether the problem is because the PC to Conroller or because Controller to PC miscommunication.
Launch roborun, go to the console tab.
Reset the controller. If you see the prompt, then your motherboard receives OK.
Click on the Enter x 10 button. If PC to controller communication works, the display should change from "no ctrl" to a steady "u"
|
| Loading... | | |
