Ecmspy for Mono; After several years of glitch-free use, I'm suddenly getting the following error statement when I attempt to load an eeprom from file; "Failed to load EEPROM: Failed to decrypt database 'BUEGB.xml'."

Fuel and timing maps will load from file with no problem.
I reloaded the database from the "My Downloads" web page, but it didn't help.
The "Messages" tab info pretty much repeats the error message.

What's going on?

Todd

Have you always used it with that firmware?

_________________
08 Specialized Langster

If by firmware you mean BUEGB, then yes, my bike is an '04 XB12S which uses the BUEGB ecm. The last time I used ECMspy to make an eeprom change was several months ago and it worked fine. I've made no changes since, but did recently attempt a datalog with an Android tablet and Buelltooth dongle. I couldn't open the resulting BIN file either.

Have you changed your PC or anything on it?

_________________
08 Specialized Langster

No, that's what is so puzzling. Could copying the BIN files from ECMDroid to my pc, then attempting to load them into ECMSPY corrupt something? I'm at a loss to explain it.

Doubt it. Why not reinstall it?

_________________
08 Specialized Langster

Okay, I went to the EcmSpy "My Downloads" page and reinstalled the EcmSpy for Mono and the database onto my PC. Didn't help.

I tried connecting to the bike's ECM via cable, which not surprisingly, failed. The following error message came up: Failed to get database info for this ECM: PKCS1 decoding error. Unable to fetch EEPROM. The Messages tab statement was, Error: Caught exception while checking for database: PKCS1 decoding error.

My ECM seems healthy, it connects to and communicates with ECMDroid, the bike runs okay - it's not throwing any error codes. I've got another known good ECM which I could plug in to see if ECMSpy would connect to it but I'm a bit shy about doing that without knowing where the problem lies.

Todd

So, your key is invalid. Something has changed on your machine

http://www.ecmspy.com/ug_mono/V2.0/inst ... n#database

What email did you use to activate?

_________________
08 Specialized Langster

My email is nt650@aol.com.

The only change I can think of is an upgrade from Win. 8 to Win. 10 when it became available for download.

Would that invalidate my key? Can I recover it?

Todd

As it turns out, the Windows 10 upgrade did blow up my ECMSpy public key, so the lesson is to beware and use caution before making changes to your PC.
Pash, always the gentleman, got me fixed up and back in the groove.