PID's

[cking]

Is there a list of PID's in manual?

Sponsored

 

[Tank]

Is there a list of PID's in manual?

Don't you have a manual [MENTION=28002]cking[/MENTION]? :lol:

The update to Forscan allows resding of all PIDs. I think it also provides a description but I haven't had a chance to play around with it. When I do, I'll post what I find.

This might be helpful:
http://forscan.org/forum/viewtopic.php?f=6&t=3334

 

[mkonrad]

When you start going beyond PIDs (parameter identifiers) you get into EEC VII, where PIDs are just one of many interfaces. Ford has to support quite a bit of infrastructure for their electronic engine controls. There is a lot more to the ECU than PIDs.

The VCM II is the Ford diagnostic tool. It's pricey at around $1400, and can be purchased from Bosch or Rotunda, as well as dozens of Chinese knockoffs on ebay (which are always being deactivated). It also requires an $800 yearly subscription to keep access to Ford's technical support and enable the software. You can actually download Ford's software and manuals right there, but would need a license and VCM to use it effectively. Many of the PIDs can be invoked directly from the software to perform operations like triggering a diag function or turning on the diagnostic for the differential pump.
https://www.fordtechservice.dealerconnection.com/vdirs/wds/diagnosticsites/ids/mcs/support.asp

Ford also has a program called "OpenXC" where they expose many of the OBD2 readings to permit writing data extensions or plugins. Forscan uses different methods.
http://openxcplatform.com/

 

[PencilGeek]

Ford also has a program called "OpenXC" where they expose many of the OBD2 readings to permit writing data extensions or plugins. Forscan uses different methods.
http://openxcplatform.com/

With OpenXC, Ford obscures direct access to the OBD2 and CAN bus through the use of an API. They give you defined API calls like open_certain_module(...), read_certain_module(...), etc., but they don't tell you how to directly access the certain_module. I asked Ford if they would provide the direct access, through OpenXC with an non-disclosure agreement. They said they don't, and won't. So with OpenXC yes you can write extensions, but don't expect Ford to tell you the guts of what appears on the OBD2 or CAN busses -- they won't.

<bandwagon>
Personally I think that's very shortsighted of Ford. Without saying too much about myself, I've spent half my career reverse-engineering microprocessors and helping their competitors make clones. I think it would be better for Ford to provide the information with an NDA, than to refuse. With an NDA, they can tightly control what information gets out to the public. Without an NDA, Ford can only hope nobody has the time, skill, and resources to reverse-engineer it and publicize it. Without an NDA, Ford can't stop such a person from reverse-engineering and making the information public, but with an NDA to that same person, they can. So it's kind of shortsighted if you ask me.
</bandwagon>

With that said, I've already spent considerable time reverse-engineering the GT350R OBD2/CAN bus. I've got quite a bit of helpful information. I've got the tools and resources and I've already completed the task I set to accomplish. I only lack the time to provide complete documentation and make it all public.

<bandwagon>
If Ford had really wanted to keep it secret, then they should have provided it through OpenXC with an NDA.
</bandwagon>

 

[cking]

Want thank the last two posts, went to the vcm site and downloaded the manuals. That helped explain things better. Some success I did learn how to run the diff pump with a forscan. Still lost as to why when you change the as built to thinking the car has 12 speaker from factory installed 9 speaker the bass out does not enable from head unit. I'm still betting on PCM doesn't see the amp power signal and disables the output but it should throw error code.

 

[cking]

Sure would be cool to have a VCM-II with a data logger. I would consider buying one except the software expires yearly!! I see that eBay has clones for the hardware, but looks like the software is the problem. Maybe PencilGeek will write some software that would run on cloned hardware. Street Outlaws shows the guys with laptops analyzing each pass and tweaking the tune, wonder what software they're using?

 

[NipSC4328]

