That was just for a read, not a write. I've done 3 reads now on 2 different PCM's, and it has averaged 50 minutes for each read. Cal flashes were pretty quick though.Originally Posted by steveo
That was just for a read, not a write. I've done 3 reads now on 2 different PCM's, and it has averaged 50 minutes for each read. Cal flashes were pretty quick though.
1995 GMC K2500 SUBURBAN 2001 LB7 DURAMAX/ALLISON swap, mostly stock, tuned by me with EFILive
1999 Tahoe 2 door 2X4, 5.7l with 0411 swap, and marine intake
I have posts up in so many places these days that I often forget to update posts from time to time......
With that being said.... I've been developing a tool with Envyous Customs as an alternative to the Allpro (since it is no longer avaible).... and I wanted something that would also work with my Android app over Bluetooth.
And it needed to be fast......
https://youtu.be/ImU5L5yQLTQ
Last edited by PeteS; 11-06-2019 at 10:23 AM.
Very cool. How many bytes are you writing in each block? Curious how you verify the write is correct? Thanks
-Carl
Ls Droid works with strings rather then bytes so packet size it a bit misleading here but my App is writing 2K blocks(4K characters).
Do you mean on each block or at the end of the flash?Curious how you verify the write is correct? Thanks
Each block uses a checksum that the PCM verifies when a block is written. If the checksum calculated by the flash kernel does not match the value sent by the app the kernel will reply with a 7F message indicating the checksum is incorrect. Each block also has a size value attached to it that the flash kernel checks to make sure the block is complete. If the block is not the correct size specified there is also a corresponding 7F message that will be sent back to the app by the flash kernel.
When the flash is complete the app also checks for a complete write at the end in 2 ways, first it checks the kernel to make sure the correct number of blocks have been written and then it reads the last 2 bytes of the PCM by address to make sure they are correct. If either check fails the app will alert the user and the flash kernel will continue running and allow you to start the flash over again with the same file or with another file if you'd rather write something else.
Really neat stuff, I've tuned a few LT1's over the years but the progress you all have made makes me wish I had a LT1 to play with :)
Back in the days of crapola I was happy to find a rom routine that would do 40h bytes at a time, load ram,write,read,verify,incw,continue. I was doing that in a vb shell, non car stuff and the files were in the 18k range and could finish in a few seconds. I really like what y'all are doing and I am enjoying the reading :)
-Carl
I didn't forget this time......
In an upcoming update for Ls Droid I'll be releasing a segment swap utility to make it easier to build the ideal file rather then hunting down a file that matches the exact combination your running.
this is great! news
has this been released yet Kind Sir
Posting Permissions
Reply With Quote
Bookmarks