Blinking LED and Communication Error
Blinking LED and Communication Error
by Viknesh
Wed Jul 04, 2007 5:06 am
Whenever i switch on the robonova, its headlight starts to blink. Cannot download any codes into the controller as it says communication problem -4 or -5. I even changed the micom board, but the same thing happens. But when i click controller reset mode in robobasic robonova responds and does an action.So that means there is connection.So What is the problem?I need some suggestions urgently as i am doing school project.Thanks
by Fritzoid
Thu Jul 05, 2007 3:07 pm
Hi Viknesh,
Your biggest problem is the -4 or -5 communications error which may be related to the hardware you are using to communicate with. The RN1 comes with a serial cable which cannot connect directly to a modern laptop without a USB converter. Some USB converters have timing issues with the RN controller. I suggest you get a serial port monitor to help you debug this problem. Check some of the older threads on this forum for links to free monitoring software.
The blinking LED is indication that the batteries are not fully charged. This is usually due to a well-known bug in the control program. You need to comment out the line that calls the battery check subroutine and reload the basic program to stop the blinking. Unfortunately the control program does not listen for incomming command while the LED is blinking so you will have touble making a connection for downloading. Just keep trying eventually you'll get lucky.
Check some older threads for users with similar problems and their solutions. You are not alone.
Your biggest problem is the -4 or -5 communications error which may be related to the hardware you are using to communicate with. The RN1 comes with a serial cable which cannot connect directly to a modern laptop without a USB converter. Some USB converters have timing issues with the RN controller. I suggest you get a serial port monitor to help you debug this problem. Check some of the older threads on this forum for links to free monitoring software.
The blinking LED is indication that the batteries are not fully charged. This is usually due to a well-known bug in the control program. You need to comment out the line that calls the battery check subroutine and reload the basic program to stop the blinking. Unfortunately the control program does not listen for incomming command while the LED is blinking so you will have touble making a connection for downloading. Just keep trying eventually you'll get lucky.
Check some older threads for users with similar problems and their solutions. You are not alone.
STILL HAVE PROBLEM
by Viknesh
Tue Jul 10, 2007 8:34 am
Thanks for the help. But i still cannot establish the connection between computer and robonova. I even changed the serial cable but the same error appears.Please help.
by Fritzoid
Tue Jul 10, 2007 2:12 pm
There are many things that can lead to you particular error. The task at hand is to break the problem down to managable pieces. The first thing is to verify that you are communication over the correct port at the correct speed and parity. To determine this and to debug any protocol problems it will be necessary to see just what data is being exchanged. For this you
need a serial port monitor.
I suggest you try this link
http://www.serial-port-monitor.com/
Once this is in place we can see how far along you are getting and possibly solve your communications problem.
Do you have an actual serial port on your computer or are you using a USB to serial converter?
need a serial port monitor.
I suggest you try this link
http://www.serial-port-monitor.com/
Once this is in place we can see how far along you are getting and possibly solve your communications problem.
Do you have an actual serial port on your computer or are you using a USB to serial converter?
by Viknesh
Wed Jul 11, 2007 4:27 am
ok i tried the Serial port monitor. I had this information about the data when downloading data to controller.
Port opened by process "rbv2.exe" (PID: 3812)
F0
Port closed
Port opened by process "rbv2.exe" (PID: 3812)
EC
Port closed
I connect to serial port directly.Not using USB.
Controller information command in robobasic does not work. but when i click the controller reset mode, the robonova responds well.
Port opened by process "rbv2.exe" (PID: 3812)
F0
Port closed
Port opened by process "rbv2.exe" (PID: 3812)
EC
Port closed
I connect to serial port directly.Not using USB.
Controller information command in robobasic does not work. but when i click the controller reset mode, the robonova responds well.
by Fritzoid
Wed Jul 11, 2007 7:48 pm
OK, two requests but no responses, we're getting farther!
F0 - is a request for the controller ID
EC - is a request to download a basic program
Both of these should get an echo from the controller. If there is no response then its probably a hardware issue.
Are you connected/configured to the right comm port?
What do you mean by "changed the cable"?
Are you using the cable that came with the RoboNova?
F0 - is a request for the controller ID
EC - is a request to download a basic program
Both of these should get an echo from the controller. If there is no response then its probably a hardware issue.
Are you connected/configured to the right comm port?
What do you mean by "changed the cable"?
Are you using the cable that came with the RoboNova?
by i-Bot
Wed Jul 11, 2007 10:58 pm
If you are seeing data in the write area, and not the read area, then you are getting no input from the RoboNova.
Disconnect the serial cable from the RoboNova, and short the tip contact to the middle contact on the cable. Make no connection to the long contact part of the connector. Try the download again.
If this gives a different error, and also shows data in the read window, then I would suspect the problem is that your serial port does not like the output levels from the RoboNova. They are not proper RS232 levels and only go from 0 to 5V. This can be a problem to some serial ports, long cables, and poor connectors. You will need to try with a different serial port.
If you don't get an read responses even with the sort, then there is something wrong with your serial port or the software.
Disconnect the serial cable from the RoboNova, and short the tip contact to the middle contact on the cable. Make no connection to the long contact part of the connector. Try the download again.
If this gives a different error, and also shows data in the read window, then I would suspect the problem is that your serial port does not like the output levels from the RoboNova. They are not proper RS232 levels and only go from 0 to 5V. This can be a problem to some serial ports, long cables, and poor connectors. You will need to try with a different serial port.
If you don't get an read responses even with the sort, then there is something wrong with your serial port or the software.
by Viknesh
Thu Jul 12, 2007 5:51 am
Controller type setting is set correctly. As i was trying today suddenly the Robonova motor control option seemed to work. The serial port monitor showed alot of hex values in both Read Requests and Write Requests. But once i disconnected and tried again, the same error start to appear. I think most probably something wrong with the cable. I actually tried two serial cables. Both seems to give the same problem. Anyway can explain how to short the tip contact. I want to try and see whether it solves the problem.Thanks.
by Fritzoid
Thu Jul 12, 2007 11:15 am
I know that we have been questioning the quality of your computer's serial connection and in particular the receive data line, which is a likely source of your trouble but one other possibility comes to mind. Other users have reported problems with their battery chargers. The LED turns green after some time but the batteries are not recharged. If the batteries are weak then two-way communications are a problem! If you have a voltmeter you can disconnect the battery pack and check the voltage. A fully charged pack should show 7 Volts or more.
by Fritzoid
Fri Jul 13, 2007 7:00 pm
Correction... my fully-charged battery pack reads 6.67volts.
Disconnect the battery pack and measure the voltage from the two metal strips on the back side of the connector. Be careful not to cross the leads because a short-circuit can quickly generate a lot of current and heat!
Disconnect the battery pack and measure the voltage from the two metal strips on the back side of the connector. Be careful not to cross the leads because a short-circuit can quickly generate a lot of current and heat!