Return To Fordmods Home Page
 Home |  Forums |  Search |  My Profile |  Chat
 Photo Gallery |  Events Calendar |  Technical Documents
 No messages |  New Posts |  Watched Topics |  Register  
1999 AU -> OBDII compliant?
Goto page 1, 2  Next
 
Post new topic   Reply to topic    Forum Index -> ECU and Fuel System Forum
 
darrinh
Fordmods Newbie




Posts: 7
Joined: 17 May 2005
Location: sydney NSW, Australia

View User Gallery (0)

 
PostPosted: Tue May 17, 2005 1:05 pm    Post subject: 1999 AU -> OBDII compliant? Reply with quote

anybody know if that model is OBD-II compliant?, from the information i've read, would suggest that it is, but i have tried a scan tool (www.scantool.net), using the PWM protocol, which is used, at least, for US delivered Fords, and it doesnt work?, i really interested in accessing the error codes.


thanks.[/quote]
Back to top
Nanger
Fordmods Stock as a Rock



Age:38
Posts: 188
Joined: 06 Nov 2004
Location: Melbourne VIC, Australia

View User Gallery (5)

 
PostPosted: Tue May 17, 2005 3:04 pm    Post subject: Reply with quote

I think the AU on wards are supposedly OBD II compliant. The scantool I bought http://cgi.ebay.com/ebaymotors/ws/eBayISAPI.dll?ViewItem&rd=1,1&item=4543270680&sspagename=STRK%3AMEWN%3AIT wont work on AU or BA. As a matter of fact it wont work on VT VX and VY Commohores either, which are supposed to be OBD II compliant. My scanner works fine on newer jap and Eurotrash but for some reason Aussie cars must have a different protocol or something.
Back to top
darrinh
Fordmods Newbie




Posts: 7
Joined: 17 May 2005
Location: sydney NSW, Australia

View User Gallery (0)

 
PostPosted: Wed May 18, 2005 12:12 am    Post subject: Reply with quote

Nanger wrote:
I think the AU on wards are supposedly OBD II compliant. The scantool I bought http://cgi.ebay.com/ebaymotors/ws/eBayISAPI.dll?ViewItem&rd=1,1&item=4543270680&sspagename=STRK%3AMEWN%3AIT wont work on AU or BA. As a matter of fact it wont work on VT VX and VY Commohores either, which are supposed to be OBD II compliant. My scanner works fine on newer jap and Eurotrash but for some reason Aussie cars must have a different protocol or something.


i ordered one of those already, from the research ive done, its mandatory for all US delivered cars to be OBDII compliant,but no such regulation exists in Australia, so manufacturers in Australia dont often bother.

The connector on the falcon very closely matches the SAEJ1850-PWM OBDII protocol, but as noted, the scantool did not like this,the NGS or WDS systems will work but i dont have a spare $3 or $4K!. so when i get the scantool from ebay, im going to probe the lines with my oscilloscope and try to see if the ECU responds at all to the scantool queries, it could be the (Ford) ECU requires some intial handshake before giving up the info or that a line needs to be pulled up or down.
Back to top
Disco Frank
Fordmods Junkie



Age:29
Posts: 13277
Joined: 05 Nov 2004
Location: Perth WA, Australia

View User Gallery (7)

 
PostPosted: Wed May 18, 2005 4:26 am    Post subject: Reply with quote

dude let us know if this works....

as far as i know the AU is OBII
but i taold this to nager after he tried the tool on his cars, and it did not work what it could be is that since the tool is US made it only recognises/reads us/european vehicles ( ie code wise ) i mean what AUS vehicles are in the us/europe ( yer yer ok the munro )
hence the scan tool may just need to be Flashed with the aussie code or somethign for it to work on the OBII cars icon_smile.gif
Back to top
Disco Frank
Fordmods Junkie



Age:29
Posts: 13277
Joined: 05 Nov 2004
Location: Perth WA, Australia

View User Gallery (7)

 
PostPosted: Wed May 18, 2005 4:31 am    Post subject: Reply with quote

just found this on the link nanger posted

ake sure the ignition is in the 2nd position. Your car OBD-II connector has 16 pins:


