Can pscan enable the factory low coolant light

pscan.uk wrote:

It is possible to "move" fobs from one Pektron unit to another, but it has to be done on the bench, not with the Pektron in the car.
I have been working on being able to do this so that Technozen isn't the only person in the world able to do it.

That is excellent !!

Cobber wrote:

Red110 wrote:

I am happy with my Lucas electronics 😅

 

I bet you'd never've thought you'd end up saying that! 

I too am happy with my Lucas system, it is predictable in all areas, until it interfaces with a third party device.
It is there where the problems start & it is rarely the Lucas part that creates the problem.
Lucas designed to the Rover specification, adapting their MEMs system to the requirements of a new model. As the system is modular, a wholesale redesign isn’t required when a part is updated, in a number of instances it’s a software tweak to rectify.
The MEMs system has deep roots & has been updated a goodly number of time since it first outings in the ‘70s.
I know all the Prince of Darkness jibes, the melted wires, poor connectors & crappy bullet connectors but Lucas built to a price which was stipulated by the motor manufacturer & it didn’t matter whether it was the motor manufacturer or Lucas that carried the can, the can still had to be carried, with both being the butt of a rather poor joke.
Hence no car industry, or Lucas.
M

=3790 wrote: It is possible to "move" fobs from one Pektron unit to another, but it has to be done on the bench, not with the Pektron in the car.
I have been working on being able to do this so that Technozen isn't the only person in the world able to do it.

I don't know how far you've already got with this, so you may already be ahead of me, but I have recently spent some time examining the contents of the eeprom in the pektron SCU. Moving the fob data between units should be straighforwsrd, as it's just the original fob code (albeit slightly rearranged in terms of the order of digits), plus some bytes preceeding each of the fob codes which store the number of times each fob has been used (in order to keep the rolling code window syncronised). As long as the usage count is copied to the new SCU along with the fob code, there shouldn't be any issues.

Some of the other contents of the eeprom were quite easy to decypher (vehicle VIN, Pektron model / version / serial number, and the EKA code), but not having access to a T4, reverse engineering any of the SCU configuration options isn't really feasable for me. 

I'm more than happy to share my findings so far if you think they would be of any use to you.