Hello,
I am trying to communicate with an Agilent 33250A Pulser via NI GPIB-ENET/100. When I use the GPIB explorer in Linux, I scan the local subnet for the device and it can not seem to find it. However, I can ping it and get a response.
I also tried to just enter the IP in the GPIB explorer and then run the NI-488.2 Troubleshooting Wizard. The first two stages pass but the "GPIB Interfaces Sequentially" test does not. Below is a copy of the NI I/O Trace capture:
> 1. ibfind(GPIB0)
> Process ID: 0x0000117C Thread ID: 0x004AFB30
> Start Time: 13:36:34.082 Call Duration 00:00:10.012
> ibsta: 0x8000 iberr: 0 ibcntl: -519700363(0xe1060075)
> 2. ThreadIberr()
> Process ID: 0x0000117C Thread ID: 0x004AFB30
> Start Time: 13:36:44.094 Call Duration 00:00:00.000
> ibsta: 0x8000 iberr: 0 ibcntl: -519700363(0xe1060075)
> 3. ThreadIbsta()
> Process ID: 0x0000117C Thread ID: 0x004AFB30
> Start Time: 13:36:44.094 Call Duration 00:00:00.000
> ibsta: 0x8000 iberr: 0 ibcntl: -519700363(0xe1060075)
> 4. ThreadIbcnt()
> Process ID: 0x0000117C Thread ID: 0x004AFB30
> Start Time: 13:36:44.094 Call Duration 00:00:00.000
> ibsta: 0x8000 iberr: 0 ibcntl: -519700363(0xe1060075)
I have already been successful with this task in Windows Labview and can see the ENET and Instrument fine with MAX in Windows.
Any help would be great!
-Robert
