F36 - cannot code start/stop since software update at BMW

Sasquartch · 01-18-2018, 08:00 AM

Although I think I have a recent version of psdzdata when I try and read coding data from FEM_BODY I get the following error :

Does this mean I need a newer psdzdata ? I thought I was on 63.3

Also I take it it's correct to be connecting as F020 (not direct) on a F36 420d ??

Sasquartch · 01-18-2018, 08:23 AM

Looks like my psdzdata may not have been in the correct place - I'll try again

Almaretto · 01-18-2018, 06:21 PM

If you were using PSdZ 3.63.3, your connection would be F020-17-11-530.

Sasquartch · 01-19-2018, 08:07 AM

Quote:

Originally Posted by Almaretto

If you were using PSdZ 3.63.3, your connection would be F020-17-11-530.

Thank you, yes, this is the connect string I used

Now my psdzdata files were correct everything worked fine.

01-18-2018, 08:00 AM	#1
Sasquartch Major 606 Rep 1,455 Posts Drives: 520i G30 Join Date: Aug 2016 Location: Herts iTrader: (0)	F36 - cannot code start/stop since software update at BMW Although I think I have a recent version of psdzdata when I try and read coding data from FEM_BODY I get the following error : Does this mean I need a newer psdzdata ? I thought I was on 63.3 Also I take it it's correct to be connecting as F020 (not direct) on a F36 420d ?? Attached Images
	Appreciate 0 Tweet Quote

01-18-2018, 08:23 AM	#2
Sasquartch Major 606 Rep 1,455 Posts Drives: 520i G30 Join Date: Aug 2016 Location: Herts iTrader: (0)	Looks like my psdzdata may not have been in the correct place - I'll try again
	Appreciate 0 Quote

01-18-2018, 06:21 PM	#3
Almaretto Major General 2374 Rep 8,364 Posts Drives: Test Vehicles Join Date: Dec 2015 Location: Mountain View, CA iTrader: (0)	If you were using PSdZ 3.63.3, your connection would be F020-17-11-530.
	Appreciate 1 Sasquartch606.00 Quote