#03 Rigol DM858 (E) DCV failure - Part 3
ฝัง
- เผยแพร่เมื่อ 28 มี.ค. 2024
- Rigol DCV failure in 01.00.00.19 and .20 version (at least).
Will occur in DCV Auto mode. Scenario is as follows:
1) free floating leads connected to DMM, while DMM setting in DCV (AUTO)
- this result in normal random small voltage in mV range (DMM switch in 1V or 100mV automatically)
2) Switch on Power supply with 33 V DC
3) Connect DMM leads directly on 33V DC outlets
- DMM remains in mV/V scale while consuming ~ 25 mA (Wrong situation)
- It stays in this faulty situation even if the Voltage is changing to lower (often 28V) and (38.. and sometimes even 60V). It looks likes there is a temperature component in the game. I have got different faulty ranges - sometimes is narrows it from 28-60 to 28-38 Volts. - วิทยาศาสตร์และเทคโนโลยี
Uma pena. Iria comprar um essa semana, vou aguardar novas atualizações :(
Vette bug zeg, dit verwacht je niet van Rigol, ik blijf dit volgen.
Ja inderdaad. Ik ben kennelijk niet de enige.
Tengo el DM858E y me falló cuando hize la medición de 380v en fuente PFC. Solo funciona en función manual (en auto no funciona) y las funciones de Ω, diodo capacitor etc.. no funcionan😢
Yep same bug, tested on a lineaire power supply and a smps. Latest firmware. DM 585
Extra info...if I try a couple of times, it start to work. Not good though
I noticed that when the device is longer switched-on the problem - or the voltage range in error [28V--50V] - becomes smaller) -> Some temperature effect?
talvez tenha problemas com cabo de força, pois no video eu acho que deveria inverter os cabos do own com rigol.
I have changed the cables - not showed on the video - this gave the same wrong result. From another user who has also the DM858 (not E version) does have the same problem. So unfortunately, it is really a bug. Question now is: Is it hardware or software.
I ordered the DM858 10 days ago from Conrad (France). Received the product not before the end of April. I will update to v00.01.00.00.20 dated 2024_03_28. We'll see if I find the same problem. This bug is totally unacceptable from a manufacturer like Rigol.
I am very interested to see if the problem is still there or not on your future DM858. Version 1.00.00.20 didn’t provide a solution for this bug (I retested it). I am afraid that it might be hardware related. It looks like the protection mechanism is kicking in before the Autorange can scale up. I would assume that the protection mechanism is not relying on Software. But we will see how Rigol will solve this problem.
@@marcelmostert3081 I received my DM858 much sooner than expected. I did the last firmware update 00.01.00.00.20 and I get exactly the same bugs. In short, we're waiting for the next update, which will correct the problems. Bad point for Rigol. 😒
@@frankkudelsko1561 Thanks for checking. Good to know that you have the same bugs - so irrelevant if it is a 858 or 858E model. Meanwhile I received the info from my supplier that they have found the right person of Rigol to take care about the DCV-failure topic. But no update received yet.
@@marcelmostert3081 Good news if your supplier has found a contact at Rigol. Now it's going to take some time for Rigol's engineers to provide a fix for the various bugs described in your videos.
Hola, mi pregunta general... El mío falló cuando hice medición de 380v. En función auto rango no me funciona, pero si lo cambio a manual si me funciona, tampoco me funcionó ya la función de Ω , diodo, capacitor ..... Me pide el vendedor que se lo regrese pero desde México a China lo veo difícil
This is not great from a brand like this.
What I also find "interesting" is that these newer models (over the DM3058[E]) the counts are lower. This seems to be a trend with Rigol? the DM3055 model had 480.000 counts, the later 3058 240.000 (or at least aound 200.000 counts) and now this latest model only 120.000. This fact alone is a big turn off for me already.
Yes, Marketing calls it 5 1/2 digit :) But it is only 20% over 5 digits. It is the bare minimum now. Wondering if Rigol 6 digits (6 1/2) will come out in this form factor - they have first to do a lot of HW reworks.
Reinstall firmware if possible ....
I have upgraded to the latest release (.20) and the bug is still there.
My works perfect. 🤔
Which Hardware version do you have?