PCMTec Development Blog

[rolls]

Right, so its 'almost' bullet proof... or for better words... 'idiot' proof.

If someone goes out of their way to purposely flash the wrong sections or ECU in.. then really.. theres no-one to blame but them.

Yes but of course there could be bugs eg it gets flashed to the wrong sectors etc.

[rolls]

Ok autodetect is finished and the read write to BF works, write to BA is failing on the last block, I suspect it requires a long time out between changing banks. I'm going to tweak all my timeouts and maybe add some retry logic (unsure if the download routine will accept retries) but I suspect it will be fine once I increase these. It seems about 4x slower than the spanish oak at this stage, the can bus routine also seems inconsistent and returns address_out_of_range instead of security_access_denied at various times when testing if it needs to be unlocked.

Gotta be up at 6am tomorrow so I guess this is it for another few days!

edit: a 5 second timeout between switching banks was all it needed. Just need to do some more unit testing and polishing and I'll send something out in the next day or two.

BA write only takes 2:36 some how... maybe it isn't writing all the data, guess we will see when I finish my testing.

edit: confirmed with HPT that it is is fine.

[rolls]

Decided to deploy the alpha through a test framework eg something like Hockey. This will automatically collect usage and crash statistics and push them to the net. As the number of people PMing me to test is increasing I need a good way to collate any issues, bugs and track who is testing what.

I'll hold off on sending anything out until I've done this as a alpha/beta is useless unless I have a way to debug any crashes you have.

[rolls]

Could everyone who wants to continue testing the application PM me your email address? Even if I already have it can you send again so I can make a mailing list for the alpha.

I've got it set up to email me the debug, sniff and crash logs now so I'm just giving it another round of testing and should send it out tonight/tomorrow sometime.

[rolls]

Just sent out alpha 0.1 release via the mailing list. Let me know if I missed anyone out.

Any questions/issues if you can post them in here so we can keep all the info in one place.

Cheers

[VX L67 Getrag]

Nice Work Rolls, I look forward to testing it out & sending any bugs back!

with the sniffing will it do it offline & then send it back in a saved format too as I have software I have to use offline, some of it is other type protocols too though!

[rolls]

It saves the logs to a text file so you can just pm/email them to me if you are offline

[rolls]

Ok I should have seen this coming but if you send a debug/sniff log can you PM me when you sent it. I pull your login and put this in the email but if your login is simply "HOME" etc then I don't know who it is. I'll add in a popup to put your name and a note when sending for the next release.

I also found out from gus that if you try and flash a FG -> BF PCM the PCM will accept the write but then on power reset it will wipe the flash and not accept any OBD commands. This is most likely as the RTOS doesn't match. Whilst the PCM won't reply to any OBD2 commands it will still accept security access. I'll put in an option for "manual download" which will ignore all errors to allow you to reflash a PCM that is in this recovery state. I believe HPT call this process "recovery mode".

So just FYI don't try and flash a completely different tune at this stage unless you have something else to recover it with. Eg don't do BF -> FG or Territory to BF etc. I'll add in a recover mode this week sometime as it isn't much work to do.

I suspect even if I do write the RTOS that the PCM won't function as no doubt the electronics are different. I'll also add a prompt that this recovery mode will most likely occur if you have mismatching PCM versions.

[0xFFFF]

I suspect even if I do write the RTOS that the PCM won't function as no doubt the electronics are different. I'll also add a prompt that this recovery mode will most likely occur if you have mismatching PCM versions.

Thanks for the update. I will wait until then before testing.

[rolls]

I suspect even if I do write the RTOS that the PCM won't function as no doubt the electronics are different. I'll also add a prompt that this recovery mode will most likely occur if you have mismatching PCM versions.

Thanks for the update. I will wait until then before testing.

As long as you flash BA->BA, BF -> BF or FG -> FG there is no problem currently. I have flashed a 2005 and 2008 file onto my BF PCM as well without issue so I suspect it is only changing model that will cause the recovery mode. Eg Territory -> BF and things like that which to be honest there is no real good reason to try anyway.

The program won't let you do BA -> BF etc as the PCM type is totally different, so no need to worry about that either.