I have been using a PCS500 for some time, capturing data in Excel using the ReadCh1 and ReadCh2 functions. I thought I mastered this, but have been getting results that perplex me.
I thought that these functions flowed from the Transient Recorder module, and followed the settings entered there, but:
I get no data reported unless the Oscilloscope is on Run
Running the TR seems to turn the Osc off
But at the same time, the Volts/Div seems to be governed by the TR settings, not the Osc
Could you please clarify for me which settings govern the Excel output? I am also unclear about the relationship between the Time/Div setting and the Hz value reported to Excel.
For volts, I understand, for example, that 5 Volts/Div is reported as 581000=40000 mV full scale, correct?
In case it helps, here is the VBA data capture routine I am using …
Thank you!
Phil
Option Explicit
Dim DataBuffer1(0 To 5000) As Long
Dim DataBuffer2(0 To 5000) As Long
Private Declare Sub ReadCh1 Lib "DSOLink.dll " (Buffer As Long)
Private Declare Sub ReadCh2 Lib "DSOLink.dll " (Buffer As Long)
Sub Read_PCS500()
Dim i As Long
ReadCh1 DataBuffer1(0)
ReadCh2 DataBuffer2(0)
With ActiveSheet
For i = 0 To 800
.Cells(i + 1, 8) = DataBuffer1(i)
.Cells(i + 1, 9) = DataBuffer2(i)
Next i
End With
End Sub
[quote]- I get no data reported unless the Oscilloscope is on Run
Running the TR seems to turn the Osc off[/quote]The oscilloscope will be running in the background until the “Run” button is pressed in the Transient Recorder.
The DSOLink is not usable in the Transient Recorder mode.
[quote]- But at the same time, the Volts/Div seems to be governed by the TR settings, not the Osc[/quote]This bug will be fixed in the next release.
As a workaround you may do following:
In the Oscilloscope mode click the “Run” button ‘up’ to stop the run mode.
Now you can click the Transient Recorder button.
By doing these steps, the transient recorder settings are not exported to your Excel application.
So you mean that the Oscilloscope should appear to be “off” and the TR “on”? I think this is what I used to do, thinking that the DSOlink actually worked with the TR, not with the scope.
But recently I found that I was getting no data unless I turned the scope back on, hence my current confusion.
So I will try this, but I am afraid it will once again stop providing any data at all …
Finally, just to be sure I have understood you, when the Oscilloscope is off" and the TR is “on”, DSOlink will nevertheless follow the settings scope settings? Very strange …
It seems to me that the behaviour changed when I started simultaneously using a PCS10, with the fast-response fixes. Could there be any relationship between the two?
[quote]But recently I found that I was getting no data unless I turned the scope back on, hence my current confusion.
So I will try this, but I am afraid it will once again stop providing any data at all …[/quote] It will provide data again when you click the button “Oscillosope” and then press the “Run” button.
Should not provide data in the Transient Recorder mode.
There is a minor bug in the software:
Now provides data also in the Transient Recorder mode until Transient Recorder’s “Run” button is pressed.
This problem occurs only if the oscilloscope is left running.
When the bug is fixed (in next release), no data will be provided in the Transient Recorder mode.
Now you can bypass the problem by turning the oscilloscope off before you switch to the Transient Recorder mode.
[quote]Finally, just to be sure I have understood you, when the Oscilloscope is off" and the TR is “on”, DSOlink will nevertheless follow the settings scope settings? Very strange …[/quote]Yes, the DSOLink should be only “tied” to the oscilloscope’s data and settings.
In the next release the DSOLink will not send any data in the Transient Recorder mode.
[quote]
It seems to me that the behaviour changed when I started simultaneously using a PCS10, with the fast-response fixes. Could there be any relationship between the two?[/quote]No, I think.