Any Siglent sds 1202x-e owners here? (last Fw question)

[CharlotteSwiss]

I recently updated this oscilloscope to the latest revision (1.3.27). In the review notes, they list 'optimization of the USB stick when inserted into the PC'. With Fw 1.3.26 when I inserted the key into the PC after saving files from the oscilloscope, a warning told me that the key had problems and needed to be analysed. With Fw 1.3.27 same problem. Have any of you experienced this situation?
Nothing has changed here... 

[tautech]

I recently updated this oscilloscope to the latest revision (1.3.27). In the review notes, they list 'optimization of the USB stick when inserted into the PC'. With Fw 1.3.26 when I inserted the key into the PC after saving files from the oscilloscope, a warning told me that the key had problems and needed to be analysed. With Fw 1.3.27 same problem. Have any of you experienced this situation?
Nothing has changed here... 

Did you try with a freshly formatted USB ?
Format it to FAT32 with 4k clusters.

[AVGresponding]

USB drive size can be an issue sometimes as well, use a small one if you can, 4GB or so

[CharlotteSwiss]

I recently updated this oscilloscope to the latest revision (1.3.27). In the review notes, they list 'optimization of the USB stick when inserted into the PC'. With Fw 1.3.26 when I inserted the key into the PC after saving files from the oscilloscope, a warning told me that the key had problems and needed to be analysed. With Fw 1.3.27 same problem. Have any of you experienced this situation?
Nothing has changed here... 

Did you try with a freshly formatted USB ?
Format it to FAT32 with 4k clusters.

Certainly. Tried with different keys. When I insert the stick into the PC it warns that it has problems and needs to be corrected. The problem was obviously already present in previous fw. I would like to understand what those at Siglent solved (since they say so in the notes of Fw 1.3.27).

USB drive size can be an issue sometimes as well, use a small one if you can, 4GB or so

Tried any size, different manufacturers of USB sticks (from 1Gb to 16Gb), always the same problem.

[AVGresponding]

Well, I'm all out of suggestions... paging tv84!   

Has it caused any functionality problems with the scope? I didn't have any issues when I last updated mine, though that was a few months ago. Just checked and it is 1.3.27, with the OS version being 8-1, the FPGA version 2019-06-12, and the HW version 00-02.

[tautech]

Well, I'm all out of suggestions... paging tv84!   

Has it caused any functionality problems with the scope? I didn't have any issues when I last updated mine, though that was a few months ago. Just checked and it is 1.3.27, with the OS version being 8-1, the FPGA version 2019-06-12, and the HW version 00-02.

It's because the Print (screen) file has no timestamp so some PC's complain. My W10 PC does.
New FW is supposed to remedy this 

Just getting setup to do some checks about this as our new units need FW updating before dispatch.
Hopefully I'll have something to report in an hour.

FFS it's still broken ! 

[CharlotteSwiss]

Well, I'm all out of suggestions... paging tv84!   

Has it caused any functionality problems with the scope? I didn't have any issues when I last updated mine, though that was a few months ago. Just checked and it is 1.3.27, with the OS version being 8-1, the FPGA version 2019-06-12, and the HW version 00-02.

Then I'll check my version. It doesn't cause problems for the oscilloscope, but it's not nice that every time I remove the key from the Siglent, as soon as I insert it into the PC I'm told to analyze/correct it. Since in the history of the latest Fw they list this problem as 'optimized', I wanted some feedback 

Well, I'm all out of suggestions... paging tv84!   

Has it caused any functionality problems with the scope? I didn't have any issues when I last updated mine, though that was a few months ago. Just checked and it is 1.3.27, with the OS version being 8-1, the FPGA version 2019-06-12, and the HW version 00-02.

It's because the Print (screen) file has no timestamp so some PC's complain. My W10 PC does.
New FW is supposed to remedy this 

Just getting setup to do some checks about this as our new units need FW updating before dispatch.
Hopefully I'll have something to report in an hour.

FFS it's still broken ! 

Now that you talked about win10 (I'm having the problem on win8), I'll try to see on win 11 (I'm trying it). If you hear about the issue, please update us