Thread: Cannot initialize DBUS obdsim generator

I'm looking for a way to receive a dbus signal from obdgpslogger every time it registers a new entry into the log so that I can display it on screen

OK, I'm confused; could you exactly explain your situation? Are you in a car with an OBDII device, using obdgpslogger to read it? And then you want obdgpslogger to signal on dbus whenever it sees a new value?

If so... you don't want to use OBDSim for that; obdgpslogger already does it, all on its own. Check obddbus.c for the exact interface/path/member and the actual message

Gary (-;

Originally Posted by chunkyks

OK, I'm confused; could you exactly explain your situation? Are you in a car with an OBDII device, using obdgpslogger to read it? And then you want obdgpslogger to signal on dbus whenever it sees a new value?

I am building a GUI that will be able to send/receive DBus messages to different areas of the OS. One of the areas deals with reading the OBD information and displaying it on screen. I think that obdgpslogger would help me out in achieving this really well.

If so... you don't want to use OBDSim for that; obdgpslogger already does it, all on its own.

The only reason why I want obdsim to work right now is because the pc isn't hooked up to the car yet, so I would like to simulate some DBus data for obdgpslogger to consume and then throw a DBus signal that my GUI can pick up.

Hope this makes more sense.

Ooooooooo

In that case, just use "obdsim -g Random -o"

Assuming obdgpslogger was build with dbus enabled, that should be all you need to actually generate dbus signals from obdgpslogger. If all you want to see it *something* output from obdgpslogger, then that should be sufficient

Gary (-;

Or, if you want to see some more realistic figures, download http://icculus.org/obdgpslogger/down-to-vista.db and use

Code:

obdsim -g Logger -s down-to-vista.db

You can also use obdgui to connect to the pty that obdsim announces, and verify that your dbus signal reader is reading the right thing by checking that obdgui and your gui say the same thing.

Gary (-;

I'm sorry if I wasn't so clear from the start. I get ahead of myself sometimes.

I just tried both examples and I didn't pick anything up in qdbusviewer or dbus-monitor. I didn't find any output errors either. Is there anything else I should try? I am positive I compiled obdgpslogger with both DBUS switches on, but I'm going to try that again and get back to you.

I just tried both examples and I didn't pick anything up in qdbusviewer or dbus-monitor. I didn't find any output errors either. Is there anything else I should try? I am positive I compiled obdgpslogger with both DBUS switches on, but I'm going to try that again and get back to you.

I haven't yet implemented introspection, so in qdbusviewer you won't see "obdgpslogger" in the "services" panel on the left, it'll be one of the :somenumber ones.

In dbusmonitor, make sure you're looking at the system bus, /a la/

Code:

dbus-monitor --system

Of the two dbus switches in cmake, the important one for this is "OBD_ENABLE_DBUS"; the other is just to enable the dbus generator for obdsim. I would suggest a rebuild from scratch, to be sure:

Code:

cd obdgpslogger-top-level-svn-checkout
rm -rf build
mkdir build; cd build
cmake -DOBD_ENABLE_DBUS=ON ..
make

Also at risk of sounding ridiculous, what OS are you running? All this should work under cygwin ["should" as in "I haven't tried it myself"], but probably not mingw/msys [yet]. I know it works on OpenSolaris 2009.06 , ubuntu 8.10 and 9.04, and OSX 10.4 and 10.5.

Gary (-;

I just tried re-compiling/installing and nothing changed. I found the entry in qdbusviewer, but it only produced an error:

Error: Cannot introspect object / at :1.87: org.freedesktop.DBus.Error.AccessDenied (Rejected send message, 1 matched rules; type="method_call", sender=":1.86" (uid=1000 pid=11297 comm="/usr/bin/qdbusviewer ") interface="org.freedesktop.DBus.Introspectable" member="Introspect" error name="(unset)" requested_reply=0 destination=":1.87" (uid=1000 pid=11333 comm="obdgpslogger --serial /dev/pts/3 --db ./obdgpslogg")))

My carpc has a custom Ubuntu Jaunty 9.04 i386 build and my desktop is also a Jaunty version but in AMD64.

Originally Posted by bkuri

I just tried re-compiling/installing and nothing changed. I found the entry in qdbusviewer, but it only produced an error:



My carpc has a custom Ubuntu Jaunty 9.04 i386 build and my desktop is also a Jaunty version but in AMD64.

I don't think chunky_ks has introspection working yet... Your best bet would be to watch for the signals coming through dbus-monitor --system.

Originally Posted by kev000

I don't think chunky_ks has introspection working yet... Your best bet would be to watch for the signals coming through dbus-monitor --system.

Eureka! I totally forgot to check with dbus-monitor... Thanks man
Now I just need to learn how to grab DBus events without depending on introspection... Any clues?