They do take offers for lower prices, so...
I did recieve it today.
After Tax and some random UPS fees its a bit over 250eur, but still not too bad.
So far, it does work, as expected its a chinese D-Brand scope with limited capabilities, but should do.
Interesting find in the MS200 fw update file:
<content> <pcode>MS200</pcode> <type>MicSig</type> <pkg>0</pkg> <version>8.0.53.306-N1</version> </content>
Might be worth trying to change MS200 to SCOPE200? Maybe its that stupid...
Congrats to your new scope.
Re price - that's about right. I have also asked why so expensive and they claimed that was the only way due to LiIon battery regulation. Btw in my case they used DHL Express, took 2 days to deliver to Europe (unnecessary (and expensive) luxury)...
Re FW upgrade - I do not it that would be that easy. I was looking a little bit into it. It seems that the FW as downloaded from web is something like:
- Header (length, perhaps checksum,etc.), which includes also the "XML manifest" you saw
- Signature
- Encrypted payload
Within the encrypted payload it sort of repeats again as there are several parts of the FW and each is again (perhaps with some variation in details):
- Header (length, perhaps checksum,etc.), which includes also the "XML manifest" you saw
- Signature
- Encrypted payload
For the current FW "MS200_8_53_306_N1.bin" it contains these "manifests":
<content>
<pcode>MS200</pcode>
<type>logo</type>
<pkg>0</pkg>
<version>8.0.0.0-N1</version>
</content>
...
<content>
<pcode>MS200</pcode>
<type>meter_mcu</type>
<pkg>0</pkg>
<version>8.4.0.0-N1</version>
</content>
...
<content>
<pcode>MS200</pcode>
<type>user_bios</type>
<pkg>0</pkg>
<version>8.0.30.201-N1</version>
</content>
...
<content>
<pcode>MS200</pcode>
<type>mcu_key</type>
<pkg>0</pkg>
<version>8.2.0.0-N1</version>
</content>
...
<content>
<pcode>MS200</pcode>
<type>app</type>
<pkg>0</pkg>
<version>8.0.53.306-N1</version>
</content>
With the exact data sizes of:
- logo - 614 400 bytes
- meter_mcu - 2 184 bytes
- user_bios - 118 872 bytes
- mcu_key - 8 227 bytes
- app - 4 519 504 bytes
Interestingly enough the program decodes and decrypts everything in the memory then checks version (which in our case fails). At the moment I think what fails is checking the "major version" - here 8 (which is then reported as 8N1) versus 7N1 from our scopes. I.e. so far what I have seen is a check is done in the program on Windows and not on the scope (which is good).
The decryption is not secret, the key , etc is in the program (or you can just use API Monitor and trace APIs like CryptDecrypt
).