You can fully control the scope via USB but unfortunately the SW is for 32b Windows only (Win 7 and up), no 64b version :-(
with high energy. Rather go for a R+S RTH (the one that sucks by far the least, compared to fluke, tek or agisight) here.Ar you sure? I went through most of the isolated input scopes last year and the higher end Keysight models seem to be the best when comparing specs. BTW I did use the Keysight U1620 a couple of times and it seems like a very capable instrument to me which can replace a 2 channel benchtop oscilloscope.
Is it not isolated channels? even when using a battery?
I like my Scopemeter just to be able to do "carefree" prodding inside mains equipment. (Of course I jest - any "carefree" prodding - even with an isolated scope or differential probes - will eventually kick your ass).
That is disappointing. Perhaps it will install and work with one of the compatibility modes in Windows? I know getting the Fluke SW to work is a pain in the A**.
Interesting.
Is it possible to flash the regular MS200 firmware image?
There may be an issue with the AD737 when it comes to low and high signal levels. The VC8145 bench DMM uses a similar RMS converter chip and the accuracy/bandwidth of the RMS conversion depends on the input signal level.
So do anyone know why the multimeter has been disconnected? Manufacturing defects? Or just don't meet the specs? (how did you reconnect and enable it?)
So do anyone know why the multimeter has been disconnected? Manufacturing defects? Or just don't meet the specs? (how did you reconnect and enable it?)
Micsig told me that there were QA issues so they disabled it and are selling it as non Micsig, but who knows...
In HW you just need to reconnect the socket - see the attached photo of how it came (they just cut the wire).
In SW for full functionality you would need to flash the original FW.
So do anyone know why the multimeter has been disconnected? Manufacturing defects? Or just don't meet the specs? (how did you reconnect and enable it?)
Micsig told me that there were QA issues so they disabled it and are selling it as non Micsig, but who knows...
In HW you just need to reconnect the socket - see the attached photo of how it came (they just cut the wire).
In SW for full functionality you would need to flash the original FW.
Did you get it with accessories and everything? How useful is the SPI/I2C triggering? Is there any form of decoding? Is the firmware available and easy to flash onto it?
I just got the shipping coast:
Hello Karsten,
the shipping cost is 75USD total. and it inlcuse ebay freight shipping cost 10%.
Jelin Wei
Shenshen Micsig instruments Co., Ltd.
www.micsig.com (http://www.micsig.com)
<content> <pcode>MS200</pcode> <type>MicSig</type> <pkg>0</pkg> <version>8.0.53.306-N1</version> </content>
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:Code: [Select]<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...
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:Code: [Select]<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...
Only 250 euro? What bid did they accept? With the 75 USD shipping + 20-25% VAT?
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:Code: [Select]<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...
<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>
If anyone is interested I have figured out how to unpack and repack the firmware updates.
However the FW for real Micsig is not completely compatible with the debranded version. And it seems that the features are controlled separately. I.e. the FW as such is just one and then some separate data block contains data like serial number, product code, delivery date, available features, etc.
My guess is that this is controlled by the FW part called "bios_user" or "bios_sys" (note that the FW updates contain only "bios_user" part).
So you are able to flash the Micsig firmware on it, but the Meter functions are still not available?
So you are able to flash the Micsig firmware on it, but the Meter functions are still not available?
The update SW is checking among others the "major" version from the scope and from the FW file (7 v. 8 ). I managed to flash it once (by running in a debugger and tweaking the data in runtime).
But no, it did not re-enable the multimeter function. So I gave up.
So you are able to flash the Micsig firmware on it, but the Meter functions are still not available?
The update SW is checking among others the "major" version from the scope and from the FW file (7 v. 8 ). I managed to flash it once (by running in a debugger and tweaking the data in runtime).
But no, it did not re-enable the multimeter function. So I gave up.
It looks like the MS420IT don't have serial bus trigger ("decode") like the MS220T.
Did you notice that Micsig also have a MS420IT scope that has exactly the same specifications as the MS220T? The only visible difference beeing the price: 999$ for the MS220T and 599$ for the MS420IT.
Something interresting is that the MS420IT shares its firmware with the MS520T, top of the range model. The "major" version in the 420/520 firmware beeing 5. Did you have a look in it?
So you are able to flash the Micsig firmware on it, but the Meter functions are still not available?
The update SW is checking among others the "major" version from the scope and from the FW file (7 v. 8 ). I managed to flash it once (by running in a debugger and tweaking the data in runtime).
But no, it did not re-enable the multimeter function. So I gave up.
So you are able to flash the Micsig firmware on it, but the Meter functions are still not available?
The update SW is checking among others the "major" version from the scope and from the FW file (7 v. 8 ). I managed to flash it once (by running in a debugger and tweaking the data in runtime).
But no, it did not re-enable the multimeter function. So I gave up.
That is the level of ugly bodge job i sort of expected.
I did check if there was any rework on the front panel controller and the connector going to the front but didnt disassemble any further. Going to have a look at mine soon...
Now for the interesting part, which glue will bond to the silicone rubber keymat?
This is at least one good reason for the "Meter" key not to work :)
So you are able to flash the Micsig firmware on it, but the Meter functions are still not available?
The update SW is checking among others the "major" version from the scope and from the FW file (7 v. 8 ). I managed to flash it once (by running in a debugger and tweaking the data in runtime).
But no, it did not re-enable the multimeter function. So I gave up.
Even the built-in recorder function works fine. Testing it against my voltage standard gives ~0.6% inaccuracy, can't find anything else wrong with it.
This is at least one good reason for the "Meter" key not to work :)
Same here - quick "transplant" from another keyboard and the meter is fully working.
Would be interesting if anyone else could check any issues/inaccuracies of the meter. If every scope has problems only with AC measurements at higher frequencies.
Did you check after flashing your scope wether you are able to activate the probe compensation signal output or not?So you are able to flash the Micsig firmware on it, but the Meter functions are still not available?
The update SW is checking among others the "major" version from the scope and from the FW file (7 v. 8 ). I managed to flash it once (by running in a debugger and tweaking the data in runtime).
But no, it did not re-enable the multimeter function. So I gave up.
So you are able to flash the Micsig firmware on it, but the Meter functions are still not available?
The update SW is checking among others the "major" version from the scope and from the FW file (7 v. 8 ). I managed to flash it once (by running in a debugger and tweaking the data in runtime).
But no, it did not re-enable the multimeter function. So I gave up.
I may need you help with some test points on scopes with working DMM function. As the DMM chip is known (the FS9922-DMM4 used in UT-61D) I will try reverse engineering the DMM part http://www.ic-fortune.com/upload/Download/FS9922-DMM4-DS-13_EN.pdf (http://www.ic-fortune.com/upload/Download/FS9922-DMM4-DS-13_EN.pdf)Some progress today. If I short the REL/RS232 pin (77) on the FS9922-DMM4 for more than 2 seconds (simulating the RS232 activation key) then it starts sending data on the TXD pin (92). I can then trace the signal on U10 (optocoupler input), and then I see a signal on another optocoupler output (U24). Still no valid data on the scope but it is stops freezing as soon as the transmition starts. It just shows 0°C whatever function I select.
I suppose that the data are retrieved from the DMM chip via TXD (pin 92) but I don't see where it could be connected.
By any chance, if someone can sense this pin on a working scope.
There are only few components around the DMM chip. Maybe I will be lucky :-//
I've bought one too, any one know if the meter is usable at least for basic measures and if the decode of serial protocols is available. Thanks in advance.
Armando Molina
Got mine, fix the keyboard and the red input and have the same issues with AC at high Freq. but at least is usable for quick measures.
Can be saved to USB memory stick, i only try FAT32, later i will test NTFS.
Too late, I've bought one! Offered $200, got accepted.Thanks for posting. I offered $200 too and it got accepted. And shipping went down to $60 from $69 for total of $260. :)
- When you attach probes and select the lowest vertical scale, the artifacts of a switching regulater start to appear. This was noticeable with the PSU connected.
There's one more issue with the meter that probably affects all of them: The shielding can of the DMM section has the scoop pressed into it like it's used on one of the scope channels. In my case, despite of the insulation sheet inside, the edge of this scoop got so close to the positive DMM socket terminal that I wouldn't consider it safe to use. Just a slight spike will cause an arc-over, and since the shielding can is referenced to the negative socket, this may result in a major firework, depending on the circuit that's being measured. I simply ground off the projecting part of the scoop and everything's fine.
Mstck - are you sure your conductive pad is up to snuff? IIRC another member mentioned that the 1st one he tried didn't work. It looks like it has worked for everyone so far but two guys, did both of you try multiple pads or directly completing the circuit?
Mstck - are you sure your conductive pad is up to snuff? IIRC another member mentioned that the 1st one he tried didn't work. It looks like it has worked for everyone so far but two guys, did both of you try multiple pads or directly completing the circuit?
Thanks for the suggestion. I was beginning to think along the same line since absolutely nothing happens when I press the "Meter" key. I ordered these... https://www.amazon.com/gp/product/B017OIKGMW/ref=oh_aui_detailpage_o02_s00?ie=UTF8&p;sc=1 (https://www.amazon.com/gp/product/B017OIKGMW/ref=oh_aui_detailpage_o02_s00?ie=UTF8&p;sc=1) as recommended by mtdoc in post #68. They install on the membrane, not the key. As such, I was wondering if there is a need to place something in the hollow of the key which would push on the contact when the key is pressed.
I will open the unit again after xmas festivities, and see if I can energize it outside of the case to test if the pad works.
Does the Windows application run under Wine?