Mine has the left and up direction key and trigger key not working and they will NOT fix it under warranty because it came form Amazon! It has a year left on the warranty. Bought in Aug 2021....not good! Will have to file a small claims suit.
Will Siglent help customers without a 500K viewer audience the same? They seem to have left quite a few people with broken scopes in the cold when some parts simply weren't mounted on the boards. Helping everyone shows dedication and that you're a serious manufacturer.
I have the sdg810 with a three year warranty. It is two years old and the left and down "direction" keys and the trigger key don't work. Only been out of the box TWICE. They WILL NOT fix it!
You said your unit is pre-production. Probably very few people if ANY have that version. How about actually "fixing" something like the left and up direction keys and trigger keys not working on my NEW (only out of the box twice since bought in Aug 2021) Siglent SDG810! Now THAT would be helpful. Your unit should be able to update firmware through the USB. using that on-motherboard SD card is arcane.
Just use the USB. Why are you fiddling with the boot sequence by soldering pads? It probably is set to boot from USB! I updated the firmware in my SDG810 over the USB with no problem. Electronic equipment made these days should NEVER be unable to boot from a panel USB port. This isn't 1970!
Hi! Great info! Where can we find the micro SD files? Can they be unpacked from the official ADS file? The thing is I had a very old version, and a USB upgrade has bricket my unit (black screen), so now I can just use the micro SD card to make it work again... Thank you in advance!
Looks like my magic ball needs recalibration :) I don't know what's the problem with sigilent tool - i have written similiar tool years ago and "run it as administrator" helped in 90% cases
that HP format software is old, and it's not needed. what that software is used for is to make some older SD cards and other flash media that aren't bootable, be able to be booted. I have no idea how the software works.
Even with pre-release sw, there should be no way for an instrument to become unbootable (unless the program flash itself is corrupted of course, which should not, unless there is a hw error). There should be a way to factory reset at the early stages of boot. So that even if there is corrupted settings or calibration data that prevents booting, it should still revert to a bootable state. Of course, proper fw should detect invalid configuration data and reset it, rather than fail to boot.
Why not? Buggy code can do all sorts of things, including data getting written to places it shouldn't be written, especially in the case of a buffer overflow etc. There's no telling what could occur when things like that happen.
User should be able to load new firmware over USB and the arcane SD card. Electronic equipment should NEVER be unable to boot firmware. The boot is supposed to be in ROM. This isn't 1970.
They should address the startup timer reset issue. It is actually a valid way of altering the value of a second hand unit. It's like changing the mileage on a car.
More worrying is the regular rewriting of the flash memory with the value, which means a page erase each time and a reprogram of the page on each power cycle. Probably not using any wear levelling on that filesystem either, so the instrument life is limited to the write lifetime of that single block of flash memory, as it probably also has a part of the boot firmware on that page as well, or at least some other volatile data. Probably best to leave it powered on all the time, though that also has issues of reducing the display lifetime amongst others.
I believe the regular firmware upgrade procedure does not reset startup counter. Because the unit was dead, Dave did a factory initialization procedure. That's why serial number was also lost.
SeanBZA if you're smart you don't do a page erase until you've filled a page. you hold # of times the page has been erased at the page start then program a sequential page word on each restart with a known constant until you hit page end. then erase and start again with an incremented erase counter.
