Now with "wifi" support!

**chunkyks** · 06-12-2011, 04:34 PM

Now with "wifi" support! Well, it's not specifically WiFi, it's just a network socket, you'll have to provide your own WiFi. But anyways:

OBDSim:

Code:

chunky@mills:~/src/obdgpslogger$ ./bin/obdsim -k 34000
SimPort name: Port 34000
Successfully initialised obdsim, entering main loop
Socket connected: Port 34000
10.000473 seconds. 1 samples, 2 queries. 0.10 s/s, 0.20 q/s
Received EXIT via serial port. Sim Exiting
chunky@mills:~/src/obdgpslogger$

Telnet:

Code:

chunky@mills:~/src/obdgpslogger$ telnet localhost 34000
Trying ::1...
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
0100
0100

41 00 FF FF FF FF
>ATI
ATI

ELM327 v1.3a OBDGPSLogger
>exit
exit
Connection closed by foreign host.
chunky@mills:~/src/obdgpslogger$

Gary (-;

**cail** · 08-31-2011, 02:40 AM

Hey, that will make debugging so simple (sometimes its inconvenient to setup virtual ports).
I've actually used com2tcp to achieve the same effect.

Will this be available in windows build btw?

PS. Had no chance to say _big thanks_ for obdsim - really good piece of software. Its great you've shared it in community. I'm using it often in development of my hobdrive piece of software (/hobd - extended OBD2 based trip computer for WinCE/PocketPC/WinMobile/Windows)

**chunkyks** · 08-31-2011, 11:04 AM

I'm glad you like it :-D

I, erm, I'm not sure if it'll go into the windows build; does windows support good old-fashioned BSD sockets? I feel like I remember it having done so in the past [Yay Trumpet Winsock, back in the day!]
I imagine it'll magically build now I think about it: I'll give it a try later.

Gary (-;

**cail** · 08-31-2011, 01:25 PM

Originally Posted by chunkyks

does windows support good old-fashioned BSD sockets?

I've thought obdsim for windows uses cygwin or mingw libs to build up. Believe cygwin should contain bsd socket api port. Im not sure however.

**chunkyks** · 09-02-2011, 10:54 AM

The "obdsimwindows" download is built using mingw/msys [it's actually cross-compiled on a Linux machine, when the real bundle is baked, and I futz around under msys on windows while developing].

It *should* all build under cygwin too, but msys makes a more intuitively appealing binary. [msys is more like a native windows app, making native windows library calls. With cygwin, your code's library calls are all posix, and cygwin knows how to proxy those to "real" windows library calls]

Anyways. I tried building obdsim for windows with the socket generator last night, but it turns out I'm doing a bunch of stuff that was assuming posixy bits further down the stack. Which is totally my bad, but it does mean it's a lot more effort to make it work properly :-(

Sounds like, at least in the immediate term, com2tcp is totally the way to go :-/

Gary (-;

**cail** · 09-05-2011, 01:28 AM

I've just took a standard cygwin, made some configuration hooks, and viola!

I've packed it with all the required cygwin libs (so hope it can work even without cygwin installed)

http://hobdrive.com/download/obdsim-latest-cygwin.zip

It works with raw socket, and even packed with fltk gui!

Thanks once more for such an impressive stuff.

Another question. Is there any easy way to make fltk UI show custom (dynamically changed) PIDs?

**@pozuelog** · 06-26-2012, 04:07 AM

Hi! I'm using OBDSim to design a free mobile service for remote real-time logging. I'm using the bluetooth interface, but I would like to use the Wifi too.

I've installed obdsim on a VM with Ubuntu 10.04. The obd-gps logger version is 0.16. When I try the command obdsim -k port the program says that -k is an invalid option. ¿Where is the problem?

Thanks.

Jorge