Siglent Bench DMMs SDM3065X, SDM3055 and SDM3045X

[Performa01]

Question:

What do you consider a standard calibration period? 1 Year? Something else?

If you purchase a DMM, and the calibration is over a year old, what would you expect of the manufacturer? Or let's say, a random number like...11 months old compared to the purchase date? What then?

Unsurprisingly, that depends on the requirements and technology.

For a DMM the most common calibration interval is one year, but certain instruments fit extra stable resistor networks and then guarantee their long-term specs for two years - which of course also means that the calibration interval is that long.

For demanding tasks, where highest accuracy is needed, you can still use the meter as a transfer standard using the short term specifications, but for this, the calibration intervals are much shorter, like e.g. 60 days or even 24 hours in extreme cases.

For the question how companies handle old stock with expired calibration - they might sell it at a discount, such as Siglent does:

https://siglentna.com/products/clearance/

[KungFuJosh]

For the question how companies handle old stock with expired calibration - they might sell it at a discount, such as Siglent does:

https://siglentna.com/products/clearance/

Interesting, but I'm not talking about old stock, I'm talking about purchasing on Amazon brand new with an expired or nearly expired cal cert (which is fairly common).

How would specific companies handle that?

[Performa01]

If you buy from a dealer, be it Amazon or anyone else, this is your contract partner, so it is between you (the customer) and the dealer to negotiate a discount or a replacement with a freshly calibrated device. Getting delivered a device that is out of cal. would be a reason for a warranty claim against the dealer.

What we don't know is what kind of contract, agreement the dealer has with the manufactuer. Basically it would not be surprising if the storage risk is completely at the dealer's side, i.e. if they stock gear that they cannot sell in time they will have to grant a discount - renewing the calibration would not be an option for most dealers. Thing is, calibration is cheapest when done in the course of production and final quality control in the factory, where the initial adjustment has to be done anyway, so the calibration data is spawned practically for free.

And it is not clear to me, how partially expired cal. certificates should be handled. Aging is slower at the dealer on the shelf than in your lab in actual use, hence sometimes manufactuerers might specify a longer validity for the calibration in such cases of long storage times.

You could try to convince the dealer to accept the following simple calculation: if the calibration is valid for one year, and a new calibration costs e.g. $200,- and if you get the device half a year after the cal. date, i.e. calibration is "half expired", you want a discount of half the calibration cost, i.e. $100,-

[Mortymore]

Taking advantage of the 10% Siglent discount until the end of the month and other 5% discount code, bought a SDM3045X, that came with firmware version 5.02.01.09R2

What's the difference between the version 5.02.01.09R2 to the latest firmware available to download V5.01.01.09R2 (Release Date 04.27.23)?

By the way, the calibration date is 2023-05-31

[Johnny B Good]

 Here's Siglent's policy statement on the matter with regard to the SDS2104X+ I'd purchased just over 3 years ago.

[tautech]

Here's Siglent's policy statement on the matter with regard to the SDS2104X+ I'd purchased just over 3 years ago.

2023 Calibration statement:

Recommended Due Date for Calibration
SIGLENT has determined that the factory calibration of the following models is not significantly affected by storage of up to 18 months before first-time use. Cal Interval should start at the time the unit is placed in service or 18 Months past the “Date of Calibration” on the certificate received with the unit.
Models effected by this notice:
·
SDS1000DL+ Series Oscilloscopes
·
SDS1000X-E/U Series Oscilloscopes
·
SDS2000X-E Series Oscilloscopes
·
SSA3000X Series Spectrum Analyzers
·
SPS5000X Power Supplies
·
SPD1000X Power Supplies
SPD3000 Power Supplies
SDG1000X arbitrary waveform generators
SDG2000X arbitrary waveform generators
Determine the date when the next Cal is due (refer to the examples shown below)
Example 1: First-time use of instrument is less than 18 Months after “Date of Calibration”.
Date of Calibration: 2019-06-17
Example calibration interval: 12 months
First-time use of instrument: 2019-8-17
First-time use + Example calibration interval = Date for next calibration
2019-8-17 + 12 months = 2020-8-17
---------------------------------------------------------------------------------------------------------------------------
Example 2: First-time use of instrument is more than 18 Months after “Date of Calibration”.
Date of Calibration: 2019-06-17
Example calibration interval: 12 months
First-time use of instrument: 2021-1-17
Date of Calibration + 18 Months + Example calibration interval = Date for next calibration
2019-6-17 + 18 Months + 12 months = 2021-12-17

https://siglentna.com/service-and-support/calibration-certificate/

[Johnny B Good]

 I noticed that the SDS2000-X Plus and SDM series don't get any mention in that list of 'models effected'. Does that mean they have a different policy for those models?

[KungFuJosh]

I noticed that the SDS2000-X Plus and SDM series don't get any mention in that list of 'models effected'. Does that mean they have a different policy for those models?