Sure would be cool to have a VCM-II with a data logger. I would consider buying one except the software expires yearly!! I see that eBay has clones for the hardware, but looks like the software is the problem. Maybe PencilGeek will write some software that would run on cloned hardware. Street Outlaws shows the guys with laptops analyzing each pass and tweaking the tune, wonder what software they're using?

I believe many of them are running Haltech ECU's with their s'ware.

 

[Helmet]

Want thank the last two posts, went to the vcm site and downloaded the manuals. That helped explain things better. Some success I did learn how to run the diff pump with a forscan. Still lost as to why when you change the as built to thinking the car has 12 speaker from factory installed 9 speaker the bass out does not enable from head unit. I'm still betting on PCM doesn't see the amp power signal and disables the output but it should throw error code.

You might have to disable the built in DSP

 

[PencilGeek]

Want thank the last two posts, went to the vcm site and downloaded the manuals. That helped explain things better. Some success I did learn how to run the diff pump with a forscan. Still lost as to why when you change the as built to thinking the car has 12 speaker from factory installed 9 speaker the bass out does not enable from head unit. I'm still betting on PCM doesn't see the amp power signal and disables the output but it should throw error code.

Or the 12-speaker is mapped to output pins differently than the 9-speaker. That would be more my assumption.

 

[PencilGeek]

Sure would be cool to have a VCM-II with a data logger. I would consider buying one except the software expires yearly!! I see that eBay has clones for the hardware, but looks like the software is the problem. Maybe PencilGeek will write some software that would run on cloned hardware.

For my CAN bus reverse-engineering, I use Vehicle Spy from Intrepid Control Systems. It's pricey @ $1000. It can data log the entire CAN bus. But based on what you ask next, I don't think this is the way to go.

Street Outlaws shows the guys with laptops analyzing each pass and tweaking the tune, wonder what software they're using?

I'm going to guess their either using AIM SOLO-DL or vBox Pro, or a standalone ECU with datalogging capabilities. The former two can provide vehicle GPS tracking, connect to the CAN bus, and datalog while you drive. Then you can graph the results on their software immediately after the runs. In the case of AIM SOLO for the GT350, you're VERY limited to what data they extract from the CAN bus. They have no facility to add your own CAN bus definitions. For example, let's say the SOLO doesn't give you TRANS temperature, but you want it -- and I know where to find it. AIM SOLO won't let you define the new sensor on CAN bus -- which means you can't data log it even if you knew where to find it. vBox Pro gives you everything AIM SOLO does (at a higher price), better analysis software IMO, and lets you define your own sensors on the CAN bus -- if you know where to find them.

What I've just explained is exactly why I've done this. I intend to publish the information so people with devices capable of datalogging will know where to find all of the sensors on the GT350 engine and transmission.

I might as well show you my "work-in-progress" wiki page. I stopped updating the wiki page about 3-weeks ago. I made huge breakthroughs since then and can now locate all of the relevant engine and transmission sensors that might be interesting for datalogging. So the info on the wiki page is old, stale, and in some cases even wrong. When I get time, I'll clean it up and add about 5x - 8x the amount of info listed there now.

http://wiki.rcollins.org/core/index.php/GT350_CAN_Bus_Topology

 

[Tank]

Some success I did learn how to run the diff pump with a forscan.

Congratulations [MENTION=28002]cking[/MENTION] :cheers: That's awesome.

Could you write it up and post either in a new thread or the Forscan thread?
I'm still hopeful we figure out the oem operation for diff pump on the Base/Techs. Every bit of info could help.

Thanks in advance.

 

[cking]

track mustangs online.com/threads/changing-diff-fluid-in-a-2017-gt-350.12268/

take the spaces out of the top line will give link to another forum that has write up about diff pump.

This site won't let you post links to another site:doh:

 

[cking]

R_DIFF_PUMP

PID FORSCAN TO RUN PUMP.
Another thread talks about manual switch harness he might sell.

 

[cking]

Diff pump maual wiring

Source with info

Sponsored