Forum >OBD-II Megalogger - Strange operation
OBD-II Megalogger - Strange operation
chevyplowman 2013-12-09 20:00:10 4334 Views2 Replies Stanley - First I have to say. This thing is Great, I can't even imagine how many hours you have into it! Thanks for sharing your knowledge! That being said, I have had the OBD-II logger kit # 2 for about a week now, and I am finding some weird things happening.
[list type=decimal]
[*]I was originally getting an intermittent problem with the SD card. Once I changed the settings in the config file to use the SS pin, everything with reading/writing to the SD card seems to be working fine from that perspective. Then I decided to enable logging which brings me to problem 2.
[*]When I read the logs it appears that I am getting random information in each of the pieces of data. RPM, Speed, and GPS coordinates randomly appear, and it looks like some of the information is in HEX.
[*]During the boot process, once the GPS gets a fix, OBD, dfrobot, and GPS all show the "Checkmark", and the SD card is recognized correctly. However, the list on the right side of the screen seems to randomly show the "Checkmark" for different PID's,(on every power up) sometimes it shows none, other times it shows many of them, and other times it shows one. THIS IS VERY RANDOM!.
[*]When the operation screen with the 4 quadrants appears, the RPM and speed show up and appear to be correct. The throttle position doesn't ever seem to update, and the temperature doesn't appear to either.
[/list]
While trying to troubleshoot this, I hooked up the serial monitor and tried to review some of the data that was being sent, however upon attaching the serial port to my computer, it seems that every time the screen is "re-drawn"/"re-freshed", it appears that the display is actually being output to the serial port the in HEX.
I would greatly appreciate some help troubleshooting this problem.
Thanks again for your hard work!!!
[list type=decimal]
[*]I was originally getting an intermittent problem with the SD card. Once I changed the settings in the config file to use the SS pin, everything with reading/writing to the SD card seems to be working fine from that perspective. Then I decided to enable logging which brings me to problem 2.
[*]When I read the logs it appears that I am getting random information in each of the pieces of data. RPM, Speed, and GPS coordinates randomly appear, and it looks like some of the information is in HEX.
[*]During the boot process, once the GPS gets a fix, OBD, dfrobot, and GPS all show the "Checkmark", and the SD card is recognized correctly. However, the list on the right side of the screen seems to randomly show the "Checkmark" for different PID's,(on every power up) sometimes it shows none, other times it shows many of them, and other times it shows one. THIS IS VERY RANDOM!.
[*]When the operation screen with the 4 quadrants appears, the RPM and speed show up and appear to be correct. The throttle position doesn't ever seem to update, and the temperature doesn't appear to either.
[/list]
While trying to troubleshoot this, I hooked up the serial monitor and tried to review some of the data that was being sent, however upon attaching the serial port to my computer, it seems that every time the screen is "re-drawn"/"re-freshed", it appears that the display is actually being output to the serial port the in HEX.
I would greatly appreciate some help troubleshooting this problem.
Thanks again for your hard work!!!
2013-12-11 19:00:34 Thanks for keeping with me on this and assisting in my learning. I appreciate you decoding those. This is very interesting, that certainly was not how I thought it would be.
Just to clarify, the format of these logs are as follows....Correct?
COL A COL B COL C
OBD BUS update time HEX value of PID to be logged actual data of correct PID from col B
Do you have any idea what any of the other data means in that snapshot I provided, or would you have any suggestions on how to decode/decipher what it is?
One other Item I ran across, I was thinking that maybe I could use the bluetooth to decode some things. So I went into the config.h file and set USE_OBD_BT to 1. When i looked at arduinodev.com site it talked about A8, A9 for the serial port. This seems to be already configured in the datalogger.h file.
I have tried 4 different ways to interface with my iPhone 5s, and it never seems to show up. Did I dfrobot something else?
Thanks! chevyplowman
Just to clarify, the format of these logs are as follows....Correct?
COL A COL B COL C
OBD BUS update time HEX value of PID to be logged actual data of correct PID from col B
Do you have any idea what any of the other data means in that snapshot I provided, or would you have any suggestions on how to decode/decipher what it is?
One other Item I ran across, I was thinking that maybe I could use the bluetooth to decode some things. So I went into the config.h file and set USE_OBD_BT to 1. When i looked at arduinodev.com site it talked about A8, A9 for the serial port. This seems to be already configured in the datalogger.h file.
I have tried 4 different ways to interface with my iPhone 5s, and it never seems to show up. Did I dfrobot something else?
Thanks!
chevyplowman 2013-12-10 15:06:39 Thanks for the quick reply.
I went and checked the format for the log file and it is FORMAT_CSV as shown in the line below
#define LOG_FORMAT FORMAT_CSV /* options: FORMAT_CSV, FORMAT_BIN */
(I copied this from the config.h file)
I have attached the a sample of the log file for reference as to what I am talking about. According to the megalogger.ino file, I believe that the three items that should be represented in this log file are as follows:
(I hope it is safe to assume that each of these should show up in their own column? A, B, C respectively?)
logOBDData(PID_RPM);
logOBDData(PID_SPEED);
logOBDData(PID_THROTTLE);
dataCount = 3;
As you can see below I took a copy of data from the logger file, it appears that the log file is logging incorrectly.
8415 F020 -756 736 18248
0 F021 207 -79 37
56 100 0
13 100 128
14 120 128
15 120 0
12 131 -28181
32 131 -27139
31 10C 719
44 F020 748 1492 16944
0 F021 -749 249 -36
37 10C 720
52 10D 0
38 10C 720
50 10D 0
12 111 14
13 F020 -2688 -240 18828
0 F021 -139 -8 45
36 110 42
14 10C 719
51 10C 719
PID_RPM is logging as 2 digit number. Even if the scaling was off....there seems to still be a problem as my truck is Diesel and some of the values would be over the red-line by 2k RPM.
PID_SPEED seems to be logging as HEX in most cases.
PID_THROTTLE seems to be all over the place, sometimes logging GPS coordinates, sometimes Logging what appears to be the RPM, sometimes logging what appears to be the throttle position (that never seems to change on the main screen), and sometimes it appears to be the temperature value (that also never seems to change on the main screen).
Regarding trying to plug it in at different times, I have tried to plug this in at different stages in of when I turn the truck on, before I put the key in the ignition, before starting, and also after starting. I have left plugged in (while running into the store for example.) and turned the truck off, then back on after leaving the store.
I guess I missed that the TFT display was on D0, D1. Thanks for the clarification!
Again, thanks for the work on this project; and the help! chevyplowman
I went and checked the format for the log file and it is FORMAT_CSV as shown in the line below
#define LOG_FORMAT FORMAT_CSV /* options: FORMAT_CSV, FORMAT_BIN */
(I copied this from the config.h file)
I have attached the a sample of the log file for reference as to what I am talking about. According to the megalogger.ino file, I believe that the three items that should be represented in this log file are as follows:
(I hope it is safe to assume that each of these should show up in their own column? A, B, C respectively?)
logOBDData(PID_RPM);
logOBDData(PID_SPEED);
logOBDData(PID_THROTTLE);
dataCount = 3;
As you can see below I took a copy of data from the logger file, it appears that the log file is logging incorrectly.
8415 F020 -756 736 18248
0 F021 207 -79 37
56 100 0
13 100 128
14 120 128
15 120 0
12 131 -28181
32 131 -27139
31 10C 719
44 F020 748 1492 16944
0 F021 -749 249 -36
37 10C 720
52 10D 0
38 10C 720
50 10D 0
12 111 14
13 F020 -2688 -240 18828
0 F021 -139 -8 45
36 110 42
14 10C 719
51 10C 719
PID_RPM is logging as 2 digit number. Even if the scaling was off....there seems to still be a problem as my truck is Diesel and some of the values would be over the red-line by 2k RPM.
PID_SPEED seems to be logging as HEX in most cases.
PID_THROTTLE seems to be all over the place, sometimes logging GPS coordinates, sometimes Logging what appears to be the RPM, sometimes logging what appears to be the throttle position (that never seems to change on the main screen), and sometimes it appears to be the temperature value (that also never seems to change on the main screen).
Regarding trying to plug it in at different times, I have tried to plug this in at different stages in of when I turn the truck on, before I put the key in the ignition, before starting, and also after starting. I have left plugged in (while running into the store for example.) and turned the truck off, then back on after leaving the store.
I guess I missed that the TFT display was on D0, D1. Thanks for the clarification!
Again, thanks for the work on this project; and the help!
chevyplowman 