Forum >Replies by sbirdranch
Replies （20）
- You Reply: I changed the class back to COBD and am getting the same thing as Matt. It seems to be more reliable about the connections, but the logic that is forcing the reconnect (error count) seems to be goofed up.
I get one good read of the tachometer pid and it resets.
Sb.
ps. I pulled the code 30 minutes ago. - You Reply: Stanley,
I just pulled the code from GitHub and you have again pushed a change that has the COBDI2C library reference.
Sb. - You Reply: 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. - You Reply: Stanley,
I just pulled your latest update to megalogger.h. It now compiles. I see from the change log that you did other modifications, but I have not had time to test for improvements as it relates to the code being used with Kit#3.
Maybe later tonight or tomorrow I can provide that feedback.
Sb. - You Reply: Stanley,
I just pulled your latest update to megalogger.h. It now compiles. I see from the change log that you did other modifications, but I have not had time to test for improvements as it relates to the code being used with Kit#3.
Maybe later tonight or tomorrow I can provide that feedback.
Sb. - You Reply: Stanley,
I believe Mattt and I are both using your kits. I'm using your Kit#3.
I have all your current code pulled down from GitHub using TortiseGit. Your code is currently not what you think it is.
I suggest you review what you are pushing to the master branch and we can go from there.
Also...you code seems to have the display turned 180 degrees. That would suck for someone who has made a mount or case for the hardware.
Mattt,
When I get back from vacation I will be branching all of Stanley's code and starting a new development thread. I think with a little help from a phd friend, I can get it running. I can at least git something working with time. I had it modified so it would at least fire up if the OBD connector wasn't attached. - You Reply: Stanley,
I believe Mattt and I are both using your kits. I'm using your Kit#3.
I have all your current code pulled down from GitHub using TortiseGit. Your code is currently not what you think it is.
I suggest you review what you are pushing to the master branch and we can go from there.
Also...you code seems to have the display turned 180 degrees. That would suck for someone who has made a mount or case for the hardware.
Mattt,
When I get back from vacation I will be branching all of Stanley's code and starting a new development thread. I think with a little help from a phd friend, I can get it running. I can at least git something working with time. I had it modified so it would at least fire up if the OBD connector wasn't attached. - You Reply: I've gone from garbage to nothing with the newest libraries:( Although there is some concern that the OBD library is not right yet.
I was so hopeful as tomorrow I will be driving all day in the mountains and wanted to log it.
I'm going to wait before I go back to hacking the code. I had it modified so it would continue without the OBD connection and in fact you could ignore it and just log GPS. Maybe I can get that working again.
Sb. - You Reply: Sorry....I meant 'serial' not 'spi'.
I have tried it and although it compiles and such, the stability is still terrible. Hitting reset is like rolling the dice (hmmm second dice reference). You may or may not get the acceloramete. You may or may not get the gps, even when it is locked. I got it to recognize the OBD connection to my truck (2012 Chevrolet) but never got it to actively retrieve data. I would get one RPM reading and that was it.
If there is a difference OBD library, it doesn't seem to be on GitHub.
Preston. - You Reply: Sorry....I meant 'serial' not 'spi'.
I have tried it and although it compiles and such, the stability is still terrible. Hitting reset is like rolling the dice (hmmm second dice reference). You may or may not get the acceloramete. You may or may not get the gps, even when it is locked. I got it to recognize the OBD connection to my truck (2012 Chevrolet) but never got it to actively retrieve data. I would get one RPM reading and that was it.
If there is a difference OBD library, it doesn't seem to be on GitHub.
Preston. - You Reply: Matt / Stanley
The problem is that the class COBDI2C does not exist in the libraries on GitHub. I have pulled down the zip file from SourceForge and the entire repo from GitHub. No dice.
You can make it compile if you change the class back to COBD like it was in the previous version, but I don't know what other issues that might reveal.
I'm going to try it, as the OBD connector from Kit#3 is SPI not I2C. - You Reply: Matt / Stanley
The problem is that the class COBDI2C does not exist in the libraries on GitHub. I have pulled down the zip file from SourceForge and the entire repo from GitHub. No dice.
You can make it compile if you change the class back to COBD like it was in the previous version, but I don't know what other issues that might reveal.
I'm going to try it, as the OBD connector from Kit#3 is SPI not I2C. - You Reply: I just did the scorched earth approach and loaded everything from scratch.
I get the same error as you.
I'll try updating the individual file that Stanley suggested and see what I get.
Sb. - You Reply: I just did the scorched earth approach and loaded everything from scratch.
I get the same error as you.
I'll try updating the individual file that Stanley suggested and see what I get.
Sb. - You Reply: Jose, Thanks for the input. The SD card is being driven off the SPI connection and is piggy backed on the LCD display. Baud settings do not apply to SPI as far as I am aware. The display works, so ground is not an issue.
Matt,
I came to this project when I started looking at OBDII connectors to augment a gps logging tool I had created. I used just a gps to log data every 60 seconds while traveling across the US for 3 weeks. I was able to create some interesting graphics, kmls, and otherwise replay the entire trip. All I really wanted to do was add the throttle position sensor and some onboard logging so I didn't have to run my netbook. This kit#3 just sort of happened to have what I wanted. Turns out the software is not as robust as I thought. But that is what open source is for. I am rather bummed though. I am leaving for this next trip tomorrow and don't have time to beat it into submission. If I had more time, I'd ditch the code and write just what I want, coming back to the bigger picture later. But I don't. At this point I'm thinking about stripping out all the logging code, and adding a simple data logger (from Sparkfun) to UART4, but then I remember that the connection is flaky and I don't have time to address that either.
My coworker is interested in looking into our problems, but that will come over time. He knows the hardware/chipset side very well, and expects that we can do a lot to make this more robust with better code. - Topic: No SD Card being reportedYou Reply: Matt,
You were spot on. I made the changes you suggest and it is now finding the file. It creates the directory and increments file names as it should.
BUT - (Don't you hate those)..... The data in the log file is not ASCII like I expected. Is it encoded?
[code]
SU € q 43 ÀDj3
T p3 ðÈ^ù¢[email protected] ï €gD„3 ð<^ù¢[email protected]„3 €gD„3
ðXû™B㯧„3 ó È $ïF.4 ð§hù¢[email protected] à¨D.4
ðôû™B⯧Â.4 ó e $ïFô4 ðgrù¢[email protected]ô4 u €~Dô4
ð.û™B⯧Âô4 ó ¿ $ïF¾5 ð"|ù¢[email protected]¾5 õ @uD¾5
ðdû™B㯧¾5 ó ô $ïFn6 ø A PC ïÄ ŒÆn6 ù à qC ¤6 ðÁ†ù¢[email protected]¤6 ì @uD¤6
ð~ø™B㯧¤6 ó P ˜îFJ7 ø WD À!Å à€ÆJ7 ù €¢Ã FC ,Âr7 ð ù¢[email protected] X à¶Dr7
ð©ø™B㯧Âr7 ó ‡ ˜îF8 ð`šù¢[email protected]8 [ ŸD8
[/code]
It almost looks like it is a baud rate issue.
Following up on my idea that I was getting the wrong SD library. I have verified that the library in the Arduino program install folder takes priority over a duplicate library in the sketch folder. So where to put the lib's should also be highlighted in the much needed startup guide.
One final thing. I have duplicated your problem with the blank screen. I can make it happen, if I plug the OBD connector into the sensor board, THEN into the vehicle. Reset does nothing. It just glows.
So try this. Leave the OBD connector attached to the vehicle and unplug it from the sensor board. You can leave the I2C connector attached.
Breath once, cross your fingers and plug it back into the board. You know it is working when the display paints across at boot up.
Why does it do this? No idea. I think putting in some serial print lines and hooking to a laptop at startup might help diagnose where it is hanging.
Sb. - Topic: No SD Card being reportedYou Reply: Matt,
You were spot on. I made the changes you suggest and it is now finding the file. It creates the directory and increments file names as it should.
BUT - (Don't you hate those)..... The data in the log file is not ASCII like I expected. Is it encoded?
[code]
SU € q 43 ÀDj3
T p3 ðÈ^ù¢[email protected] ï €gD„3 ð<^ù¢[email protected]„3 €gD„3
ðXû™B㯧„3 ó È $ïF.4 ð§hù¢[email protected] à¨D.4
ðôû™B⯧Â.4 ó e $ïFô4 ðgrù¢[email protected]ô4 u €~Dô4
ð.û™B⯧Âô4 ó ¿ $ïF¾5 ð"|ù¢[email protected]¾5 õ @uD¾5
ðdû™B㯧¾5 ó ô $ïFn6 ø A PC ïÄ ŒÆn6 ù à qC ¤6 ðÁ†ù¢[email protected]¤6 ì @uD¤6
ð~ø™B㯧¤6 ó P ˜îFJ7 ø WD À!Å à€ÆJ7 ù €¢Ã FC ,Âr7 ð ù¢[email protected] X à¶Dr7
ð©ø™B㯧Âr7 ó ‡ ˜îF8 ð`šù¢[email protected]8 [ ŸD8
[/code]
It almost looks like it is a baud rate issue.
Following up on my idea that I was getting the wrong SD library. I have verified that the library in the Arduino program install folder takes priority over a duplicate library in the sketch folder. So where to put the lib's should also be highlighted in the much needed startup guide.
One final thing. I have duplicated your problem with the blank screen. I can make it happen, if I plug the OBD connector into the sensor board, THEN into the vehicle. Reset does nothing. It just glows.
So try this. Leave the OBD connector attached to the vehicle and unplug it from the sensor board. You can leave the I2C connector attached.
Breath once, cross your fingers and plug it back into the board. You know it is working when the display paints across at boot up.
Why does it do this? No idea. I think putting in some serial print lines and hooking to a laptop at startup might help diagnose where it is hanging.
Sb. - Topic: No SD Card being reportedYou Reply: Matt,
Thanks so much for the specifics. I'll give this a try.
This software and set of hardware needs a wiki in the worst way. I asked Stanley how we could contribute back to his project, but haven't heard anything. Seems he has/is at the World Maker Fair.
I'll let you know how this goes.
SB. - Topic: No SD Card being reportedYou Reply: Matt,
Thanks so much for the specifics. I'll give this a try.
This software and set of hardware needs a wiki in the worst way. I asked Stanley how we could contribute back to his project, but haven't heard anything. Seems he has/is at the World Maker Fair.
I'll let you know how this goes.
SB. - Topic: No SD Card being reportedYou Reply: I might have an idea of the issue. I will test it tonight.
The Arduino IDE ships with a copy of the SD library. The code from arduinodev for use with the kits they sell, has a newer version of the library. I'm going to try removing the stock library and putting this one in its place and see what happens.