pcmhacking.net

I think its just a competing interface instead of the one this thread is actually about.

An EXPENSIVE competing device at $850+.
Thanks, but no thanks, I'll pass!

Mike

Tazzi wrote:Priority is for the developers at the moment since we have had alot of requests from GM and Ford devs.

Breaking free of PC applications has actually been a lot harder then most people realize for J2534 developers, since there is not a single J2534 tool on the planet which is designed to also work with smartphones or any non-PC based system.

Working with Jason has been a breath of fresh air. He has done more for us in the last few months than any other scan tool developer has in years.

Highly recommend everyone gets onboard. PCMTEC is going to push the OBDX tool hard so this will hopefully fund even more great things from Jason and Pete.

I don't often give praise but in this case it is well and truly deserved.

Keep up the great work and thanks for taking the time to update firmware to benefit our application!

MudDuck514 wrote:An EXPENSIVE competing device at $850+.
Thanks, but no thanks, I'll pass!

Mike

The price point of the OBDX is on point. Even if they raise prices 25% it's still highly competitive against anything else on the market.

The fact they are willing to work with other developers and open up their driver source code to allow developing custom applications makes them one of a kind for the money they are charging.

At the price of the obdx you can split the tuning industry into 3 segments with it remaining profitable for all 3.

Hardware with low level software drivers (J2534, gmlan etc) eg obdx

Tuning software/mapping/custom roms (eg what we do at PCMTEC)

Tuning itself, eg the tuning workshops that do the hard work of finding customers and making their cars work by doing custom tuning.

This means each segment can specialise instead of spreading themselves thin and doing each one at an average level.

antus wrote:I think its just a competing interface instead of the one this thread is actually about.

I think so too. Don't really see what was special about that specific one?

rolls wrote:Working with Jason has been a breath of fresh air. He has done more for us in the last few months than any other scan tool developer has in years.

Same back to you mate!

MAUI template app is now also going to support direct USB connection on Android devices!

The default android USB CDC driver works with OBDX devices, this will easily be the fastest option available which we will encourage developers to use.

Unfortunately it is not an option for iPhones, but still pushing forward with solutions there.

rolls wrote:

MudDuck514 wrote:An EXPENSIVE competing device at $850+.
Thanks, but no thanks, I'll pass!

Mike

The price point of the OBDX is on point. Even if they raise prices 25% it's still highly competitive against anything else on the market.

snip

I wasn't saying the OBDXPro is the expensive tool ( I bought one just to help support them) but the OTHER one at $850.00

Mike

While waiting on answers for one thing, its straight onto the next.
I have been trying to get a Ford AU Falcon (Aussie Ford) EEC-V ECU to be communicating on the bench using PWM. I know its powered up, since its outputting the reference 5v on the PWM negative line, but it just never broadcasts any information and does not respond to any diagnostic requests.

I have attached a photo which has the 104 connector pinout and highlighted the pins of interest. I do not have FEPs connected, but it does not seem to make a difference.

Currently the method of testing out PWM is basically having a J2534 tool connected and sending a PWM message so that our tools can decode to verify its timing is correct. Then sending back a message and verifying the J2534 tool picks it up. I have to have the AU ECU connected since it provides the 5v pullup on the PWM negative line which is needed for communication. This kind of development works but is not ideal, would much rather real life ECU responses, traffic, noise ect which then allows us to use dealership tools for testing out the J2534 compliance.

If anyone spots something I might have missed on that sheet, do let me know!

I don't have pinouts handy, but you should be right to get PWM out of it with ka power, ign, and ground. Maybe your ECU is faulty?

Cheers, Jason

galapogos01 wrote:I don't have pinouts handy, but you should be right to get PWM out of it with ka power, ign, and ground. Maybe your ECU is faulty?

Cheers, Jason

That’s basically what I have done. I have two ecus, both doing the same thing.
Im not sure if there’s some specific command I suppose to send to the ecu to start a diagnostic session?

There’s next to zero information online about the AU falcon ecus in regards to diagnostics. Basically everything online is relating to tuning and links to the xcal3.

Iv sent a few questions out to a few gurus, hopefully someone has the answer. Or has a bench ecu+harness that’s known to be working to purchase.

Pwm also has a high speed mode (83.2kbps) used for programming, this is the part I want to ensure is rock solid which requires careful timing.