|
 |
10-31-2009, 04:27 PM
|
#1
|
|
Mod - OBDII GPS Logger forum
Join Date: Mar 2009
Location: Los Angeles
Posts: 401
|
New Release: 0.10
Version 0.10 (released 2009-10-31)
Logger, conf: Ability to adjust serial baudrate
Initial add of ftdi-pty proxy for systems without ftdi-sio
conf: Add ability to write config file back to disk
ftdipty can modify config file for obdgpslogger
Logger, conf: Ability to configure logfile name
Logger: Gracefully exit if a serial write fails
Logger,doc: Hotplug docs
Logger: cygwin compilation fixes
Sim: Don't build socket generator without getaddrinfo symbol
Logger: If obd device isn't available, exit [would log gps before]
Have fun, all
Gary (-;
|
|
|
|
|
|
Advertisement
|
Sponsored links
|
11-03-2009, 03:21 AM
|
#2
|
|
Newbie
Join Date: Aug 2009
Posts: 14
|
Doesn't compile with Cygwin:
Quote:
[ 92%] Building C object src/sim/CMakeFiles/obdsim.dir/simport.o
Linking C executable ../../../bin/obdsim.exe
CMakeFiles/obdsim.dir/simport.o:simport.c  .text+0xe): undefined reference to `_posix_openpt'
collect2: ld returned 1 exit status
make[2]: *** [../bin/obdsim.exe] Error 1
make[1]: *** [src/sim/CMakeFiles/obdsim.dir/all] Error 2
make: *** [all] Error 2
Uncommenting line 36 and commenting line 37 of \src\sim\simport.c makes the error go away.
Edit: Added screen shot of codes from my Lumina. I know for sure the codes are P0300 and P1406, I guess you can sort of see one of them?
Last edited by dents; 11-03-2009 at 03:45 AM.
Reason: Added screen shot
|
|
|
11-03-2009, 12:30 PM
|
#3
|
|
Mod - OBDII GPS Logger forum
Join Date: Mar 2009
Location: Los Angeles
Posts: 401
|
Quote:
Uncommenting line 36 and commenting line 37 of \src\sim\simport.c makes the error go away.
Yeah, I'm aware of that. I need to check for the posix_openpt symbol. The insulting bit is that posix_openpt is available in the header, and the other necessaries [eg posix_grantpt] are just fine. It's just that the symbol isn't publicly available in the cygwin C library itself.
You found the fix I'm going to use; the code will look like
Code:
#ifdef HAVE_POSIX_OPENPT
int fd = posix_openpt(O_RDWR);
#else
int fd = open("/dev/ptmx", O_RDWR);
#endif //HAVE_POSIX_OPENPT
Just gotta set up the build system to do it.
Quote:
Edit: Added screen shot of codes from my Lumina. I know for sure the codes are P0300 and P1406, I guess you can sort of see one of them?
Heh, that's the svn that I only committed last night. Among other things, it doesn't gracefully handle multiple ECUs...
You're getting NO DATA; that's what happens when the OBD device literally responds with the string "NO DATA". Please could you run obdgpslogger with "-l seriallog.txt" [dash little-ell] and post the seriallog?
Thanks,
Gary (-;
|
|
|
11-04-2009, 12:09 AM
|
#4
|
|
Newbie
Join Date: Aug 2009
Posts: 14
|
Zipped it up in case the browser decides to get creative with a .txt file that has binary contents. I did svn sync and rebuilt just now, then ran it.
|
|
|
11-04-2009, 12:34 AM
|
#5
|
|
Mod - OBDII GPS Logger forum
Join Date: Mar 2009
Location: Los Angeles
Posts: 401
|
OK, two things:
1) Please could you do an svn update [and probably an "svn revert src/sim/*", to back out your modifications], and see if it compiles on cygwin for you now? I'm explicitly checking for posix_openpt in the build system, and using open("/dev/ptmx") if that's not available.
2) Also, do an svn update; I *was* sending "0300" [ie mode+cmd], which is incorrect; mode 0x03 does not need a cmd. Perhaps that will fix the problem? If not [for that matter, even if it does], please could you upload a fresh seriallog?
Hope all that helps,
Gary (-;
|
|
|
11-04-2009, 01:59 AM
|
#6
|
|
Newbie
Join Date: Aug 2009
Posts: 14
|
Reverted src/sim/* and everything compiles in Cygwin now. Did svn update but it's still getting NO DATA. Edit: Whoops ran obdgpslogger.exe instead of ./obdgpslogger.exe ... new seriallog now. Edit #2: Hah! Bluetooth port shut down before I ran the command and I didn't notice. Re-ran again and now it's printing out the codes:
Quote:
Opening serial port /dev/com10, this can take a while
Successfully connected to serial port. Will log obd data
Your OBD Device claims to support PIDs:
PID: [column] human_name
00: [unknown] PIDs supported 00-20
01: [unknown] Monitor status since DTCs cleared
03: [fuelsys] Fuel system 1 and 2 status
04: [load_pct] Calculated LOAD Value
05: [temp] Engine Coolant Temperature
06: [shrtft13] Short Term Fuel Trim - Bank 1,3
07: [longft13] Long Term Fuel Trim - Bank 1,3
0B: [map] Intake Manifold Absolute Pressure
0C: [rpm] Engine RPM
0D: [vss] Vehicle Speed Sensor
0E: [sparkadv] Ignition Timing Advance for #1 Cylinder
0F: [iat] Intake Air Temperature
10: [maf] Air Flow Rate from Mass Air Flow Sensor
11: [throttlepos] Absolute Throttle Position
13: [o2sloc] Location of Oxygen Sensors
14: [o2s11] Bank 1 - Sensor 1/Bank 1 - Sensor 1 Oxygen Sensor Output Voltage / Short Term Fuel Trim
15: [o2s12] Bank 1 - Sensor 2/Bank 1 - Sensor 2 Oxygen Sensor Output Voltage / Short Term Fuel Trim
1C: [obdsup] OBD requirements to which vehicle is designed
2 trouble codes set [MIL is off]
Error: P0014
Error: P0600
Last edited by dents; 11-04-2009 at 02:13 AM.
|
|
|
11-04-2009, 02:14 AM
|
#7
|
|
Mod - OBDII GPS Logger forum
Join Date: Mar 2009
Location: Los Angeles
Posts: 401
|
Code:
>0100
NO DATA
>0101
NO DATA
That makes no sense at all.
Thus, I suggest you check that the OBD dongle is plugged in properly and hasn't wiggled loose.
Gary (-;
|
|
|
11-04-2009, 02:15 AM
|
#8
|
|
Mod - OBDII GPS Logger forum
Join Date: Mar 2009
Location: Los Angeles
Posts: 401
|
I'm really pleased that it builds on cygwin now, though. Of course, I'd also like to know if it actually *works*, but building is a good start :-)
Gary (-;
|
|
|
|
Sponsored links
|
|
Advertisement
|
|
11-04-2009, 02:16 AM
|
#9
|
|
Newbie
Join Date: Aug 2009
Posts: 14
|
Indeed! See above post, I edited it twice
|
|
|
11-04-2009, 02:20 AM
|
#10
|
|
Mod - OBDII GPS Logger forum
Join Date: Mar 2009
Location: Los Angeles
Posts: 401
|
Getting there! Sorry this is so difficult, I really appreciate your patience on the topic :-)
Also, could you upload another seriallog, [for -p, with the error output]? Those errors aren't the same as the ones you said you know they should be... Which may be an artifact of some other changes I made earlier this evening. Lots of development has gone on tonight, and I'm started to get tired.
Thanks,
Gary (-;
|
|
|
11-04-2009, 02:28 AM
|
#11
|
|
Newbie
Join Date: Aug 2009
Posts: 14
|
Realizing that "binary data" in the log is just \n, stopping with the .zip stuff. The codes come from a commercial scanner, so I assume they are correct.
|
|
|
|
Sponsored links
|
|
Advertisement
|
|
| Thread Tools |
|
|
| Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 11:42 PM.
| |