Sounds good. I'm flexible and can do the remote this evening if you are available. Not sure what time zone you are in, I'm MST.jpl250rs wrote: Tue Aug 26, 2025 9:18 am great so let's plan a schedule and get connected with rustdesk when ever you can
Integer is not valid
Forum rules
Do not send PM , if your can't find your problm , please open a new thread with your bike and issue
Do not send PM , if your can't find your problm , please open a new thread with your bike and issue
-
- Posts: 5
- Joined: Sun Aug 24, 2025 10:58 pm
Re: Integer is not valid
Re: Integer is not valid
from now untill the end of this hours it's ok for me it's 9:12 pm actually
-
- Posts: 5
- Joined: Sun Aug 24, 2025 10:58 pm
Re: Integer is not valid
PM sentjpl250rs wrote: Tue Aug 26, 2025 7:12 pm from now untill the end of this hours it's ok for me it's 9:12 pm actually
Re: Integer is not valid
yes i got it , but you are probably at work now
Re: Integer is not valid
Hello,
I also get the same error when Melcodiag v 2.0.4.8 (the latest download) is run; I just tried it after previous versions 2.0.3.7 and 2.0.4.6 which startup (still needing an OK on a visual basic prompt) and connect OK, but the reset buttons are not active despite lic.cle present (will open another thread on that).
My bike / PC / ELM device
- Scrambler 800 2109
- Windows 10
- Lonelec Bluescan v1.5
I also get the same error when Melcodiag v 2.0.4.8 (the latest download) is run; I just tried it after previous versions 2.0.3.7 and 2.0.4.6 which startup (still needing an OK on a visual basic prompt) and connect OK, but the reset buttons are not active despite lic.cle present (will open another thread on that).
My bike / PC / ELM device
- Scrambler 800 2109
- Windows 10
- Lonelec Bluescan v1.5
Last edited by cds31 on Mon Sep 01, 2025 7:12 pm, edited 1 time in total.
Re: Integer is not valid
thanks for the capture , i think i found the error , you can download it again and make a new test
Re: Integer is not valid
I have just tried the latest Melcodiag from the DOWNLOAD (v 2.0.4.8)
- It starts up OK now - there is no longer the error "conversion from string to type integer not valid".
- I am unable to confirm whether resets work (as I already did my annual earlier with the previous version); note however, I was unable to activate any "button" on the DTC tab (e.g. Scan for ECUs), and on the Resets tab the only buttons that seem to be active are "Key reset" and "Gear reset" : not grayed like the other ones, and turn brighter when the cursor is over them. Thanks for your work.
- It starts up OK now - there is no longer the error "conversion from string to type integer not valid".
- I am unable to confirm whether resets work (as I already did my annual earlier with the previous version); note however, I was unable to activate any "button" on the DTC tab (e.g. Scan for ECUs), and on the Resets tab the only buttons that seem to be active are "Key reset" and "Gear reset" : not grayed like the other ones, and turn brighter when the cursor is over them. Thanks for your work.
Re: Integer is not valid
thanks for the feedback
it looks like the cle.lic is not valid or locked .
this can be checked in the debug report file
it looks like the cle.lic is not valid or locked .
this can be checked in the debug report file
Re: Integer is not valid
at the end of the debug report :
"lic found
000357929hard :QD0J3010
scrambler detected
soft :1QABAAD1
"
"not registered"
(I have the whole report if needed);
What do I need to do to unlock the cle.lic ? if that is the cause
"lic found
000357929hard :QD0J3010
scrambler detected
soft :1QABAAD1
"
"not registered"
(I have the whole report if needed);
What do I need to do to unlock the cle.lic ? if that is the cause
Re: Integer is not valid
try to register again , maybe the cle.lic is not correct