Using LAN Interface Sessions

The LAN interface, unlike most other supported SICL interfaces, does not allow for direct communication with devices via interface commands. LAN interface sessions, if used at all, will typically be used only for setting the client-side LAN timeout. (See Using Locks, Threads, and Timeouts.)

Subtopics are:

Addressing LAN Interface Sessions

To create a LAN interface session, specify the interface logical unit or interface name in the addr parameter of the iopen function. The interface logical unit and SICL interface ID are defined by the Connection Expert utility.

SICL Interface ID Examples

lan

A LAN interface address using the interface name lan.

30

A LAN interface address using the logical unit 30. (30 is the default logical unit for LAN.)

SICL Function Support

These SICL functions are not supported over LAN interface sessions; they return I_ERR_NOTSUPP.

  • All GPIB specific functions
  • All serial specific functions
  • All formatted I/O routines
  • iwrite, iread, ilock, iunlock, isetintr, itrigger, ixtrig, ireadstb, isetstb, imapinfo, ilocal, iremote

These SICL functions perform as follows with LAN interface sessions.

SICL Functions for LAN Interface Sessions

iclear

Performs no operation, returns I_ERR_NOERROR.

ionsrq

Performs no operation against LAN gateways for SICL, returns I_ERR_NOERROR.

ionintr

Performs no operation, returns I_ERR_NOERROR.

igetluinfo

Returns information about local interfaces only. Does not return information about remote or LAN interfaces.