Program that can log from many multimeters.

[The Soulman]

DC Voltage:
400 mV range doesn't work.(<NaN>)
4 V range has decimal point in the wrong place i.e.: dmm displays 0.994V software 99,4V
400 V range doesn't work. (<NaN>)

note this chip has a separate 40mV DC function, that does work correctly in software.

 

[The Soulman]

DC current:

40mA range works correctly
400ma range doesn't work (<NaN>)

20A range has decimal point in the wrong place i.e.: dmm displays 0.098A software 9,8A

Edit to add:

200uA range doesn't work (<NaN>)
2000uA range works correctly

[HKJ]

New jar file up (V0.80)

It fixes the temperature problem and hopefully the decimal placement and adds permanent hex dump (Will be removed when the ranges works).
It may also fix OL in ohm ranges, if not I need the hex dump.
Please post the a line of hex dump for the ranges that shows NaN or other wrong values.

[The Soulman]

New jar file up (V0.80)

It fixes the temperature problem and hopefully the decimal placement and adds permanent hex dump (Will be removed when the ranges works).
It may also fix OL in ohm ranges, if not I need the hex dump.
Please post the a line of hex dump for the ranges that shows NaN or other wrong values.

First check in V0.80 shows the DCV 400mv still doesn't work, were can I find the HEX dumps? 

[HKJ]

First check in V0.80 shows the DCV 400mv still doesn't work, were can I find the HEX dumps? 

It is something like this:
;; COM11: Rx: 1.234  2B 31 32 33 34 20 30 78 78 78 78 78 0D 0A
;; COM11: Rx: 1.234  2B 31 32 33 34 20 30 78 78 78 78 78 0D 0A
;; COM11: Rx: 1.234  2B 31 32 33 34 20 30 78 78 78 78 78 0D 0A

In the log window.

[The Soulman]

First check in V0.80 shows the DCV 400mv still doesn't work, were can I find the HEX dumps? 

It is something like this:
;; COM11: Rx: 1.234  2B 31 32 33 34 20 30 78 78 78 78 78 0D 0A
;; COM11: Rx: 1.234  2B 31 32 33 34 20 30 78 78 78 78 78 0D 0A
;; COM11: Rx: 1.234  2B 31 32 33 34 20 30 78 78 78 78 78 0D 0A

In the log window.

Ok, on the 400mV range it doesn't show hex, neither in the cmd.exe.
On working ranges it does.
The meter does work on this range with other software.

[HKJ]

Ok, on the 400mV range it doesn't show hex, neither in the cmd.exe.
On working ranges it does.
The meter does work on this range with other software.

I have modified the start of message detection, I hope this helps (V0.81).
Its not really a question about what software the meter works on, the problem is that I need to get the decoder correct for the meter. It is not difficult, but it is slow when somebody else do the testing. As long as some people do test and post results I will get the meter working.
I have programmed a Arduino to simulate the meter (more or less), it will repeat any hex dump I put into it. This means any hex dump that do not decode correctly I can easily simulate and fix.

[The Soulman]

Ok, on the 400mV range it doesn't show hex, neither in the cmd.exe.
On working ranges it does.
The meter does work on this range with other software.

I have modified the start of message detection, I hope this helps (V0.81).
Its not really a question about what software the meter works on, the problem is that I need to get the decoder correct for the meter. It is not difficult, but it is slow when somebody else do the testing. As long as some people do test and post results I will get the meter working.
I have programmed a Arduino to simulate the meter (more or less), it will repeat any hex dump I put into it. This means any hex dump that do not decode correctly I can easily simulate and fix.

Much appreciated, will test with 0,81

[The Soulman]

098,3mV = 0A 2B 30 39 38 33 20 34 11 00 40 80 09 0D

edit to add:

0,097V = 0A 2B 30 30 39 37 20 31 11 00 00 80 00 0D

[MikeLud]

If getting either LXI or GPIB to work on a existing device, please post a line here with the device filename and the #port line used, then I can update the original.

HKJ,

LXI works for the Siglent SDM's line shown below.  I notes that when using LXI the Rx line has the > on the next line. I am making some changes to the device file. I will send an update file in the next day or two including LXI.

