12-06-2023 12:40 PM
Hello,
I have a continuous error occurring,
I have tried instrument timeout although I don't show that in the below code.
Increasing Instrument timeout did not seem to make any difference.
This is a Ethernet connection - Vektrex SpikeSafe SMU, Windows 10- LabVIEW 2020 32 bit
How would I be sure that my query is not being interrupted prematurely & clear the error ?
12-07-2023 01:49 PM
1. You should probably have a wait after the reset to allow the instrument time to reset before sending the next command.
2. Is the MEMORY:TABLE:READINGS supposed to be a query? If so, you are missing the question mark at the end. Also, you should be performing a read immediately after the sending of the query to make sure nothing else is getting in there are you. If it is not a query, I would have to find the manual to figure out what you are doing there.
12-07-2023 02:12 PM
2.5.1 Get SpikeSafe Status
This query obtains status information for all channels and the module itself. The data format used for readings
is described below. The readings reported are voltage and current, with present channel on/off status added to
the end of each channel’s information. Also included in this data are the 4 heat sink temperature readings in
degrees Centigrade. The entire message is a single string that has a max length of 299 bytes.
NOTE: SS400 model varies between 1 to 8 channels but will always report 4 heat sink temperatures. SS400
Mini or PSMU is always 1 channel and will always report 1 heat sink temperature.
NOTE: On average this query takes between 5ms to 18ms to respond varying based upon the SS400 model.
Syntax
Query MEMory:TABLe:READings
even though they call it a query ,I don't see the ?
Well thank you for the response you got me thinking I might try to break up the two queries and do them separately so I may have some fundamental code error here.
I'll post again if I get a solution...
12-08-2023 12:32 PM
above is what I ended up with, decreasing the count in the re-statement seem to get rid of the timeout error
I put the reset in there because I thought I might want to have it handy when this gets integrated into the grand scheme of things but I probably won't use it anyway
Thanks again for responding to me