1. ECU
2. J1850 bus + , VPW data, PWM data
3. engine rpm signal
4. chassis ground
5. signal ground
6. CAN High (J2284)
7. ISO 9141-2 K line (ECU), engine load data, etc
8. ignition
9. ABS,traction control,stability control, electronic brake proportioning, Brake Assist System, antislip regulation, electronic shift lever detector
10. J1850 bus - , PWM data
11. transmission
12. Activity Module/Extended Activity Module, transfer case
13. airbag, seatbelt, SRS, audio, navigation, CD changer, teleaid
14. CAN Low (J2284)
15. ISO 9142-2 L line
16. battery power positive (+14V)

Note: If your car has one or two green or blue pins above, this unit will work on your car. I do not have a product that works on yellow pins (CAN protocol) yet. Other pin 1,3,8,9,11-13 are manufacture discretion pins, could be different function or empty.
Back to top
darrinh
Fordmods Newbie




Posts: 7
Joined: 17 May 2005
Location: sydney NSW, Australia

View User Gallery (0)

 
PostPosted: Wed May 18, 2005 9:37 am    Post subject: Reply with quote

Disco Frank wrote:
dude let us know if this works....

as far as i know the AU is OBII
but i taold this to nager after he tried the tool on his cars, and it did not work what it could be is that since the tool is US made it only recognises/reads us/european vehicles ( ie code wise ) i mean what AUS vehicles are in the us/europe ( yer yer ok the munro )
hence the scan tool may just need to be Flashed with the aussie code or somethign for it to work on the OBII cars icon_smile.gif


there are 4 protocols within OBDII, SAEJ1850-PWM,SAEJ1850-VPW,ISO 9141 (Asia) & KWP2000, i still think its PWM, but perhaps has some particular sequence to initialize the interface, which technically, means it is not OBDII compliant.
Back to top
Nanger
Fordmods Stock as a Rock



Age:38
Posts: 188
Joined: 06 Nov 2004
Location: Melbourne VIC, Australia

View User Gallery (5)

 
PostPosted: Wed May 18, 2005 9:51 am    Post subject: Reply with quote

Disco Frank wrote:
just found this on the link nanger posted

ake sure the ignition is in the 2nd position. Your car OBD-II connector has 16 pins:


1. ECU
2. J1850 bus + , VPW data, PWM data
3. engine rpm signal
4. chassis ground
5. signal ground
6. CAN High (J2284)
7. ISO 9141-2 K line (ECU), engine load data, etc
8. ignition
9. ABS,traction control,stability control, electronic brake proportioning, Brake Assist System, antislip regulation, electronic shift lever detector
10. J1850 bus - , PWM data
11. transmission
12. Activity Module/Extended Activity Module, transfer case
13. airbag, seatbelt, SRS, audio, navigation, CD changer, teleaid
14. CAN Low (J2284)
15. ISO 9142-2 L line
16. battery power positive (+14V)

Note: If your car has one or two green or blue pins above, this unit will work on your car. I do not have a product that works on yellow pins (CAN protocol) yet. Other pin 1,3,8,9,11-13 are manufacture discretion pins, could be different function or empty.


Frank I checked this out before I bought mine and according to the diagram the AU has the pins in the right spot. Could it be a case of Ford disabling the system somehow? The other thing I don't understand is if OBD II is supposed to be a standard why is there a few different protocols? Sort of defeats the purpose.
Back to top
4.9 EF Futura
Moderator



Age:27
Posts: 8658
Joined: 05 Nov 2004
Location: Adelaide CBD SA, Australia

View User Gallery (37)

 
PostPosted: Wed May 18, 2005 12:28 pm    Post subject: Reply with quote

Yeah, OBD2 gets even better.... the standard legislated certain 'minimums' that the protocol had to adhere to - the kind of data needed, the manner in which it communicated...

But then there are 'enhanced' versions specific to each manufacturer.. which provide information above and beyond the OBD standards, and I think this is where ECU flashing comes into it...

http://www.obdii.com/connector.html

And its home page

http://www.obdii.com/

May have little relevance to Australia.... god bless america icon_wink.gif
Back to top
4.9 EF Futura
Moderator



Age:27
Posts: 8658
Joined: 05 Nov 2004
Location: Adelaide CBD SA, Australia

