PLX WIFI and Dash Command

[Caffeine Fiend]

99% certain it's different from Gen I to Gen II, but hell it's worth a shot

[Yeldarb]

Hell yeah....

[SarcasticOne]

Thanks Sam. You use Torque, right?

There is a PID for fuel pressure. But may be different for the Mazda.

Yeah, torque
The fuel pressure pid it comes with doesn't work, this one seems to

Sent from my Galaxy Nexus using Tapatalk

[Nexus]

Dashcommand should read and log just about anything. Mine does. Here's the thing though : PC software compatibility and hardware flexibility is good. IOS iphone/ipad is not. I wouldn't use an IOS device or android for this. There's too many points of failure that won't have a work around.

Bluetooth and wireless OBD is shit - high latency, low bandwidth. 802.11 should be better but a direct USB connection is best.

Happy to have a look and see if I can help if still having trouble. I've been logging fuel pressure for ages, I'm surprised people are STILL having trouble finding what they need to do it.

---------- Post added at 06:31 PM ---------- Previous post was at 06:25 PM ----------

Happy to demonstrate a fully functional dashcommand doing everything that is being stated here that it can't do.
Fuel pressure? Boring! There is very little I can't read from the ECU. 90% of the mazda proprietary PID, which includes things like air conditioning compressor duty cycle.
Want more still? Get a professional license.

I bluntly don't believe that the product is as poor as suggested below, because I've been using it and it does everything it is advertised to. It's had maybe one minor bug that I've encountered in a couple of years and more of ownership.

It's not perfect but it is very capable and I think some of the users here probably need to read the manuals more before throwing the towel in

[SarcasticOne]

for those of us just wanting basic real time (every 0.3s for me..) they work pretty well
i can get enough data from it to see what car is doing

[Nexus]

0.3sec is pretty good for a bluetooth interface. You'll find the more bandwidth you try to consume (more logging) - for me ALL the interesting stuff leads to latencies closer to a second and more over bluetooth. That DOESN'T include air conditioning duty cycles and the like

802.11 I would expect to be a little problematic to set up. MAC addresses, promiscuous capabilities, lots of things about your config could impact it. I'd suggest seeing if you can get it working with an alternative to the ipad first - something more flexible such as a pc. Just checking that the WAN works appropriately and the device can communicate over WAN. Then try the ipad, which should be simpler really.

I'm not thrilled by the quality of ipad applets I've needed to setup in production configurations. People like having their security cameras accessible from their ipad but the compatibility with all the different devices out there is pretty shit, even though there is a supposed standard for these things.

Similarly... anyway, not an ipad user myself, apart from minimal IOS support for work. Although ipad applet quality seems to be hit and miss, I really don't expect dashcommand to be anywhere near as shit as it sounds in discussion. I'd be interested in testing 802.11 interface, myself.

[Yeldarb]

UPDATE FOR APPLE.

[Reedy]

One thing this thread didn't answer: Fuzzycar does log fuel pressure in my Gen II. But it doesn't store log files, you need to view it from within the app itself which isn't ideal, but it's the only iPhone app ive found that logs fuel rail pressure.