Siglent NA told me the 12 months + 180 days thing for the SDM. I guess they did okay since they offered to calibrate my SDM3055 for half price under the circumstances. Of course, I asked them if I could wait a couple months because I want more break-in time first, and I haven't heard back yet, so we'll see. 🤷

[KungFuJosh]

Wow! I just saw on eBay, that if you think an SDM3045X is too cheap, you can buy the same DMM with a Lecroy badge on it for the price of the SDM3065X. Cool! 

[tomud]

Wow! I just saw on eBay, that if you think an SDM3045X is too cheap, you can buy the same DMM with a Lecroy badge on it for the price of the SDM3065X. Cool! 

Not only this multimeter can be purchased with a LeCroy badge at a "good" price What's funny is that when I looked at equipment with the LeCroy badge, I don't know why it has terribly delayed firmware updates (or maybe even no update - I haven't checked for a long time whether they have published any newer firmware for both SDM and SVA).

I once thought about uploading the firmware from "LeCroy" (Firmware for SVA). However, it turned out that updates are worse there and the firmware is much older.

On the other hand, you can always print a Teledyne badge and change the launch logo for more prestige - this is a certain advantage of Siglent equipment

[flo.b]

Taking advantage of the 10% Siglent discount until the end of the month and other 5% discount code, bought a SDM3045X, that came with firmware version 5.02.01.09R2

What's the difference between the version 5.02.01.09R2 to the latest firmware available to download V5.01.01.09R2 (Release Date 04.27.23)?

By the way, the calibration date is 2023-05-31

For now the difference is that you cannot flash it with a SDM3055X-E firmware. For me, trying to flash any official firmware gives "Update fail" although I don't know if a downgrade ever worked.
There's already a thread about it: https://www.eevblog.com/forum/testgear/sdm3045x-to-sdm3055x-e-improvement-thread/msg5075350/
Hopefully there will be a solution

[Mortymore]

There's a new user manual for the SDM3055

https://siglentna.com/wp-content/uploads/dlm_uploads/2023/10/SDM3055_UserManual-EN03B.pdf

Unfortunately, despite the updated display screenshots in the manual, there's no explanations about calibration, Ref. temperature or custom sensor 

[Martin72]

I had yesterday the calibration protocol for my 3065X sent, I put a link to it(24h), you can look at better than these csv files I got before.
Uploaded I have everything except the page with further information such as serial number.
The execution of the protocol.....well, it is sufficient for private use.
A few display errors, but that does not bother me.
The main thing is that I have it.

[Danielpedro71]

Hello friends,
do you have any examples of remote communication with the multimeter SDM3055?
I'm using the language that the Agilent HP34401A use with the Metcal 7 Fluke Software, but I can't get the readings.
Thanks

[KungFuJosh]

Hello friends,
do you have any examples of remote communication with the multimeter SDM3055?
I'm using the language that the Agilent HP34401A use with the Metcal 7 Fluke Software, but I can't get the readings.
Thanks

There's the programming guide: https://siglentna.com/wp-content/uploads/dlm_uploads/2017/10/SDM-Series-Digital-Multimeter_ProgrammingGuide_EN02A.pdf

[skander36]

Hello friends,
do you have any examples of remote communication with the multimeter SDM3055?
I'm using the language that the Agilent HP34401A use with the Metcal 7 Fluke Software, but I can't get the readings.
Thanks

Hi! The language is called SCPI. In Easy DMM, the Siglent software for DMM3XXX you have a SCPI console to test the commands (Control tab-> Send Command).

[Mortymore]

Hello friends,
do you have any examples of remote communication with the multimeter SDM3055?
I'm using the language that the Agilent HP34401A use with the Metcal 7 Fluke Software, but I can't get the readings.
Thanks

I've been playing with Python and some of my Siglent instruments so here's some code to read current, voltage and calculate power from 2 SDM30XX

Code: [Select]

# Reading voltage and current with Siglent multimeters
# current: SDM3055
# voltage: SDM3045X

import pyvisa
import time
from pyvisa import errors

# --------------------------------------------------------------
class Multimeter:

    def __init__(self, device):
        self.device = device

    def measure_current(self):
        '''Ampmeter ID '''
        amp_meter_id = self.device.query('*IDN?').split(',')
        print("\nDMM Amp: " + str(amp_meter_id[1]).strip())
        # Set as DCI
        self.device.write("CONF:CURR:DC")
        # measure current (A)
        current = float(self.device.query('READ?'))
        time.sleep(0.2)
        print(f"Current = {current:.5f} A")
        return current

    def measure_voltage(self):
        '''Voltmeter ID'''
        volt_meter_id = self.device.query('*IDN?').split(',')
        print("\nDMM Volt: " + str(volt_meter_id[1]).strip())
        # Set as DCV
        self.device.write("CONF:VOLT:DC")
        # measure voltage (V)
        voltage = float(self.device.query('READ?'))
        time.sleep(0.2)
        print(f"Voltage = {voltage:.5f} V")
        return voltage


# --------------------------------------------------------------
def main():

    rm = pyvisa.ResourceManager()

    # Device LAN connections (set IPs)
    SDM45 = 'TCPIP0::192.168.0.45::inst0::INSTR'
    SDM55 = 'TCPIP0::192.168.0.55::inst0::INSTR'

    amp_meter = None
    volt_meter = None

    # Try to connect to amp_meter (DMM1)
    try:
        amp_meter = Multimeter(rm.open_resource(SDM55))
        print("Ampmeter connected.")
    except errors.VisaIOError:
        print("Ampmeter not found!")

    # Try to connect to volt_meter (DMM2)
    try:
        volt_meter = Multimeter(rm.open_resource(SDM45))
        print("Voltmeter connected.")
    except errors.VisaIOError:
        print("Voltmeter not found!")

    while True:
        print("\n== MENU =========")
        print("1. Measure current")
        print("2. Measure voltage")
        print("3. Measure power")
        print("0. END")
        print("=================")

        choice = input("OPTION: ")

        if choice == '1' and amp_meter is not None:
            amp_meter.measure_current()
        elif choice == '2' and volt_meter is not None:
            volt_meter.measure_voltage()
        elif choice == '3' and amp_meter is not None and volt_meter is not None:
            voltage = volt_meter.measure_voltage()
            current = amp_meter.measure_current()
            power = voltage * current
            print(f"\nPower = {power:.5f} W")
        elif choice == '0':
            if amp_meter is not None:
                amp_meter.device.close()
            if volt_meter is not None:
                volt_meter.device.close()
            print("Terminated")
            break
        else:
            print("Invalid OPTION or device not connected.")

if __name__ == "__main__":
    main()

This site can be a good reading source: https://www.iu3jsx.it/wp/2023/01/29/bench-multimeter-remote-programming-using-python/

[Danielpedro71]

Hello guys,

thanks for help me.
I manage to communicate with the Siglent, but the problem is when it comes to communicating it with Fluke's Metcal software. Below I've put the code I use for an Agilent 34401A. I'm trying to adapt the code.... let's see if anyone has experiences with the Metcal program.....
 STEP    FSC    RANGE NOMINAL        TOLERANCE     MOD1        MOD2  3  4 CON

  5.001  HEAD         DC VOLTAGE: {1V Range}
  5.002  TARGET
  5.003  IEEE         VOLT:DC:RANG 1V;*OPC?
  5.004  M550   RNGLK 3.3V
  5.005  ASK-                                        U
  5.006  5500         0.000000V                                                             E  S  2W
  5.007  ASK+                                       U
  5.008  IEEE         READ?READ?
  5.009  MATH         M[100] = MEM
  5.010  5500         1.000000V                                                             E  S  2W
  5.011  MATH         MEM = (1 + (1 - MEM1)) - M[100]
  5.012  5500         V                                                                           E  S  2W
  5.013  JMP          5.015
# This statment is only included so a compile time TUR report is possible.
  5.014  5500         1.000000V                                                             E  S  2W
  5.015  MATH         MEM1 = 1
  5.016  IEEE         READ?
  5.017  MEME
  5.018  MEMC   1     V              0.000047U

thanks

[colorado.rob]

Martin72, thanks for this info. I wil certainly try it. Any idea how many values can be put into that conversion table? Since the behaviour of NTC (and others) is strictly non-linear, the more entrires the better the precision.
Suggestion to Siglent: why not allow for entry of a math equation to define a known sensor? (More difficult to implement in soft of course)??

RikV did you ever make a table for the NTC 10k thermistor? I find I need the same thing to monitor the battery temp sense wire.

Siglent, adding NTC models to the SDM3065X would be a welcome addition. These are such common devices.

[RikV]

colorado.rob,
I did not (yet). I made an excel sheet to calculate Temp vs measured resistance and vice versa.
Indeed an urgent suggestion to Siglent! Shame on them!

This is also helpful: https://www.thinksrs.com/downloads/programs/therm%20calc/ntccalibrator/ntccalculator.html

[maralb]

We just received 2 new SDM3065X Bench multimeters at work. They came with more recent firmware than currently available at Siglents' website - 3.02.01.12R1 vs 3.01.01.12R1

[james38]

To me it looks more like a display error.
It would be more than atypical to specify such versioning. I would expect a version 3.02.0.2 or similar.
What's strange is that version 2 has exactly the same R12 as version 1. Possibly a bug in the update.

[KungFuJosh]

It's not a bug, they changed the numbering/ID scheme to be annoying. There might actually be a related hardware change, but my guess is that it's to make hacking things harder.

[Mortymore]

We just received 2 new SDM3065X Bench multimeters at work. They came with more recent firmware than currently available at Siglents' website - 3.02.01.12R1 vs 3.01.01.12R1

In Reply #1628 can be observed the same "phenomenon" on a SDM3045X.
It's not a bug. It's a bugger!

[Veteran68]

but my guess is that it's to make hacking things harder.

But this was reported on a SDM3065X. What is there to hack on that model? The only thing I could think of is adding the scanner card, but that requires hardware mods -- I think the firmware already has support for it.