View User Gallery (37)

 
PostPosted: Wed May 18, 2005 12:35 pm    Post subject: Reply with quote

More info:

Seems like OBDII kicked off in 03 here, and will be required buy 08... ah well, we're only 12 years behind...

http://norcom.net.au/~bpt/can_scan_tool.htm

Might wanna try your scan tools on an explorer or focus or probe or something....
Back to top
darrinh
Fordmods Newbie




Posts: 7
Joined: 17 May 2005
Location: sydney NSW, Australia

View User Gallery (0)

 
PostPosted: Wed May 18, 2005 2:02 pm    Post subject: Reply with quote

4.9 EF Futura wrote:
More info:

Seems like OBDII kicked off in 03 here, and will be required buy 08... ah well, we're only 12 years behind...

http://norcom.net.au/~bpt/can_scan_tool.htm

Might wanna try your scan tools on an explorer or focus or probe or something....


yeah, seen that page, the CAN protocol is to replace all previous OBDII protocols, at least for Ford, also, i read somewhere that there is OBDIII in the works.

anyway, i want to get something to work, i dont want to have to 'assume the position' at a stealership or local garage, ive always done my own work, but on vehicles without much in the way of computerisation.


Last edited by darrinh on Wed May 18, 2005 2:04 pm, edited 1 time in total
Back to top
Nanger
Fordmods Stock as a Rock



Age:38
Posts: 188
Joined: 06 Nov 2004
Location: Melbourne VIC, Australia

View User Gallery (5)

 
PostPosted: Wed May 18, 2005 2:02 pm    Post subject: Reply with quote

Another problem I have found is locating the connector on the car. Jap cars are easy, usually under the dash, but Euro cars hide them, under consuls behind panels ect. It seems its law that they have to have them but you are allowed to hide them if you like.
Back to top
darrinh
Fordmods Newbie




Posts: 7
Joined: 17 May 2005
Location: sydney NSW, Australia

View User Gallery (0)

 
PostPosted: Wed May 18, 2005 4:15 pm    Post subject: Reply with quote

ok. apparently ford uses something called SCP:

Quote:
The information is sent through Ford's standard corporate protocol, or SCP, the company's proprietary version of the SAE J1850 diagnostic data communications protocol.

http://www.popularmechanics.com/automotive/auto_technology/1266726.html?page=2&c=y
Back to top
Nanger
Fordmods Stock as a Rock



Age:38
Posts: 188
Joined: 06 Nov 2004
Location: Melbourne VIC, Australia

View User Gallery (5)

 
PostPosted: Wed May 18, 2005 6:09 pm    Post subject: Reply with quote

darrinh wrote:
ok. apparently ford uses something called SCP:

Quote:
The information is sent through Ford's standard corporate protocol, or SCP, the company's proprietary version of the SAE J1850 diagnostic data communications protocol.

http://www.popularmechanics.com/automotive/auto_technology/1266726.html?page=2&c=y


Ha Ha, got this off the popular mechanics site. Obviously a company car.

here it is..........

In addition to learning more about the mechanical performance of the vehicles, Ford has made other interesting discoveries. One person starts up his F-150 pickup and immediately holds it at wide-open throttle in Park for several minutes every morning. Many customers who say they need more power hardly ever run their engines wide open.
Back to top
darrinh
Fordmods Newbie




Posts: 7
Joined: 17 May 2005
Location: sydney NSW, Australia

View User Gallery (0)

 
PostPosted: Wed May 18, 2005 7:34 pm    Post subject: Reply with quote

the pinout for my connecter is:

2,4,5,7,10,13,16

Pin-----Ignition On---- /---- OFF
2___________0.05v______0v
4____________gnd______ gnd
5___________ gnd______gnd
7____________10.30v____10.53v
10___________5.06v______0v
13___________0.41v______0v
16___________12v______12v
Back to top
darrinh
Fordmods Newbie




Posts: 7
Joined: 17 May 2005
Location: sydney NSW, Australia

View User Gallery (0)

 
PostPosted: Tue May 24, 2005 7:09 pm    Post subject: Reply with quote