Code: [Select]

#port 5024 LXI

Code: [Select]

;; 15:26:48.437 SDM3065X: Tx <DATA:LAST?>
;; 15:26:48.516 SDM3065X: Rx <+2.25545080E+01    C
>
;; 15:26:48.566 SDM3065X: *OPC waited: 32ms
;; 15:26:48.566 SDM3065X: Rx as numbers <22.554508>
;; 15:26:48.638 SDM3065X: Tx <DATA:LAST?>
;; 15:26:48.758 SDM3065X: Rx <+2.25566770E+01    C
>
;; 15:26:48.808 SDM3065X: *OPC waited: 33ms
;; 15:26:48.808 SDM3065X: Rx as numbers <22.556677>

[HKJ]

098,3mV = 0A 2B 30 39 38 33 20 34 11 00 40 80 09 0D

My start of block detection was still faulty, I hope it is fixed now.
The decimal placement  that is specified to be 0, 1, 2, 3 was 4
For now I have just put a 1 factor in, but it will probably have to be adjusted.

[HKJ]

LXI works for the Siglent SDM's line shown below.  I notes that when using LXI the Rx line has the > on the next line. I am making some changes to the device file. I will send an update file in the next day or two including LXI.

Code: [Select]

#port 5024 LXI

I will wait for your update. The > on the next line means I am not stripping the LF character, I may add that.

[The Soulman]

098,3mV = 0A 2B 30 39 38 33 20 34 11 00 40 80 09 0D

My start of block detection was still faulty, I hope it is fixed now.
The decimal placement  that is specified to be 0, 1, 2, 3 was 4
For now I have just put a 1 factor in, but it will probably have to be adjusted.

dcV:

40mV     OK
400mV   meter: 198.1mV software: 1,981V

400mV   meter: 198.1mV software: 1,981V
4V          OK
40V        OK
400V      meter: 046,8V   software: 468V
1000V    OK

Will test other functions tomorrow..
Thanks again.

[gby]

I am trying out logging at the fastest rate with a single fast device.  Specifically I choose the 0.01 sec per sample point option.  Sometimes I see a fairly major glitch in the chart data.  At first I thought it was the device and/or communications issue.  But, I really don't think so.  I examined the details of the point Index number versus the time stamp and I am seeing the sample time interval almost double.

I took a short log session to .csv and then in Excel plotted the time stamp versus index number.  That graph clearly shows a glitch followed by the sample interval time increasing by almost exactly 2x.  What is going on here???  Is this a bug in the code or is the code trying to be smart and adjust the sample time slower when the sampling does not keep up?

Second issue with logging at 0.01 sec intervals:  In the Table tab the time column only shows up to 0.1 sec resolution.  Certainly when sampling at the 0.03 second or the 0.01 second interval you want to see two digits after the decimal.  I get that for slower sampling it may not be needed to show the extra digit, but would it hurt?

[HKJ]

I took a short log session to .csv and then in Excel plotted the time stamp versus index number.  That graph clearly shows a glitch followed by the sample interval time increasing by almost exactly 2x.  What is going on here???  Is this a bug in the code or is the code trying to be smart and adjust the sample time slower when the sampling does not keep up?

The software will adjust sample interval if it gets behind.
I run the sample code with fairly high priority in the system, but the OS may have other tasks it want to do first, that may delay a sample. If you give any command to the device while sampling it may also delay sampling.

Second issue with logging at 0.01 sec intervals:  In the Table tab the time column only shows up to 0.1 sec resolution.  Certainly when sampling at the 0.03 second or the 0.01 second interval you want to see two digits after the decimal.  I get that for slower sampling it may not be needed to show the extra digit, but would it hurt?

Internally I use millisecond resolution, but because most devices are fairly slow I have limited the table to 0.1 sec resolution. I believe it is easier to read numbers with fewer digits.

[HKJ]

dcV:

40mV     OK
400mV   meter: 198.1mV software: 1,981V

400mV   meter: 198.1mV software: 1,981V
4V          OK
40V        OK
400V      meter: 046,8V   software: 468V
1000V    OK

