TcubedCollectIR SubNet IO      
 Back Home Up Next

SubNetIo Icon    The SubNetIO application is used to obtain IR Tag data from a CollectIR system.

The SubNetIO application can be configured to send arriving tag data to one or more Event Processors using either DDE, NetBios or TCPIP communications.  Multiple SubNetIO applications can be run on a network allowing data to be collected from any number of PC's connected to CollectIR Concentrators (Internal, Arcnet or Ethernet).  SubNetIO can be run under Windows 3.11, Windows 95/98 or Windows NT 4.0.

The following screen depicts the typical appearance of the SubNetIO application. 

     subnetIo_s1.gif (8585 bytes)  

The following is a brief description of each field displayed.

bulletBlocks Received - CollectIR sends up to 12 tags per block, this is how many blocks have been received
bulletTags Received - This is the number of tag receptions from CollectIR
bulletReceive Errs - This is the number of Blocks/Tags which contained invalid data.  If this number gets large then there is probably something wrong with your hardware/configuration.
bulletSubNet Ignores - If SubNetIO is busy processing transmit requests it MAY ignore incoming data, this counter indicates how many blocks of data have been ignored.
bulletTraps Received - If the CollectIR SNOID DLL traps an error this counter is incremented.   See your SNOID.LOG file for details.
bulletSend after - This value indicates how much transmission delay/buffering that SubNetIO is configured to perform.  In systems with many tags, it is desirable to have SubNetIO buffer transmissions to the Event Processor to achieve better system efficiency by minimizing the number of transmits made to the Event Processor.
bulletSends Queued - This is the total number of sends queued for transmission currently.   If communications to your Event Processor are working smoothly, this number will remain zero.  If your system/network becomes very busy you may see some queuing.   No data is lost, it is just delayed until the system/network gets time for transmission.
bulletEP Sends - This is the number of data transmissions to your Event Processor.
bulletEP Send Errs - This is the number of transmits which were attempted, but errors occurred in the transmission.  In many cases this will cause the data that was to be transmitted to be queued (see Sends Queued)
bulletLast EP Send Size - This is the number of tags that were last sent to the Event Processor.  This gives you some idea regarding the volume of tag transmissions being sent to the Event Processor.
bulletSend to - This is either a DDE/Name or NetBios name used to communicate with your Event Processor, or it is the TCPIP address/Port of your Event Processor.

The next set of information refers to how other applications can communicate to the SubNetIO application.

bulletDepending on which communications mechanisms are configured (via the SUBNETIO.CFG file) your Local TCPIP address and port will be displayed here.  If NetBios/DDE input is supported then your NetBios connection name will also be displayed.

The next window (or drop down list) shows the Concentrator Id(s) that are communicating with SubNetIO.

The next section is for display options

bulletShow Collector Stats displays what sensors have seen data.  This is useful in diagnosing sensor problems. (see the screen shown below)
subnetIo_s2.gif (9990 bytes)
bulletShow Exceptions (the default) shows test relating to any error conditions detected.

Last Modified: February 11, 2003