Products > Test Equipment
Siglent SHS820X USB flash-drive port (white) only accepts USB1 gen sticks?
JAM-PDX:
--- Quote from: Psi on May 11, 2024, 10:44:16 am ---I wonder if maybe this could be a USB power issues.
I personally have had no issue with Siglent and USB devices, but obviously as USB sticks get faster and higher capacity they will need more current and higher burst currents to function correctly.
--- End quote ---
Easily could be. The larger the capacity and the newer the generation the higher the power.
Psi: is your experience statement regarding powered desktop instruments or also battery powered?
I didn't notice a difference in willingness to connect the 16G stick with charger connected or not. I haven't found anything that correlates.
I don't have a powered hub to play with, but just ordered some 2G USB2 to test... I'm assuming that's the "lowest power" test I can make with available media and play by strict USB port rules. I'll be able to compare 2G, 8G, and 16G USB2 sticks for ability to connect. That should provide some size and power data points. I kinda doubt they all run the same speed, but wouldn't know how to measure that. I'll report next Monday when I have all the media in hand.
KungFuJosh:
I don't have one of the portable scopes, but I use these without issue on all my test gear: https://www.amazon.com/gp/product/B09FFK1QLR/
Fine in 5 Siglent devices, and a bench LCR, etc...
JAM-PDX:
Testing Update:
Two different USB2 8Gb flash memory w/4K clusters appears to mount and read/write w/o issue. I would then expect the USB2 2G sticks coming will also work. Clearly there's trouble for anything larger than USB2 8G. This would seem consistent with tautech's experience.
I did notice the file Create/Modify Date as seen on Win10/11 doesn't agree with the scope time as I set (local Pacific Time Zone time); rather it looks like UTC-0. Is this a failure on my part to configure the scope, or a bug in the firmware that doesn't use set time? I suppose I can mitigate the bug by setting scope time as local and setting scope timezone as UTC-0. Does Siglent have a place to report instrument function bugs?
tautech:
--- Quote from: JAM-PDX on May 12, 2024, 10:04:41 pm ---I did notice the file Create/Modify Date as seen on Win10/11 doesn't agree with the scope time as I set (local time); rather it looks like UTC-0. Is this a failure on my part to configure the scope, or a bug in the firmware that doesn't use set time? I suppose I can mitigate the bug by setting scope time as local and setting scope timezone as UTC-0. Does Siglent have a place to report instrument function bugs?
--- End quote ---
Oh good find, will check it out and send in a possible bug report.
Edit to add
Not a bug.
JAM-PDX:
Confirmed... setting scope to UTC-0, (Atlantic Reykjavik) and resetting scope time to current local time creates scope files with Create dates that match scope time. I think this will continue to work even when I reset scope time back to local Standard Time.
I also noticed you need to press CONFIRM a second early to compensate for the internal delay in setting scope time.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version