Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

Ni Spy logging problem

I'm using Ni Spy version 2.7.2 and one task is to verify GPIB-commands send to measurement devices. I can do live capture and check traffic there but there is need to automate this process. I checked and tested logging possibilities that Ni Spy offered but ran into following problem. When saving captured trace to text formatted file (in this case .txt or .csv), actual GPIB-command is in log but if it is long enough log string is cut down and rest of it is replaced with 3 dots. This can be see also in live capture where description field has limited lenght, there user can look at buffer input and see total GPIB command.

Question, is there any option or other way to get whole buffer text to text log file? In .spy capture file you can see this but I couldn't get this working in text formated capture file.

0 Kudos
Message 1 of 5
(3,277 Views)

try setting the buffer size from small to large for Buffer Limit per parameter.

Regards
Ray Farmer
0 Kudos
Message 2 of 5
(3,274 Views)

I tried that and it didn't help. Ni Spy seems to write only description field to text log and that has limited field lenght I quess.

0 Kudos
Message 3 of 5
(3,265 Views)

I write a litter application to export the NISpy buffer to text file.May be you can try it.I only test it on NI Spy 2.7.2

Please decompress the attachment with winrar.

0 Kudos
Message 4 of 5
(3,209 Views)

Hi again and sorry for late answer to proposal, I did find solution before this but forgot to report it here. When I was testing text formatted log file I did use only csv-format because it would have been easy to handle later on programmatically. It did have these side affects but when I tested to log into txt-formatted file description information was written to log file and I could proceed with my program.

So solution was to use in logging .txt-type, not .csv :).

0 Kudos
Message 5 of 5
(3,173 Views)