Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

ilrd timeout error

JDSU is similar to JGR instruments all the commands of JGR are except the call "A05E" specific for selecting relative reference etc.. which is not affecting our ilrd call , also "?" part  it will also show same result  when i read the "valuestr" it shows P0.0 db 1335 1 ||||||||||||||||||||||
any way afteer reading its shows timeout error
0 Kudos
Message 11 of 16
(1,883 Views)

JDSU is the name of the manufacturer (http://www.jdsu.com/index.html) correct? They make a lot of instruments. What is the particular model number?

Nor can you randomly place a '?' where ever you want.

0 Kudos
Message 12 of 16
(1,882 Views)

Hi Dennis

                Please checkthis link,this guy also have the same problem

http://forums.ni.com/ni/board/message?board.id=140&thread.id=578

regards

mathewm

0 Kudos
Message 13 of 16
(1,862 Views)

HI dennis

                    Machine name:JDS Uniphase  RX3 MULTI CHANNEL BACK REFLECTION METER

                   ModelNumber : RX 3070 -2I

Hopethis will help u

regards

mathew m

0 Kudos
Message 14 of 16
(1,854 Views)

What I was hoping was that JDSU had improved their web site since the last time I used one of their instruments. I couldn't find an on-line manual before and I still can't. I wanted to look at the commands you are sending to see whether they actually returned something to the GPIB read buffer of the instrument. If you are able to sometimes read, then that indicates to me that there is nothing wrong with the basic communication. It' just that you are trying to do a read when the instrument has not been commanded to return anything.

If you have access to an electronic copy of the manual or can provide a link, I'll be happy to look at it.

0 Kudos
Message 15 of 16
(1,844 Views)

Dear Dennis

                          A  "BREAKTHROUGH"  had happened when we connect the machine with Com port communication , ie with out GPIB interface and it was fast and succesfull.So naturally we decided start with RS232 communcation now and i am thinking whether the DLL was the real cause

thanks and regards for your efforts

mathew m

0 Kudos
Message 16 of 16
(1,826 Views)