Monaro cluster modding

[maccavvy]

Mines an 04 so I'll keep you posted

[SturdyHSV]

alfienoakes said:

Has anyone managed to do this on an 04 CV8 ? I've tried 2 cables from CPC and one from ebay with no luck

KMud's is an 04 and he's had some success. Which part of it isn't working? Does the software see the COM port but not talk to the car?

If it's that I'd be looking at the USB to Serial converter, the one in the ebay link I posted definitely works. I leave mine in my car so will make sure I bring my tablet to every meet

[KMud]

maccavvy said:

Mines an 04 so I'll keep you posted

Please do. I got the comms fine, just not sure if the tables I supposedly overwrote took (the ECT needle seems to behave as before). I'm not helping at all here until I check whether the tables were actually written...my car is currently away for some love, I will get to it at some point!

[alfienoakes]

I could connect to the lead, and open the port, but when I listen most of the output is just hex, without any text. Any read coomands also fail.

Then I updated the driver (windows 7) and it can't see the lead now. Apparently FTDI have amended the latest drivers to stop hookey cables working

which tablet do you use ?

[the_ferret82]

alfienoakes said:

Has anyone managed to do this on an 04 CV8 ? I've tried 2 cables from CPC and one from ebay with no luck

Yes done quite a few..

[SturdyHSV]

alfienoakes said:

I could connect to the lead, and open the port, but when I listen most of the output is just hex, without any text. Any read coomands also fail.

Then I updated the driver (windows 7) and it can't see the lead now. Apparently FTDI have amended the latest drivers to stop hookey cables working

which tablet do you use ?

That's odd, as their chips are used in bloomin' loads of stuff, and sold as a standalone USB to serial chip so it would be more damaging to their market to try and be clever and disable stuff.

To answer your question, I've got a Surface Pro 2, which runs Windows 8.1 (which is an utterly, utterly st operating system) but is basically built on Windows 7, so the driver architecture is much the same, so it should work really.

You will just get hex back when reading stuff, there won't be any text. All of the basic functions people want (logo, shift light etc.) can all be done using the 'preset' options in the software that he lists on his website, so you really once it's communicating it should be good to go

[alfienoakes]

I've sorted the cable now after finding this

internet said:

Starting from FTDI drivers version 2.08.14 we have faced random connectivity issues with some users. At that point of time FTDI gave us the first signal of market "cleaning". But they decided to go further and drivers version 2.10.00 started to "kill" all non-original ICs. Fortunately they don't destroy whole eeprom, just replace PID with 0000, what makes it appear in Devices Manager as FT232R and no driver can be installed. There are 2.12.00 drivers already released and by rumours they don't destroy PID, but what else is hidden there remains unknown.

So the moral seems to be 'don't use the latest drivers'

So now I can connect to the car, but I get a lot of error 06 when I try to read the interesting tables, 9 for example :-


