GPIB ENET/1000 and the PharLap TNT Real-Time DOS Extender

[Chong_TC]

Hi.

My company is currently working with NI GPIB ENET/100 box, through ESP source code.

Since the GPIB ENET/100 is replacing by GPIB ENET/1000, we are undergoing the migration stage. After getting the new GPIB ENET/1000, and configure it to static IP (172.20.190.xxx) through MAX, we tried to swap in this new box to our system that is already running correctly with the old GPIB ENET/100 box. 

However, the result is negative. When the system init, the GPIB ENET/1000 READY LED immediately turn to error mode (RED blinking with error code of 2-long and 8-short). After code tracing, we found out that, during the call to the ibfind( ) function in ESP code:

a. if the Role is set to BOARD, the new GPIB ENET/1000 turned error immediately when data is written to it through TCP with the command EG_DEV (0x07).Note that, the data passed is the bdinfo structure (Board and device info structure defined in ESP header file).

b. If the Role is set to DEVICE, there is no problem to pass the bdinfo structure (defined in ESP header file) with the command EG_DEV (0x07) for Device setting, followed by Board setting (of bdinfo structure). However, the next command passed (which is within the ibfind( ) body), the command EG_ONL (0x12), causes the same error (RED blinking with error code of 2-long and 8-short) at the new GPIB ENET/1000 too.

The questions I have:

1. How we could make the new GPIB ENET/1000 work with the ESP488 source code?

2. Is the above is negative, what is the option for code migration, to make system able to communicate with the new GPIB ENET/1000? Note, the system is running on he PharLap TNT Real-Time DOS Extender. 

Thanks.

With warm regards,

Chong TC