Products > Test Equipment
Rigol DS1000Z series buglist continued (latest: 00.04.04.04.03, 2019-05-30)
frozenfrogz:
No problem :)
The implications of this are not very self-explanatory.
Edit: Additional Info on USB behavior and new bug regarding telnet query has been appended to the OP.
technogeeky:
--- Quote from: Karel on May 15, 2017, 07:55:34 am ---
--- Quote from: technogeeky on May 15, 2017, 02:50:59 am ---All of the features of the Keysight could easily be added to the 1054z.
--- End quote ---
I believe you make the wrong assumption that the internal system (FPGA/CPU/memory) of the scope allows for that.
It's my impression that one of the reasons for the "shitty" firmware is that there's not enough space (memory/cpu-power) to implement all the features in the correct way.
They are strugling with it. Probably, the only way to improve the firmware is to throw out half of the features...
For example, the big blunder with the USB max packetsize (64 bytes instead of 512), they can't solve it because changing the
usb stack from using 64 byte buffers to 512 byte buffers requires more memory.
--- End quote ---
I secretly hoped this counter-argument would come up. With the slow rate of patches and relatively small list of fixes in each patch, I think we really don't have any clue as to the level of ingenuity and competence of the Rigol software engineers -- at least those who work on these devices after initial release. It is possible that there is a great deal of room for optimization, or it's possible that users would choose to turn off/disable some features selectively in order to add new features or to enhance the speed of existing features. I think this could be warped to be an argument in support of releasing the firmware open source.
Part of the problem is that nobody apparently has the ear of anyone with any clout at Rigol around here. While other manufacturers have representatives on this forum, Rigol seems to keep their distance. It would be nice for someone to step in and say: I'm not an official channel, but I have the ear of xxx of Rigol engineering and I could try to be a proxy for making this case.
sandor626:
Hi,
I've updated the firmware. It's okay.
1) I downloaded the firmware from the rigol site.
2) I did the oscilloscope memory sanitization procedure. I reboot.
3) I re-calibrated. I Reboot.
4) I installed the firmware. I Reboot.
5) I checked the extended version installed (menu, menu, force, menu) and everything was ok !
6) At that moment, two new options appeared on the calibration screen. I did not re-calibrate, I Rebbot
7) After re-boot, the two new options had disappeared . I re-calibrated , successfull after 20min.
This firmware version is very very good . The trigger is better on small signals. The measures is better ,
stable Is better, stable, and equal between the channels .
Thanks Rigol !!
Nat:
So, to experienced folks out there, should I update my DS1054z (Board Version: 0.1.4, Boot Version: 0.0.1.4, Firmware Version: 0.2.3.11, CPLD Version: 1.1) to the latest firmware, given that the only thing that bother me right now is the display mode Normal that merges with Peaks.
And, yes, I've read the whole thread, still can't make up my mind.
Thanks.
(This is my first post!, fantastic forum.).
frozenfrogz:
--- Quote from: Nat on June 14, 2017, 08:01:13 am ---So, to experienced folks out there, should I update (...) ?
--- End quote ---
Of course I can not give you a definite answer, but as I see it, no devices were bricked by the current firmware. There is the one issue with failing calibration, however all units experiencing the described behavior could be recovered without any further trouble.
Update procedures are described above, but you already know that :)
If it was my scope I would drop in the update.
Regards,
Frederik
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version