So it seems to me [correct me if I'm wrong], that some people are using their fusion brain to read sensors in their car, readings that you'd usually do with an OBDII device.
The problem with this is that there's a huge corpus of excellent OBDII tools out there that you can't use with an FB setup like this, which kinda sucks.
I've been working on a pluggable OBDII simulator, and just finished a plugin that solves this problem. Using it, your Fusion Brain's output is presented as an OBDII device that you can use standard OBDII tools to work with.
It's actually a dbus plugin, primarily intended to work with kev000/tripzero's fbd
in this thread. The way it works, you run trip's fusion brain daemon to listen to the FB and spit out dbus signals, then run my simulator configured to listen to those signals and present OBDII data.
The configuration for it looks like this:
Code:
# obdsim dbus plugin sample config file
# We specifically listen to only one member from one path from one
# interface
# The message for the member-path-interface tuple must come in as two
# numbers. The first is mapped to a PID using this file. The second
# is a real or integer that is the actual value.
# bus can be "session" or "system"
bus=session
interface=org.openice.test
path=/org/openice/test/testsignal
member=SomeSignal
# Some sample mappings.
# Each mapping is of the form:
# map {dec number} -> {hex PID}
# Map 22 to engine temperature
map 22 -> 0x05
# Map 34 to airflow mass
map 34 -> 0x10
Obviously you'll need to modify it to work with dbus, perhaps if trip or someone else could post a sample config written to work with fbd, that would be great. Unfortunately, I don't have a fusion brain so I'm not able to actually test this in a real environment, but the software is working fine with trip's test program he wrote for testing helping me with this plugin.
At this stage, it's still orientated heavily towards technical users, for which I apologise [although it occurs to me that most FB users are probably smarter than your average bear anyways :-)]. But what you need to do is check out from svn, build with dbus enabled, write a config file for fbd [almost everyone will use the same config file for this; which is why I suggested a smart person might be able to post a good config in this thread]. Quick and easy instructions to svn checkout and build:
Code:
svn co svn://svn.icculus.org/obdgpslogger/trunk obdgpslogger
mkdir obdgpslogger/build
cd obdgpslogger/build
cmake -DOBD_ENABLE_DBUS=On ..
make
Then to run it:
Code:
cd ../bin
./obdsim -g DBus -s ../src/sim/generators/dbus/dbustest.simconf
Instead of that sample config, you should use an fbd one, of course.
So that's still pretty techie, but if anyone has a chance to try it, please post in this thread with details, information, advice, general abuse, all that good stuff.
Gary (-;