Permanent Traction Override Switch

[86Nanny]

Originally Posted by stugray

So does yours get the same results as the pedal dance?
Or is it just the same as the VSC/TC buttons.

Convince me that it works by explaining it just a bit.

I see the bare minimum that it would take to build one (assuming all interfaces are on the ODBII connector):
Arduino - $35
OBD Shield - $50
OBD passthru cable - $25
Case and associated hardware - $10

So total in hardware costs = $125

UNLESS it can work from a Droid phone and an ELM327, then it is just $10.

@stugray Sure! I don't mind explaining. The unit does achieve the same results as the pedal dance and isn't just Trac/VSC disabled.

Your list/cost is about dead on. The only difference is I'm kinda picky so I tend to custom make various things such as the passthru cable in order to avoid clearance issues and use only what the unit needs. I'll be able to hammer down a final on everything soon.

Edit: And it's definitely not an ELM327 unit.

[stugray]

Originally Posted by 86Nanny

Edit: And it's definitely not an ELM327 unit.

But if the transactions are standard OBD, then the ELM327 should be able to execute those commands wouldnt it?

[86Nanny]

Originally Posted by stugray

But if the transactions are standard OBD, then the ELM327 should be able to execute those commands wouldnt it?

@stugray Yes there are some tasks a ELM327 chip could accomplish, but without having a custom coded 327 chip to handle submit & response transactions, you'll run into plateaus. I haven't looked into the Android ELM327 apps you mentioned to know how deep you can go, but at a chip level I know there are going to be limitations. The biggest issue will be filtering for responses from the network so your device knows when to continue communication/stay in sync. Most 327 chips the buffer will fill up too quickly to get what you need in time. The nodes in these cars are quite noisy.

If there is a particular app you are curious could achieve this, I'd be happy to take a look any give you my opinion.

[stugray]

Originally Posted by 86Nanny

The biggest issue will be filtering for responses from the network so your device knows when to continue communication/stay in sync. Most 327 chips the buffer will fill up too quickly to get what you need in time. The nodes in these cars are quite noisy.
.

Sounds like you are trying to build a Tactrix.
I have one of those too.

[86Nanny]

Originally Posted by stugray

Sounds like you are trying to build a Tactrix.
I have one of those too.

I'm not familiar with Tactrix, but I'll look it up to see what the similarities are.

EDIT: Just browsed the website. They are reflashing, I don't do any reflashing. At this moment I'm just targeting 1 system in the network so there isn't an advantage for reflashing yet. I have future ideas though that might have me on the reflashing path.

[Sammakko]

Originally Posted by Dustin

Not trying to thrash on your idea here, but seriously people, it's 3 seconds. With all the time and effort involved to make this a functional kit, even if it took only 5 minutes to install and only cost $30 for the kit, depending on how much you make an hour, you could do the 3 second feature over 1000 times before you would see a return on your "investment".

worth every penny lol

[stugray]

Originally Posted by 86Nanny

I'm not familiar with Tactrix, but I'll look it up to see what the similarities are.

EDIT: Just browsed the website. They are reflashing, I don't do any reflashing. At this moment I'm just targeting 1 system in the network so there isn't an advantage for reflashing yet. I have future ideas though that might have me on the reflashing path.

They can do a lot more than flashing.
They can also log data at high rate and make generic CAN Bus transactions.
It is essentially an Arduino with the CAN bus shield (and then some) already in one package for ~$150 ea.

[robot]

I think the Tactrix a more powerful microcontroller (but that is admittedly splitting hairs).

The ELM327 chips are ok for doing some OBD II transactions. Most of the better stuff is using scantool.net chips (STN1xxx). They accept all the AT commands like an ELM chip but also add some other features (for the very curious: http://www.scantool.net/scantool/dow..._vs_elm327.pdf)

[mig86]

http://www.ft86speedfactory.com/mig-...ator-2007.html

[codesplice]

Originally Posted by mig86

http://www.ft86speedfactory.com/mig-...ator-2007.html

Any chance of a model which incorporates an OBD pass-through, so that I could still run OBD-based telemetry stuffs?

It sounds like I could just unplug that device after the "pedal dance" mode is engaged, but I'm not sure that repeatedly fumbling with the 86's notoriously-flaky connector is really a great idea - plus I'm not sure that would actually be easier than doing the Pedal Dance the manual way.

Not knocking it, just genuinely curious.

[Hyper4mance2k]

Ohhh competition... I can't wait to give you my hard earned money. This car is such a hindrance to my ability to feed myself!!!

[stugray]

Or you can just get an OFT and it is capable of the pedal dance mode now.

[mig86]

You can buy a two way adaptor on ebay (y cable) for about $5. I would do this because the factory plug is not really robust and the you can tuck the device away (unclip the factory plug and secure behind the dash). Now you have a more robust, replacable plug for other items.

This will in no way interfere with other OBD devices, so keep your telemetry.

No need to unplug, its set and forget. Can't see how that could be 'harder' than the manual way.

[mig86]

Originally Posted by stugray

Or you can just get an OFT and it is capable of the pedal dance mode now.

Yes, difference is that this requires no user input, automatically enter the mode each time the ign is cycles. Also does not need full warm up, just idle drop back.
Still, great feature on the OFT for those with one.