Nanger wrote:
I think the AU on wards are supposedly OBD II compliant. The scantool I bought http://cgi.ebay.com/ebaymotors/ws/eBayISAPI.dll?ViewItem&rd=1,1&item=4543270680&sspagename=STRK%3AMEWN%3AIT wont work on AU or BA. As a matter of fact it wont work on VT VX and VY Commohores either, which are supposed to be OBD II compliant. My scanner works fine on newer jap and Eurotrash but for some reason Aussie cars must have a different protocol or something.


i also brought one of these, doesnt work as you have said, so i had a look inside, it contains an Atmel 89C251 microcontroller (based on the old Intel 8051), so i will probably be able to download the code and may be able to modify it to work with AU fords.
Back to top
Nanger
Fordmods Stock as a Rock



Age:38
Posts: 188
Joined: 06 Nov 2004
Location: Melbourne VIC, Australia

View User Gallery (5)

 
PostPosted: Tue May 24, 2005 8:17 pm    Post subject: Reply with quote

That would be great if you could do that. Let us know when it happens.

As for my scanner I had to use it today on my 2001 Rodeo V6. This is the second time in 3 weeks that it wont start. It cranks over but nothing else. I connected up the code reader and got code 1626 which is 'B(+) supply to Variable Load Control Module Air Condition Circuit Malfunction'.

Now this sounds like an ISC but I'm not sure. Both times it has started after 10 minutes so I don't really care especially since it's my work car and I leaving work next month. I'll let somebody else worry about it.
Back to top
ItchiOne
Fordmods - Smokin em up




Posts: 280
Joined: 30 Mar 2005
Location: Melbourne VIC, Australia

View User Gallery (2)

 
PostPosted: Mon May 30, 2005 1:10 pm    Post subject: Reply with quote

Nanger wrote:
..The other thing I don't understand is if OBD II is supposed to be a standard why is there a few different protocols? Sort of defeats the purpose.

ODB-II was a mandated minimum standard initially pushed onto US car manufactures and car importers by the US state of california primarily for polution reaons.
Car makers did not and do not want any generic diagnostics tool or open protocols. They live by propritery systems and fight tooth and nail to keep them.
It's then no surprise that as the standard allows for variations to exist, they do exist and as a result we have 4 protocols as well as manufacturer specific extensions being used within ODB-II vehicles.
It's just a typical world of legislative compromises.

What i find anoying is when a manufacturer can use ODB complient systems in their export vehicles (=monaro) and sell a propritery system to the locals in auz (and wors still, sell it for a higher price).

What can you do icon_confused.gif

Cheers.
Back to top
cheets
Fordmods Newbie




Posts: 1
Joined: 11 Feb 2005
Location: Hobart TAS, Australia

View User Gallery (0)

 
PostPosted: Wed Jun 08, 2005 1:18 pm    Post subject: Reply with quote

The AU falcon OBD-II port and uses SCP (Standard Corporate Protocol) which is a part of the OBD-II standard. Most cheap scantools do not suport all the protocols of the OBD-II standard. Since SCP is a ford specific protocol many do not support it.
Back to top
reaper_falcon
Fordmods Newbie



Age:20
Posts: 15
Joined: 21 Jul 2007
Location: Mackay QLD, Australia

View User Gallery (0)

 
PostPosted: Tue Apr 22, 2008 6:59 pm    Post subject: Reply with quote

has anyone been able to flash their scan tool to include SCP at all?
Back to top
Lukeyson
Fordmods - Getting Side Ways




Posts: 882
Joined: 07 Nov 2005
Location: Newcastle NSW, Australia

View User Gallery (0)

 
PostPosted: Fri May 02, 2008 9:34 pm    Post subject: Reply with quote

SCP is just Ford rebranding of J1850 PWM. And most scantools support that.

I had heard that the pinout of the port on the AU was unique, but I'm not sure about that.

I'd love to try an get my ELM to talk to an AU someday. I have a mate down the road withw 2 x AU2's that might be able to help (1 is a dual fuel, the other a dedicated LPG)


Lukeyson
Back to top
Display posts from previous:   
   
Post new topic   Reply to topic    Forum Index -> ECU and Fuel System Forum
Goto page 1, 2  Next
Page 1 of 2

 
 
(c)2002-2008 Matti Jones and Brad Evans

[47 queries :: 0.09001 seconds ]