[incar-cluster-com6]# read 9
Waiting for heartbeat...
Send: ['F2', '57', '01', '09', 'AD']
['01', '09', '06', '00', '00', '00', '00', '00', '50', '73', '74', '76', '76', '
76', '40', '80', '00', '00', '00', '00', '00', '00', '00', '00', '00', '00', '00
']
ALDL Mode: 0x1 (read configuration table) Table: 0x9
Startup Logo:
error: '06'


also if I use the preset it gets the same error


[incar-cluster-com6]# preset startup-logo=2
Waiting for heartbeat...
Send: ['F1', '56', '08', 'B1']
=== Current Config ===
Send: ['F2', '57', '01', '09', 'AD']
['01', '09', '06', '00', '00', '00', '00', '00', '50', '73', '74', '76', '76', '
76', '40', '80', '00', '00', '00', '00', '00', '00', '00', '00', '00', '00', '00
']
Startup Logo: Send: ['F1', '56', '09', 'B0']

error: '06


Is this because it's already got a Vauxhall logo ? I don't see Vauxhall in the list of valid logos, so is it a one way change ? ie, can't return to the original logo (not that I would want to !)

I wonder if I should I just splat over the code that's there

This is the result of a readALL, i'd be interested to compare it to another 04 if someone has kept it
Meanwhile I'm looking through the source code to see why it throws a 6....


Table 0x0,78,E2,01,01,00,00,2E,18,08,8D,00,00,43,F8,00,00,13,88,05,AB,36,06,1C,39,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,01,08,00,00,00,00,00,00,00,E5,FF,E5,51,D2,5F,02,6C,02,30,35,0C,07,94,08,00

Table 0x1,05,01,02,02,04,00,02,04,05,7E,64,11,12,01,05,7F,0A,62,00,03,AF,F0,00,00,00,B8,05,00,00,00,00,06

Table 0x2,00,01,A0,D7,00,01,D5,10,00,02,66,90,02,BE,00,11,00,11,00,18,00,37,2D,00,00,00,00,00,00,00,00,B4,00,7C,00,00,36,16,00,00,4A,56,03,E7,00,00,00,00,00,00,64,19,23,37,4B,00,01,00,0F,01,00,00,6C

Table 0x3,00,00,00,00,00,00,FB,00,00,07,04,44

Table 0x4,05,7E,64,11,0C,00,00,00,00,01,00,00,00,00,00,03,AF,F0,18,56,00,C8,00,00,FF,C0,3C,00,06,04,01,00,01,AD,B0,14,00,00,00,00,2B,50,73,74,76,76,76,03,00,40,80,78,05,40,80,C0,FF,05,5A,64,5A,06,84,91,02

Table 0x5,0C,00,00,00,00,01,00,00,00,00,00,03,AF,F0

Table 0x6,00,3C,00,49,00,5F,00,79,00,A7,00,C2,00,D0,00,DF,00,F0,00,F4,96,88,7E,72,60,48,38,28,10,04,96,08,02,04,26,4A,68,86,05,7F,0A,62,03,06,00,0A,01,40,08,12,01

Table 0x7,01,00,01,AD,B0,14,00,01,8F,69,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00

Table 0x8,00,03,00,03,03,01,01,03,E8,03,E8,01,2C,01,2C,01,F4,01,F4,64,64,19,23,37,4B,3C,50,64,6E,19,23,37,4B,3C,50,64,6E,00,01,00,0F,01,00,01,00,0F,01

Table 0x9,06,00,00,00,00,00,50,73,74,76,76,76,40,80,00,00,00,00,00,00,00,00,00,00,00

Edited by alfienoakes on Saturday 7th March 14:19

[the_ferret82]

alfienoakes said:

I've sorted the cable now after finding this

internet said:

Starting from FTDI drivers version 2.08.14 we have faced random connectivity issues with some users. At that point of time FTDI gave us the first signal of market "cleaning". But they decided to go further and drivers version 2.10.00 started to "kill" all non-original ICs. Fortunately they don't destroy whole eeprom, just replace PID with 0000, what makes it appear in Devices Manager as FT232R and no driver can be installed. There are 2.12.00 drivers already released and by rumours they don't destroy PID, but what else is hidden there remains unknown.

So the moral seems to be 'don't use the latest drivers'

So now I can connect to the car, but I get a lot of error 06 when I try to read the interesting tables, 9 for example :-


[incar-cluster-com6]# read 9
Waiting for heartbeat...
Send: ['F2', '57', '01', '09', 'AD']
['01', '09', '06', '00', '00', '00', '00', '00', '50', '73', '74', '76', '76', '
76', '40', '80', '00', '00', '00', '00', '00', '00', '00', '00', '00', '00', '00
']
ALDL Mode: 0x1 (read configuration table) Table: 0x9
Startup Logo:
error: '06'


also if I use the preset it gets the same error


[incar-cluster-com6]# preset startup-logo=2
Waiting for heartbeat...
Send: ['F1', '56', '08', 'B1']
=== Current Config ===
Send: ['F2', '57', '01', '09', 'AD']
['01', '09', '06', '00', '00', '00', '00', '00', '50', '73', '74', '76', '76', '
76', '40', '80', '00', '00', '00', '00', '00', '00', '00', '00', '00', '00', '00
']
Startup Logo: Send: ['F1', '56', '09', 'B0']

error: '06


Is this because it's already got a Vauxhall logo ? I don't see Vauxhall in the list of valid logos, so is it a one way change ? ie, can't return to the original logo (not that I would want to !)

I wonder if I should I just splat over the code that's there

This is the result of a readALL, i'd be interested to compare it to another 04 if someone has kept it
Meanwhile I'm looking through the source code to see why it throws a 6....


Table 0x0,78,E2,01,01,00,00,2E,18,08,8D,00,00,43,F8,00,00,13,88,05,AB,36,06,1C,39,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,01,08,00,00,00,00,00,00,00,E5,FF,E5,51,D2,5F,02,6C,02,30,35,0C,07,94,08,00

Table 0x1,05,01,02,02,04,00,02,04,05,7E,64,11,12,01,05,7F,0A,62,00,03,AF,F0,00,00,00,B8,05,00,00,00,00,06

Table 0x2,00,01,A0,D7,00,01,D5,10,00,02,66,90,02,BE,00,11,00,11,00,18,00,37,2D,00,00,00,00,00,00,00,00,B4,00,7C,00,00,36,16,00,00,4A,56,03,E7,00,00,00,00,00,00,64,19,23,37,4B,00,01,00,0F,01,00,00,6C

Table 0x3,00,00,00,00,00,00,FB,00,00,07,04,44

Table 0x4,05,7E,64,11,0C,00,00,00,00,01,00,00,00,00,00,03,AF,F0,18,56,00,C8,00,00,FF,C0,3C,00,06,04,01,00,01,AD,B0,14,00,00,00,00,2B,50,73,74,76,76,76,03,00,40,80,78,05,40,80,C0,FF,05,5A,64,5A,06,84,91,02

Table 0x5,0C,00,00,00,00,01,00,00,00,00,00,03,AF,F0

Table 0x6,00,3C,00,49,00,5F,00,79,00,A7,00,C2,00,D0,00,DF,00,F0,00,F4,96,88,7E,72,60,48,38,28,10,04,96,08,02,04,26,4A,68,86,05,7F,0A,62,03,06,00,0A,01,40,08,12,01

Table 0x7,01,00,01,AD,B0,14,00,01,8F,69,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00

Table 0x8,00,03,00,03,03,01,01,03,E8,03,E8,01,2C,01,2C,01,F4,01,F4,64,64,19,23,37,4B,3C,50,64,6E,19,23,37,4B,3C,50,64,6E,00,01,00,0F,01,00,01,00,0F,01

Table 0x9,06,00,00,00,00,00,50,73,74,76,76,76,40,80,00,00,00,00,00,00,00,00,00,00,00

Edited by alfienoakes on Saturday 7th March 14:19

it throws a 06 error as 06 is the VX logo number, the yanks that put the software together where not interested that the UK clusters, had a VX logo so never programmed there software for the 06 code.... just ignore the error. fyi its not a one way change...

[maccavvy]

ive got my cable ... connected to car... opened a port.

and when I try to programm anything is says error 06 .. any ideas

[SturdyHSV]

It appears both you guys are getting the Error 06 when doing the startup logo. As ferret said this is because the Vauxhall logo is in there as 06, so when that VZClusterMod software reads the information from the cluster, it gets that 06 back, and that doesn't correspond to any logo value it's expecting, hence the error.

I've let the guy know who wrote the software, and have copied over alfie's post as that should be pretty useful for him to sort it out, it'll just be a case of adding in the extra value so that it knows what a '06' is and doesn't throw the error.

If anything, it's a good thing that the software is throwing an error when it sees something it doesn't expect and isn't just blindly writing over stuff with its fingers crossed!

I'll let you guys know

[alfienoakes]

SturdyHSV said:

I've let the guy know who wrote the software, and have copied over alfie's post as that should be pretty useful for him to sort it out, it'll just be a case of adding in the extra value so that it knows what a '06' is and doesn't throw the error.

Thanks for that, I was going to have a go at amending the code myself but never having used Python before it could take a while !!

Hopefully he will be up for making the changes, it's only a few lines of code, but potentially the US cars will never have an 06 set, and I imagine it might cause problems if the code allows an 06 to be set on a US cluster

Otherwise I thought we might be able to use writemem if I could be sure of the location. It might be 0x7F but I've not tried it yet

[VinceM]

Got my cable and connector but haven't had time to do any soldering yet, am watching this latest update with interest. Thanks.

[SturdyHSV]

alfienoakes said:

Thanks for that, I was going to have a go at amending the code myself but never having used Python before it could take a while !!

Hopefully he will be up for making the changes, it's only a few lines of code, but potentially the US cars will never have an 06 set, and I imagine it might cause problems if the code allows an 06 to be set on a US cluster

Otherwise I thought we might be able to use writemem if I could be sure of the location. It might be 0x7F but I've not tried it yet

I would assume (wildly) that when reading it back it's attempting to cast the '06' to a 'Logo' type he's defined, and as 6 doesn't exist, it's getting the error.

I would also assume that the 'preset' functions will do something similar, hence getting the error. His easiest bet would be to add the 06 to the 'Logo' type as a valid option, and then in the 'preset' function for setting the logo, disallow a value of 6.

If it was in a language I know and I'd written it, then that's how I'd have done it and I know that it'd take 2 lines of code to fix. So I'd imagine it's probably not too difficult and he's got it this far for free and fixed bits etc. so I'd assume he'd be happy to make it a more rounded product.

[maccavvy]

mine did make the mph dim .. but wouldn't recognise anything else. .I daren't do anything except presets as its above and beyond my pc knowledge

[SturdyHSV]

Guy who wrote the software said:

Ah, I see what the problem is. I'm doing a dumb dictionary lookup for the friendly value of the cluster model, which in this case isn't in the config file. Almost positive the UK clusters have different firmware, which is why when you put 06 in a US/AUS cluster, it does nothing.

In the definitions.py file from the source:
Code:
cluster_models = {
"00" : "Holden",
"01" : "HSV",
"02" : "Chevrolet",
"03" : "Omega",
"04" : "Chevrolet Special Vehicles",
"05" : "Pontiac",
}
needs to be:

Code:
cluster_models = {
"00" : "Holden",
"01" : "HSV",
"02" : "Chevrolet",
"03" : "Omega",
"04" : "Chevrolet Special Vehicles",
"05" : "Pontiac",
"06" : "Vauxhall",
}
And...probably some less rubbish error handling too. lol

I'll try to get a new release out tomorrow.

[alfienoakes]

Top Man thanks for chasing that up

I did notice in the thread on LS1GTO that someone over there actually wanted the Vauxhall logo

[SturdyHSV]

alfienoakes said:

Top Man thanks for chasing that up

I did notice in the thread on LS1GTO that someone over there actually wanted the Vauxhall logo

Yeah, to them Vauxhall is exotic and unusual Some of them have done Vauxhall conversions

[maccavvy]

Nice one dude.. any sign of the new software yet.. would love to get mine sorted from the exotic Vauxhall to something more mundane lol

[SturdyHSV]

maccavvy said:

Nice one dude.. any sign of the new software yet.. would love to get mine sorted from the exotic Vauxhall to something more mundane lol

Nothing yet, will give him a few days then pester him

[alfienoakes]

Updated software is available, works a treat

http://api.viglink.com/api/click?format=go&jso...