Feature Suggestions for the SDG-2000X:
1. allow a modulating wave shape (MDSP) for FSK so that a square wave signal can be uploaded to modulate an arbitrary bit sequence (example: "C1:MDWV FSK,MDSP, ARB")
2. allow the modulator to use the other channel as the signal source (example: "C2:MDWV PWM,MDSP, C1")
Right now the FSK modulation feature is rather limited. One can only modulate a simple square wave or it requires using an external source. It seems like an oversight not to allow an uploaded wave form to modulate the FSK signal.
Rob
Hi everyone,
I had my old channel deleted.
Here is the video in my new youtube channel.
Enjoy!
Electro Detective is not the only one that thinks Siglent's DSO firmware updating is a mess.
https://www.eevblog.com/forum/testgear/siglent-cml-firmware/msg1197684/#msg1197684
Confusion with the filenames, is there info in the filename?
Confusion with cfg files, where are they?
Confusion over whether or not you can jump over a version.
The Change Log. LOL
Are they trying to support different (possibly undocumented) hardware versions, different bootloader versions?
Does the firmware do any basic checks to check the hardware is compatible?
At least you don't have to worry about the power going off during the 2 minutes of upgrading - that's the least of your worries.
@Electro Detective
How did you update config? This last update package do not have config file at all.
There is long way from 5.01xxxx to 5.03xxxx. Perhaps there is some previous update what have included also config update file. I do not know but I feel that perhaps this version jump is too big and it need first do some intermediate update before this last version. I do not remember what all versions have included needed new cnf file. Perhaps before this last update it first need some previous version update, example: SDS1000CFL_4CH Version: 5.03.02.12 | Published?2014-09-26. There is also new config for 5.03xxxx versions.
But, I do not know if you can now downgrade and update this previous version first before last version or do it now need some "trick".
I recommend to contact Siglent China Engineer who know what and how to do now. Best that do not try enything before get real information based to real knowledge. (Siglent Engineer) For avoid more problems.
@Electro Detective
How did you update config? This last update package do not have config file at all.
There is long way from 5.01xxxx to 5.03xxxx. Perhaps there is some previous update what have included also config update file. I do not know but I feel that perhaps this version jump is too big and it need first do some intermediate update before this last version. I do not remember what all versions have included needed new cnf file. Perhaps before this last update it first need some previous version update, example: SDS1000CFL_4CH Version: 5.03.02.12 | Published?2014-09-26. There is also new config for 5.03xxxx versions.
But, I do not know if you can now downgrade and update this previous version first before last version or do it now need some "trick".
I recommend to contact Siglent China Engineer who know what and how to do now. Best that do not try enything before get real information based to real knowledge. (Siglent Engineer) For avoid more problems.
Maybe the Siglent firmware notes should say whether you can jump over versions or need specific intermediate versions.
@Electro Detective
How did you update config? This last update package do not have config file at all.
There is long way from 5.01xxxx to 5.03xxxx. Perhaps there is some previous update what have included also config update file. I do not know but I feel that perhaps this version jump is too big and it need first do some intermediate update before this last version. I do not remember what all versions have included needed new cnf file. Perhaps before this last update it first need some previous version update, example: SDS1000CFL_4CH Version: 5.03.02.12 | Published?2014-09-26. There is also new config for 5.03xxxx versions.
But, I do not know if you can now downgrade and update this previous version first before last version or do it now need some "trick".
I recommend to contact Siglent China Engineer who know what and how to do now. Best that do not try enything before get real information based to real knowledge. (Siglent Engineer) For avoid more problems.
Maybe the Siglent firmware notes should say whether you can jump over versions or need specific intermediate versions.
Actually, this is something that we have started doing but we will remind those involved of the importance of it. Some product families have probably been better than others.
Thanks for the reminder.
Thanks.
Actually, our upgrade path's are normally located in the FW upgrade file itself. There is a PDF with instructions. The entire filed is compressed into a .RAR file.
We are working on some website upgrades and we planning for improvements.
Stay tuned!
Electro Detective, I think rars are OK.
While we're giving Siglent a hard time, what does "our upgrade path's are normally located in the FW upgrade file itself." actually mean.
FWIW, the most recent SDG2000X firmware upgrade comes in a .rar file. When you unpack that file it gives you a file that is the actual .ads update file (with no .cfg file for this particular update), and it gives you a "Firmware Revise History & Update Instructions" .pdf file. In the .pdf file is a chronological listing of the updates with file name and date, and for each file is a list of the features or bugs addressed including descriptions of the features or bug fixes. However, there is no mention of what updates can be applied with or without previous updates. To be clear, listing the firmware updates in order of release is not the same as specifying which updates can be applied regardless of previous firmware status and which updates require one or more interim updates. This might not seem like a big distinction, but for a user bricking an update the experience becomes a frustrating loss of time in trying to correct the problem along with a loss of the productive use of the product, and for Siglent and it's distributors it only adds work and cost while potentially jeopardizing future sales.
Siglent, I think what users are saying is that while it is impressive that rf-loop and tautech and others are offering their best possible assistance to Siglent users and potential Siglent users around the world, it would be helpful if the firmware updates had better documentation.
As Electro Detective (no relationship to Electro Fan, whatsoever) has said: it is the manufacturer's RESPONSIBILITY to inform the end user of the correct sequence, to avoid either bricking the unit or introducing erratic performance.
FWIW, I've just made the decision to purchase a SDG2042X so I don't have any experience yet with the product, but in looking ahead to possibly having to update the firmware in a unit that has possibly been sitting in a distributor's inventory for awhile, I think there is room for improvement in how firmware updates are documented. The good news as I see it is that 1) the SDG2K is capable of offering very good features and performance and 2) it looks like Siglent has been providing firmware updates about every 3-6 months. So why not capitalize on all the good work that has gone into designing, manufacturing, distributing, and supporting this product (and other Siglent products) by improving the documentation (for both the product manuals and the updates)?
Hoping to become a Siglent fan, EF
Why these things happen I am at a loss to understand, the only suggestion I can offer is to return all units to factory default before installing updates.
This is not documented but as I have zero problems with new equipment FW upgrades before they are dispatched I wonder if this may be the issue.
Before you say Siglent needed to have checked the FW before release, think about this; how many user setups and control conditions would need to be individually checked before guaranteeing no problems will exist after updating the FW ?
I intend to explore this with tech support and maybe have some instruction in future FW to say: return to factory default before updating.
Why these things happen I am at a loss to understand, the only suggestion I can offer is to return all units to factory default before installing updates.
This is not documented but as I have zero problems with new equipment FW upgrades before they are dispatched I wonder if this may be the issue.
Before you say Siglent needed to have checked the FW before release, think about this; how many user setups and control conditions would need to be individually checked before guaranteeing no problems will exist after updating the FW ?
I intend to explore this with tech support and maybe have some instruction in future FW to say: return to factory default before updating.
If the device's configuration can cause the update process to fail, then the firmware update mechanism should must restore the factory defaults at the very beginning of the upgrade process, and the firmware update instructions should make it clear that this is what will happen. Obviously, then, the unit should provide a way to save and restore the unit's configuration, and it should do it in such a way as to make it difficult for the firmware to improperly set things up after the upgrade (the easiest way to ensure this is to use a text file to represent the configuration, which will force the firmware to parse the configuration file so that, at least, you don't wind up with otherwise-impossible settings resulting from some binary file mixup like you easily could if the settings file were just a memory dump or something).
Siglent, the detailed firmware information provided on this oscilloscope model looks really good; this level of detail is very useful and helpful.
As noted it appears that some product lines have more detailed documentation than others within the overall product family. Maybe someone from Siglent could help MrW0lf (and possibly other users or potential users) with some more detailed guidance on the firmware user name and password process he is working through with the most recent firmware update (as being discussed over in the Siglent SDG2042X Thread)? Thx
https://www.eevblog.com/forum/testgear/the-siglent-sdg2042x-thread/msg1204362/#msg1204362
Siglent, the detailed firmware information provided on this oscilloscope model looks really good; this level of detail is very useful and helpful.
As noted it appears that some product lines have more detailed documentation than others within the overall product family. Maybe someone from Siglent could help MrW0lf (and possibly other users or potential users) with some more detailed guidance on the firmware user name and password process he is working through with the most recent firmware update (as being discussed over in the Siglent SDG2042X Thread)? Thx
https://www.eevblog.com/forum/testgear/the-siglent-sdg2042x-thread/msg1204362/#msg1204362
Thank you, Electro Fan.
We did reach out to one of the people in this thread via PM who was having a problem.
Anyone can also write to us here at our USA office at
info@Siglent.com
We are still working on ways to improve procedures and decimating information. We have made improvements but we are still working on it.