Forum >Code - Compiling, Loading, Modifying
Code - Compiling, Loading, Modifying
sbirdranch 2013-09-22 04:14:27 9799 Views8 Replies I started a new topic for questions regarding the code that Stanley provides with his kits.
I don't want to have to surf through assembly questions and pid questions to find only code related questions.
I'll start with the first one....
Has anyone else found that they cannot download code to their atmega based telematics assembly, if the OBD-II connector is attached to the UART port?
I'm wondering if this is normal and to be expected. I'm having other issues and want to determine if this is a symptom.
I don't want to have to surf through assembly questions and pid questions to find only code related questions.
I'll start with the first one....
Has anyone else found that they cannot download code to their atmega based telematics assembly, if the OBD-II connector is attached to the UART port?
I'm wondering if this is normal and to be expected. I'm having other issues and want to determine if this is a symptom.
2013-10-25 07:08:51 Stanley,
I finally got the code to build using the Arduino compiler, but now it says the file is too large for the processor:
"Binary sketch size: 30,978 bytes (of a 30,720 byte maximum)"
Any ideas on what can be safely trimmed from the sketch without jeopardizing functionality?
Thanks. brcd131
I finally got the code to build using the Arduino compiler, but now it says the file is too large for the processor:
"Binary sketch size: 30,978 bytes (of a 30,720 byte maximum)"
Any ideas on what can be safely trimmed from the sketch without jeopardizing functionality?
Thanks.
brcd131 2013-10-21 15:36:29 More info - CodeBlocks appears to compile and link it ok, but it produces a hex file that is 80K in size which I think is too big for the Nano board. Part of the extra size is because the GPS stuff is in there, even though GPS is turned off in the code.
Also, when I look at the log file for the ArduinoBuilder build, it starts out saying "Compiling obdlogger.ino" then compiles a few more files then says "Compiling obdlogger.ino" again. Not sure why it compiles this twice (or appears to do this).
Thanks,
Chuck brcd131
Also, when I look at the log file for the ArduinoBuilder build, it starts out saying "Compiling obdlogger.ino" then compiles a few more files then says "Compiling obdlogger.ino" again. Not sure why it compiles this twice (or appears to do this).
Thanks,
Chuck
brcd131 2013-10-21 07:56:41 Stanley,
Still no luck. I have all of the main files in a folder called "obdlogger" as the arduino compiler wants, and I deleted the SSD1306.* files from the library folders so there was no duplication, and I also made sure that all of the library files had the latest versions based on your latest download and they do and I still get the multiple definition error. Any other ideas what may be causing this?
Thanks,
Chuck brcd131
Still no luck. I have all of the main files in a folder called "obdlogger" as the arduino compiler wants, and I deleted the SSD1306.* files from the library folders so there was no duplication, and I also made sure that all of the library files had the latest versions based on your latest download and they do and I still get the multiple definition error. Any other ideas what may be causing this?
Thanks,
Chuck
brcd131 2013-10-20 16:02:11 Stanley,
I'm still having problems compiling and uploading the example code to kit #1. Here's a partial screen shot of some of the errors I get - Multiple definition error. I've tried a number of things to avoid this like putting #ifndef in the header files to be sure that they are not re-entered but it didn't help. I also noticed that even though USE_GPS is turned off, the TinyGps module is still included in the build. I manually removed all the GPS code and that didn't help. Any ideas how I can get the code to compile and upload to the Nano using ArduinoBuilder? Thanks. brcd131
I'm still having problems compiling and uploading the example code to kit #1. Here's a partial screen shot of some of the errors I get - Multiple definition error. I've tried a number of things to avoid this like putting #ifndef in the header files to be sure that they are not re-entered but it didn't help. I also noticed that even though USE_GPS is turned off, the TinyGps module is still included in the build. I manually removed all the GPS code and that didn't help. Any ideas how I can get the code to compile and upload to the Nano using ArduinoBuilder? Thanks.
brcd131 2013-10-04 15:59:56 Stanley,
I am using your Kit#3 with Model B of the OBD adapter. The issue is not when I am powering the board to run it. The problem is when I have it sitting on the bench and I am uploading code to the Arduino Mega board. If I leave the OBD connector attached, It draws power from the board, when is plugged into my laptop USB port.
The screen module being used is the one you supply with Kit#3
I hope this helps.
Sb. sbirdranch
I am using your Kit#3 with Model B of the OBD adapter. The issue is not when I am powering the board to run it. The problem is when I have it sitting on the bench and I am uploading code to the Arduino Mega board. If I leave the OBD connector attached, It draws power from the board, when is plugged into my laptop USB port.
The screen module being used is the one you supply with Kit#3
I hope this helps.
Sb.
sbirdranch 2013-09-23 03:57:00 I have narrowed down the problem to power draw.
When the OBD-II is connected, it is drawing so much power that the USB port can't keep up.
I verified this by downloading the software without the connecter attached. Success.
Unplugged the usb cable.
Powered the board up via the barrel jack and a 9v battery. The software booted and the display was nice and bright.
I plugged in the OBD-II connector. The board rebooted and the display was very dim. sbirdranch
When the OBD-II is connected, it is drawing so much power that the USB port can't keep up.
I verified this by downloading the software without the connecter attached. Success.
Unplugged the usb cable.
Powered the board up via the barrel jack and a 9v battery. The software booted and the display was nice and bright.
I plugged in the OBD-II connector. The board rebooted and the display was very dim.
sbirdranch 2013-09-23 03:18:37 Thanks Jose. That is good info. I am familiar with that limitation with boards having only a single UART.
In this case, my post noted that this was an AtMega (Arduino Mega) chip which has several (4). As I have been following the instructions I can find regarding the Mega Logger (kit 3 from from ArduinoDev.com), the setup and code have the OBD-II connector plugged into UART 1. This leaves what I thought was the default, of UART-0 open for com via USB.
P. sbirdranch
In this case, my post noted that this was an AtMega (Arduino Mega) chip which has several (4). As I have been following the instructions I can find regarding the Mega Logger (kit 3 from from ArduinoDev.com), the setup and code have the OBD-II connector plugged into UART 1. This leaves what I thought was the default, of UART-0 open for com via USB.
P.
sbirdranch 2013-09-22 20:07:09 Sbirdranch,
This is usually quite normal, for all arduino modules and shields. Arduino UNO and older most cases have just 1 serial port which is also attached to the USB port. If this serial port / UART is blocked, the PC can't upload the sketch. Many of DFRobot products have a switch which you can use to unblock/block the serial without unplugging your shield or module. But if this is not the case, the fix is quite simple, just unplug it when you are ready to upload the sketch.
There are a few alternatives to this. Like software serial, or using a different Serial port on boards like Arduino Mega or Leonardo. But it complicates the coding as well and quite often leads to confusions.
Cheers^^ Jose
This is usually quite normal, for all arduino modules and shields. Arduino UNO and older most cases have just 1 serial port which is also attached to the USB port. If this serial port / UART is blocked, the PC can't upload the sketch. Many of DFRobot products have a switch which you can use to unblock/block the serial without unplugging your shield or module. But if this is not the case, the fix is quite simple, just unplug it when you are ready to upload the sketch.
There are a few alternatives to this. Like software serial, or using a different Serial port on boards like Arduino Mega or Leonardo. But it complicates the coding as well and quite often leads to confusions.
Cheers^^
Jose 