New Centrafuse Update, manual install with Debug OBDII version for testing

**midiwall** · 03-28-2007, 01:08 PM

And...

OBD reconnected 3/3 times after a resume from hibernate!!! YAY! I did see it _disconnect_ once after having been reconnected for about 1 minute, but it never happened again during the rest of the hour(ish) of driving.
MIL _indicator_ is fixed. (see next point)
MIL error codes are slightly broke. I had thrown two codes and CF only showed the first one.

Side points...

After this update, CF fired up in "First time" mode and wanted a registration. My 1.11 registration code wouldn't work, but I think I saw in another thread that this is a known. I haven't been to the FM site yet to see if there's a new reg code.

Ideas:

It'd be nice to be able to add our own definitions for Error Codes and modify the current ones. Many manufacturers have their own codes and/or slightly redefine the standard ones. Are these in an Access table?
I think it'd be cool to have an option to autoswitch to the OBD module when/if a MIL code is thrown.

THANK YOU DAVID!

**veetid** · 03-28-2007, 03:23 PM

Great news!

Those are some good ideas, I will look into them after I get everything fixed...

I have re-enabled all the sensors now, but added some new functionality to OBDII...

you can now click each sensor and set it to disabled and it will remember after you restart, etc...

this way it will only query the sensors you want it too...

I did overlook the get supported PID code and it looks right, but atleast in the next version if it isn't working a temp fix will be to disable the sensors causing the issue until I fix it...

I will also check on it not getting all the codes...

so I will wrap this up and get onto fixing that XM issue...

also the next release will have a brand new navigation engine, completly different... it includes street names in 3D mode, visible terrain changes in 3D mode, much improved routing engine, support for most all GPS receivers in NMEA or SiRF mode, much better...

one problem though is I might not be able to use the updater to send out the new navigation engine, but it won't change for atleast a year now... It's hot of the press...

It's over 600 new files and folders... I know you will be really upset if I don't get the updater to work and I will see if it works right, but it's so many files and folders...

An upgrade this large might have to warrant a new install, but I'm tracking down all the issues finally...

I will post 1.12, then we will debug XM!

david

**Nola111** · 03-28-2007, 03:34 PM

Originally Posted by veetid

I will post 1.12, then we will debug XM!

david

YES!!!!!!!!

**ComradeJew** · 03-29-2007, 03:08 AM

Yay! Glad to see the OBDII issue has been fixed - I was away gambling in Vegas the past few days - but now I am back and am itchin' to get my hands on the new OBDII plugin. Is the whole thing (the one that lets you disable PIDs) available in the update, or do I have to wait for 1.12?

**midiwall** · 03-29-2007, 09:30 AM

Originally Posted by ComradeJew

Is the whole thing (the one that lets you disable PIDs) available in the update, or do I have to wait for 1.12?

You'll need to wait for the 1.12 release. The update here is a stripped-down test version that David put together to chase a theory or two.

Soon!

**Dj-[NRG]** · 04-13-2007, 02:27 AM

just installed my OBDII cable, but don't get any readouts in CF...
the leds on my device are flashing once i connect it in CF, but everything stays N/A...
my device has no problem connecting...

Greetz

Dj NRG

**midiwall** · 04-13-2007, 10:00 AM

Originally Posted by Dj-[NRG]

just installed my OBDII cable, but don't get any readouts in CF...
the leds on my device are flashing once i connect it in CF, but everything stays N/A...
my device has no problem connecting...

If you're using this test release then the only field that will be updating is SPEED. David disabled everything else for now.

Can you confirm that you don't see anything in SPEED? Also, if CF shows "CONNECTED" and the light is green, then it's happy and has "talked" to your OBD module. Which module are you using?

As another test, you could try throwing a MIL error and see if the OBD interface picks it up. Depending on how comfortable you are under the hood of your car, disconnecting the MAF/AFM is a quick way to usually throw a couple.

**Dj-[NRG]** · 04-13-2007, 04:33 PM

sorry, now I saw I am using 1.1 instead of the 1.12 pre release...

wil download the "test" release and install it tomorrow, and let you know what it does...

I am using the ELM 327 from obd2allinone...

Greetz

Dj NRG

**midiwall** · 04-13-2007, 05:57 PM

Originally Posted by Dj-[NRG]

sorry, now I saw I am using 1.1 instead of the 1.12 pre release...

wil download the "test" release and install it tomorrow, and let you know what it does...

Ahhh... yeah, there are a few known issues, hence the test version. Give the test version a try and you should get better results, at least in the sense of it connecting, reconnecting and staying connected.