Products > Test Equipment
Pocket-Sized 6 GHz 1 TS/s ET Scope
SJL-Instruments:
To avoid confusion, we've switched to the more explicit notation shown in the attached image. Hopefully this is more clear.
joeqsmith:
It's been running since that last update and I have not detected a single glitch. I let it run overnight again using my software. This time collecting a wider range. I really have only been focusing on this one problem but I ran several tests with it yesterday and nothing else showed up.
For the manual, you may want to remove the "Single-Point Upsets". Also consider adding some additional details to the manual for the R(Acquire CDF) command. When more than one channel is selected, the manual states:
--- Quote ---The binary data consists of d chunks of 3Nch bytes each, where Nch is the number of channels requested via the bitmask. Each chunk containsNch three-byte entries, each representing a single CDF value F(V ;Δt) for each requested channel.
--- End quote ---
It wasn't clear to me how this data was formatted. I convert the entire chunk array (which includes data for all selected channels) to form a voltage/CDF array. I then decimate the data V1_Ch1,CDF1_Ch1; V1_Ch2,CDF1_Ch2; ... V1_Chn,CDF1_Chn; V2_Ch1,CDF2_Ch1; V2_Ch2,CDF2_Ch2; ... V2_Chn,CDF2_Chn; ...
where Ch is the channel number, Vt and CDFt are the voltage and CDF for a specific sample. I thought it may have sent all of the data for the first channel, then the second rather than interlace them.
SJL-Instruments:
--- Quote from: joeqsmith on January 28, 2024, 04:37:03 pm ---For the manual, you may want to remove the "Single-Point Upsets".
--- End quote ---
In the current revision (H5) of the manual, we changed this section to link to the firmware upgrade instructions. We'll remove the section once we've confirmed everyone is on the patched version.
--- Quote from: joeqsmith on January 28, 2024, 04:37:03 pm ---It wasn't clear to me how this data was formatted. I convert the entire chunk array (which includes data for all selected channels) to form a voltage/CDF array. I then decimate the data V1_Ch1,CDF1_Ch1; V1_Ch2,CDF1_Ch2; ... V1_Chn,CDF1_Chn; V2_Ch1,CDF2_Ch1; V2_Ch2,CDF2_Ch2; ... V2_Chn,CDF2_Chn; ...
where Ch is the channel number, Vt and CDFt are the voltage and CDF for a specific sample. I thought it may have sent all of the data for the first channel, then the second rather than interlace them.
--- End quote ---
We've added the attached example to the next manual revision - let us know if it's clear.
joeqsmith:
--- Quote ---When no trigger is present, the scope will trigger off its internal clock (>100 Mtrig/s) until a valid
trigger source returns.
--- End quote ---
With nothing attached to the scope's trigger your software will continue to sweep. Connecting a DC signal to the scope's inputs, you are certainly reading the correct data. When I try this with my software, the scope never appears to send data unless there is a valid trigger. Is there another command you are using to force the scope to send the data?
*** Using your software, if there is no trigger when I start, it begins to sweep. Normal. If I apply a single trigger event, the software stops sweeping and waits for further triggers. It never returns to what ever state it was in that allowed it to collect without triggers. I don't see anything in the software menus that allows me to control this. Assuming this is how you have designed it to behave, could you maybe provide further details to the manual explaining it beyond that one sentence? ***
Also, while experimenting with my own software and yours, I got the scope into some mode where when I attempt to run your software, I get the attached error. Your software would come up to the main menu but that dialog would remain. I could exit your software and restart and would get this same error. Eventually, I pulled the USB connection to the scope (power cycling it) which cleared the problem. I am not a fan of having to power cycle any device to clear an error. I don't want to be driving down the highway and have to pull over to yank the battery cable to reset the engine's computer.
SJL-Instruments:
--- Quote from: joeqsmith on January 28, 2024, 05:47:11 pm ---With nothing attached to the scope's trigger your software will continue to sweep. Connecting a DC signal to the scope's inputs, you are certainly reading the correct data. When I try this with my software, the scope never appears to send data unless there is a valid trigger. Is there another command you are using to force the scope to send the data?
--- End quote ---
There is a command that selects the internal clock source as the trigger (X1 sets internal source, X0 sets to normal trigger mode). For each acquisition, the software first tries in normal mode, and if no trigger is detected, issues the X1 command and retakes the CDF.
See attached image - we'll document this command in the next manual revision.
--- Quote from: joeqsmith on January 28, 2024, 05:47:11 pm ---It never returns to what ever state it was in that allowed it to collect without triggers.
--- End quote ---
The software should automatically return to the internal trigger ("wait") mode if no triggers are detected (e.g. the signal source is removed). What happens when you try this - does the software freeze?
--- Quote from: joeqsmith on January 28, 2024, 05:47:11 pm ---Also, while experimenting with my own software and yours, I got the scope into some mode where when I attempt to run your software, I get the attached error. Your software would come up to the main menu but that dialog would remain. I could exit your software and restart and would get this same error. Eventually, I pulled the USB connection to the scope (power cycling it) which cleared the problem. I am not a fan of having to power cycle any device to clear an error. I don't want to be driving down the highway and have to pull over to yank the battery cable to reset the engine's computer.
--- End quote ---
We can reproduce this error if some data remains in the serial buffer prior to starting our software.
We'll send you a preview build shortly that clears the buffers on startup - you can see if this fixes the problem.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version