jar file V0.83 where the extra factor is 0.1
I was missing the hex dump to confirm it was the extra decimal location.

[The Soulman]

dcV:

40mV     OK
400mV   meter: 198.1mV software: 1,981V

400mV   meter: 198.1mV software: 1,981V
4V          OK
40V        OK
400V      meter: 046,8V   software: 468V
1000V    OK

jar file V0.83 where the extra factor is 0.1
I was missing the hex dump to confirm it was the extra decimal location.

dcV is 100% now 
I start checking other functions.

I've also discovered I can use ctrl-c to copy data from the command screen (right click copy doesn't work) so that makes it easier for me to include the hex dump when something isn't right.

edit:

dcA is 100%
resistance is 100%
Temperature in C is correct, in F converts to C in software, maybe intentional.
Frequency including duty cycle is 100% up to 99,99Khz range, above untested.
acV is 100%
diode and continuity is 100%
capacitance is 100%

A minor imperfection is that on all ranges that I've noticed OL is displayed as 0, for instance MOhm range:

Code: [Select]

;; COM6: Rx: 0.0  2B 3F 30 3A 3F 20 32 21 00 10 20 29 0D 0A


[HKJ]

A minor imperfection is that on all ranges that I've noticed OL is displayed as 0, for instance MOhm range:

Code: [Select]

;; COM6: Rx: 0.0  2B 3F 30 3A 3F 20 32 21 00 10 20 29 0D 0A


I had guessed wrong about how overload was signaled, it is fixed now. I will not upload a new version yet.
How many meters is covered by this definition? Uni-T UT61B, UT61C, UT61D, but what other brands and models?

[The Soulman]

How many meters is covered by this definition? Uni-T UT61B, UT61C, UT61D, but what other brands and models?

After searching the Sigrok website I've came up with these:

EZA EZ-735
Victor 70C
Victor 86C
Voltcraft VC830
Voltcraft VC850
SparkFun 70C

And also:

Peaktech 2025

And thanks to UltraDMM:

Pro'sKit MT-1820
Uni-t UT60A
Uni-t UT60D
DigiTek DT-9602R+



And probably some more.

My Metrawatt 2+ and Ohmeron MT488E also work but not out of the box because the serial out isn't implemented from the factory..

edit: added a few

[MikeLud]

I will wait for your update. The > on the next line means I am not stripping the LF character, I may add that.

HKJ,

Attached is an updated device file for the Siglent SDM's

Changes:
Improved read speed, old speed about 800ms to new speed about 70ms
Added LXI support

 SiglentSDM30xxx.txt (18.65 kB - downloaded 41 times.)

[HKJ]

After searching the Sigrok website I've came up with these:

That was a long list, I have added them all for next releaes.

Thanks for all the help with the implementation.

Attached is an updated device file for the Siglent SDM's

Will be included in next release.

[HKJ]

V0.84 is up, it is mostly about the meters added above.

   Added Uni-t UT61B, UT61C, UT61D (Fortune FS9922-DMM3 & FS9922-DMM4 DMM chips) with help from "The Soulman"
   Added a lot of other similar meters, thanks to "The Soulman" from EEVBlog forum
   Updated Siglent bench meter definitions , thanks to "MikeLud" from EEVBlog forum
   Added manual/help pages for Histogram, Scales, Range and Math.

[Marco1971]

Many many thanks HKJ...for your work.

Marco1971

[MikeLud]

V0.84 is up, it is mostly about the meters added above.

   Added Uni-t UT61B, UT61C, UT61D (Fortune FS9922-DMM3 & FS9922-DMM4 DMM chips) with help from "The Soulman"
   Added a lot of other similar meters, thanks to "The Soulman" from EEVBlog forum
   Updated Siglent bench meter definitions , thanks to "MikeLud" from EEVBlog forum
   Added manual/help pages for Histogram, Scales, Range and Math.

HKJ,

V0.84 shows V0.76 in about

[HKJ]

V0.84 shows V0.76 in about

You have been to fast to download, the webserver has some caching that can delay a upload before is available. It is very frustrating but I cannot do anything about it (I could, of course, wait some time before saying a new version was uploaded).