I need to watch for deviant conditions with my new SDS1104 X-E.That is called data logging. The scopes from GW Instek and Yokogawa have this feature.
Would love to be able to plug a flash drive into USB and set the scope to store all acquired waveforms directly to the stick while I am off doing something else. Until memory is full or I stop it.
Is this a thing available. And yes the events are spaced far enough apart so that a file could be written before the next likely event.
The 1000X-E does indeed seem to lack this. Even the beeper function is quite under-developed. (The beeper continuously alerts after the first failure, but with variable delay between beeps, which makes it sound as if the scope was complaining about new failures.)I think you could offer better/more info.
One more item for the "alternative firmware" to do list, I guess ;-)
Certainly Pass/Fail can do this
You have a perfectly capable tool and all that is required is some thought as to how to best use it. :)
If you can translate the excursion to a specific trigger, then you have more options.There are a few work around's, Runt and Period triggers spring to mind.
Would love to be able to plug a flash drive into USB and set the scope to store all acquired waveforms directly to the stick while I am off doing something else. Until memory is full or I stop it.
But the purpose of data logging is to do a very long term measurement to find a very rare event. Maybe even with power cycles in between. Storing data of each waveform with maximum details will be useful here because you can't reproduce it quickly let alone go back and adjust a trigger condition.If you can translate the excursion to a specific trigger, then you have more options.There are a few work around's, Runt and Period triggers spring to mind.
Once you know what the excursion is and how to accurately and repeatably trigger on it the battle is won.
Then we have the other channels to find an event correlation on signals that are the cause of it.
I need to watch for deviant conditions with my new SDS1104 X-E.
Would love to be able to plug a flash drive into USB and set the scope to store all acquired waveforms directly to the stick while I am off doing something else. Until memory is full or I stop it.
Is this a thing available. And yes the events are spaced far enough apart so that a file could be written before the next likely event.
The trigger event will happen maybe once an hour. I want the scope to log the entire waveform. The record length will be set to 10M points or whatever is practical.
I need to be able to review the stored waves to find a deviant event in product testing. Sampling speed of 100k/sec would be about right.
I am reading GW instek manual 1000B series but I cannot confirm that the waveforms are stored to internal memory automatically.
Anybody know for sure of a scope to do this?
Now, I don't know if any scope lets you have a regular capture running during a pass/fail test,
The trigger event will happen maybe once an hour. I want the scope to log the entire waveform. The record length will be set to 10M points or whatever is practical.I did some testing with my GDS-2204E and the data logging app. This seems to work but there is one issue though. You need to set a capture interval with a minimum time of 2 seconds. This interval seems to count down only when the oscilloscope is acquiring data. To capture each trigger event you have to make sure acquiring the waveform takes 2 seconds or more. A timebase setting of 200ms/div will do that.
I need to be able to review the stored waves to find a deviant event in product testing. Sampling speed of 100k/sec would be about right.
I am reading GW instek manual 1000B series but I cannot confirm that the waveforms are stored to internal memory automatically.
Anybody know for sure of a scope to do this?
Thanks for all input.Not once have you described the 'event' !
Would really like it to be all in the scope but I guess that doesn't exist.
Scope builders it would be a good feature....
tauSCPI commands are NOT my strength, if fact a weakness, however I'd be VERY surprised if this ^ cannot be done with the SCPI command set in most DSO's.
If i were designing the feature for my scope the 'event' is any acquisition.
Very simply.
1 wait for trigger.
2 after one triggered sweep, stop and write file to USB.
3 re arm trigger.
4 goto 1
Cmon, get that feature implemented. Would pave the way for scopes to cross over into data logging territory.
tauAs I wrote before: Yokogawa scopes have this feature for sure. The GW Instek scopes can do this too with a simple workaround. I just checked and the data logger application is also available for the GDS1000B series.
If i were designing the feature for my scope the 'event' is any acquisition.
Very simply.
1 wait for trigger.
2 after one triggered sweep, stop and write file to USB.
3 re arm trigger.
4 goto 1
Cmon, get that feature implemented. Would pave the way for scopes to cross over into data logging territory.
he said he doesnt want any programming or any PC related mess, he wants "built-in to the scope". if 100 people with 100 different trigger/logging requirements, the scope should implement them all. ::)tauSCPI commands are NOT my strength, if fact a weakness, however I'd be VERY surprised if this ^ cannot be done with the SCPI command set in most DSO's.
If i were designing the feature for my scope the 'event' is any acquisition.
Very simply.
1 wait for trigger.
2 after one triggered sweep, stop and write file to USB.
3 re arm trigger.
4 goto 1
Cmon, get that feature implemented. Would pave the way for scopes to cross over into data logging territory.
Where ?he said he doesnt want any programming or any PC related mess, he wants "built-in to the scope". if 100 people with 100 different trigger/logging requirements, the scope should implement them all. ::)tauSCPI commands are NOT my strength, if fact a weakness, however I'd be VERY surprised if this ^ cannot be done with the SCPI command set in most DSO's.
If i were designing the feature for my scope the 'event' is any acquisition.
Very simply.
1 wait for trigger.
2 after one triggered sweep, stop and write file to USB.
3 re arm trigger.
4 goto 1
Cmon, get that feature implemented. Would pave the way for scopes to cross over into data logging territory.
tau
If i were designing the feature for my scope the 'event' is any acquisition.
Very simply.
1 wait for trigger.
2 after one triggered sweep, stop and write file to USB.
3 re arm trigger.
4 goto 1
Cmon, get that feature implemented. Would pave the way for scopes to cross over into data logging territory.
I need to watch for deviant conditions with my new SDS1104 X-E.Further thoughts......
Would love to be able to plug a flash drive into USB and set the scope to store all acquired waveforms directly to the stick while I am off doing something else. Until memory is full or I stop it.
Is this a thing available. And yes the events are spaced far enough apart so that a file could be written before the next likely event.
I have three stations I need to monitor signals on for the errant condition. Asked boss if we can buy three budget scopes for this as this is the only way.whats the budget? if its $300 per scope then there is an offer in ebay right now... https://www.ebay.com.my/itm/RIGOL-DS1054Z-Digital-Oscilloscope/273448409163?hash=item3faacb984b:g:7skAAOSwFdpbMgGb (https://www.ebay.com.my/itm/RIGOL-DS1054Z-Digital-Oscilloscope/273448409163?hash=item3faacb984b:g:7skAAOSwFdpbMgGb) ;D
The machines are each have a pc running a VB6 program.you are just one step close to what you want. there is programming guide for siglent, but if you dont want to invent a wheel, get a DS1054Z and someone or me may help you in programmming for a pack of coffee. ;)
I plan to add serial ports to each pc via USB and edit the code to output a byte ( any byte will do ) if the event happens which will trigger a single capture on my cheap scopes because they will be monitoring the TX data line out of the serial port.sounds like a nasty/poor hack, lets hope the cheap scope can send back the data or save it internally upon pc command.
You would love to but X-E DSO's are not the correct tool to do this. For one they have no RTC to give timestamps as when an event occurs.
ntpd -n -d -p 201.217.3.85I plan to add serial ports to each pc via USB and edit the code to output a byte ( any byte will do ) if the event happens which will trigger a single capture on my cheap scopes because they will be monitoring the TX data line out of the serial port.
Can you please share all about this in the SDS1104/1204X-E thread ?You would love to but X-E DSO's are not the correct tool to do this. For one they have no RTC to give timestamps as when an event occurs.
Just connect Ethernet to your 1000X-E, log in (as root), make sure it can reach the global Internet, then runCode: [Select]and watch the miracle unfold :-)ntpd -n -d -p 201.217.3.85
Can you please share all about this in the SDS1104/1204X-E thread ?
Some 'dummy guide' and usage examples would be much appreciated. :)