When IO monitor catches an error it produces some detailed data of the error. Is there some guide for interpreting this detailed data and/or way to debug on the basis of for example the data in the output box?
IO Monitor displays the error codes that are output by the various I/O Layers. So if you are seeing errors on the VISA layer, it is a VISA error, if its on VISA COM, its a VISA COM error, etc...
Each I/O layer has its on documentation and documents all of the errors that you are seeing. You also have access to the error codes in your Development Environment so that you can trap those errors in your code and deal with them appropriately.
Do you have any specifics of what you are seeing? E.g.:
I/O Layer? Error Code? Error Message? What command are you calling when the error occurs? What I/O interface are you using? Can you attach your IO Monitor XML log and tell me which timepoint you have a question on?
" IO Monitor displays the error codes that are output by the various I/O Layers. So if you are seeing errors on the VISA layer, it is a VISA error, if its on VISA COM, its a VISA COM error, etc...
Each I/O layer has its on documentation and documents all of the errors that you are seeing. You also have access to the error codes in your Development Environment so that you can trap those errors in your code and deal with them appropriately.
Do you have any specifics of what you are seeing? E.g.:
I/O Layer? Error Code? Error Message? What command are you calling when the error occurs? What I/O interface are you using? Can you attach your IO Monitor XML log and tell me which timepoint you have a question on?
alan io support "
Everything appears to be functioning as they should be, but IO Monitor reports error in "SICL_B::tulip_unlock" and I would rather make it so that there are no errors anywhere. I am using standard VISA commands (viRead, viWrite, viClose etc.) and the error is generated in either viRead or viClose.
For security reasons I am unable to post the xml, but here is a small piece:
TimeStamp Program Address IO Layers Function Call IO Data Ret Val Time(ms)
No worries on that one... "SICL_B::tulip_unlock" will always occur in normal operation. If there is an error in a layer that is lower than the one you are using, it is usually pretty safe to ignore it (e.g. if there is no error in the VISA layer, you can ignore SICL errors).
To help clear our some of the "noise", you can modify which layers that you want to monitor. For example, if you are only interested in monitoring VISA calls, you can turn off SICL monitoring.
In Suite 15.0, you do this by:
1) Open IO Monitor, 2) Select Monitor from the menubar 3) Select Options... 4) On the Monitor tab, select only the layers that you want to monitor in [b]I/O Layers to Monitor[\b] 5) Click OK
" PS. This forum is quite slow (3,5 min. to log in @ 100Mb) at least in the modern sense. Could you please make it a little bit faster? "
Usually it zips along just fine for me even on my 750kb connection from home. However, it occasionally has hiccups, like right now (9:30 PST 8/1/08 ) it is taking forever to load. I guess contacting the administrator and letting them know would be the way to report it.
Each I/O layer has its on documentation and documents all of the errors that you are seeing. You also have access to the error codes in your Development Environment so that you can trap those errors in your code and deal with them appropriately.
Do you have any specifics of what you are seeing? E.g.:
I/O Layer?
Error Code?
Error Message?
What command are you calling when the error occurs?
What I/O interface are you using?
Can you attach your IO Monitor XML log and tell me which timepoint you have a question on?
alan
io support