Iom Driver Log

windows-8-logo-png MacOS_Pnthr_Vert_v1

Overview

The information put in the log by the iom Driver is fairly easy to understand, and many problems with the iom Driver or the data connection can be determined simply by comparing a normal log with your own log. There are two samples of a normal log shown below:

  • iom Driver Startup – the process where the iom Driver starts up, connects with the hardware, and starts listening on the necessary ports.
  • iom Driver Data Request – contains the startup section of the log, as well as a request for data from a program.

Data Chain

The iom Driver is designed to start up with your system, and wait for a request on a local network port for iom Data. When it receives this request the iom Driver connects to the iom hardware, pulls in bio data, processes the data, transmits the data over the same local network port. Additionally, it contains a policy server that allows Adobe Flash to connect to the driver and get data from it.

The steps the iom Driver takes are:

  1. Startup
  2. Hardware connection and function verification
  3. Starts listening on 0.0.0.0:8888 (for commands and data) and 0.0.0.0:4242 (for policy requests)
  4. Receipt of request for data from application (for Flash, a policy request is sent first). This request contains a list of the data types required and their paramaters.
  5. Establishment of connection with iom Hardware
  6. Receipt of data from hardware
  7. Data processing completed by iom Driver
  8. Data broadcast by iom Driver
  9. Upon receipt of data termination command from program, or loss of connection with program, the driver stops processing and releases the connection with the iom hardware

Most Typical iom Driver Problems

  • Firewall blocking communication with iom Driver – if a request for data is blocked by a firewall, the iom Driver will not receive it, and will not get past step 3 in the driver chain.
  • Other application using required network port – if the iom Driver cannot listen on required ports, it cannot receive data requests, and will not get past step 2 in the driver chain.
  • Hardware failure – if there is a problem with the iom Hardware, the driver may be able to go through all the steps above, but may not receive enough information from the hardware to run properly. Additionally, in this situation, the connection with the hardware may be established and lost many times in a short period of time.

Normal Start Log

This is what is normally seen when the iom Driver starts. It starts up, connects with the hardware to make sure it is available and ready, and then starts listening on the required network sockets. 0.0.0.0:8888 is used to receive and transmit commands and data. 0.0.0.0:4242 is used for a policy file that allows Flash to connect to the driver.

04:46:06: iom Driver v.2.0.0.0
04:46:06: Initializing application…
04:46:06 AM: Initializing IOM device…
04:46:06 AM: Initializing callback…
04:46:06 AM: Received LightStoneControlPacketTypeLightStoneDeviceAdded packet

04:46:06 AM: Received LightStoneControlPacketTypeLightStoneStartedRunning packet

04:46:06 AM: Received LightStoneControlPacketTypeDeviceOpened packet

04:46:06 AM: Received LightStoneControlPacketTypeLightStoneStartedReading packet

04:46:06 AM: Received LightStoneControlPacketTypeLightStoneStoppedReading packet

04:46:06 AM: Received LightStoneControlPacketTypeDeviceClosed packet

04:46:06 AM: Received LightStoneControlPacketTypeLightStoneStoppedRunning packet

04:46:06 AM: Initializing policy server at 0.0.0.0:42420
04:46:06 AM: Server listening at 0.0.0.0:42420
04:46:06 AM: Initializing socket server at 0.0.0.0:8888
04:46:06 AM: Server listening at 0.0.0.0:8888

Normal log with data request

The following log shows normal iom Driver startup, and then a normal connection and disconnection from one of Wild Divine’s programs.

9:22:21: iom Driver v.2.0.0.0
9:22:21: Initializing application…
9:22:21 AM: Initializing IOM device…
9:22:21 AM: Initializing file playback…
9:22:21 AM: Initializing policy server at 0.0.0.0:42420
9:22:21 AM: Server listening at 0.0.0.0:42420
9:22:21 AM: Initializing socket server at 0.0.0.0:8888
9:22:21 AM: Server listening at 0.0.0.0:8888

9:24:10 AM: OnServerEvent: wxSOCKET_CONNECTION

9:24:10 AM: New client connection from 127.0.0.1:49460 accepted
9:24:10 AM: Received command message:
9:24:10 AM: Command: status
9:24:10 AM: Received command message:











9:24:10 AM: Command: start
9:24:10 AM: Received start command, gathering requested variables and parameters…
9:24:10 AM: Starting device…
9:24:40 AM: Stopping device…

Log with no receipt of data request

If a data request isn’t received by the iom Driver, there will be no change from the normal startup log. So what will be seen, is the same as the normal startup log.

Trouble shooting information can be found here.

04:46:06: iom Driver v.2.0.0.0
04:46:06: Initializing application…
04:46:06 AM: Initializing IOM device…
04:46:06 AM: Initializing callback…
04:46:06 AM: Received LightStoneControlPacketTypeLightStoneDeviceAdded packet

04:46:06 AM: Received LightStoneControlPacketTypeLightStoneStartedRunning packet

04:46:06 AM: Received LightStoneControlPacketTypeDeviceOpened packet

04:46:06 AM: Received LightStoneControlPacketTypeLightStoneStartedReading packet

04:46:06 AM: Received LightStoneControlPacketTypeLightStoneStoppedReading packet

04:46:06 AM: Received LightStoneControlPacketTypeDeviceClosed packet

04:46:06 AM: Received LightStoneControlPacketTypeLightStoneStoppedRunning packet

04:46:06 AM: Initializing policy server at 0.0.0.0:42420
04:46:06 AM: Server listening at 0.0.0.0:42420
04:46:06 AM: Initializing socket server at 0.0.0.0:8888
04:46:06 AM: Server listening at 0.0.0.0:8888

Log with iom Driver unable to listen on network port:

Trouble shooting information can be found here.

The log shows the port that the iom Driver is attempting to listen on, and then whether or not it is able to. In this example the iom Driver starts up and is unable to listen on port 0.0.0.0:4242. The pertinent lines are these:

9:26:49 AM: Initializing policy server at 0.0.0.0:42420
9:26:49 AM: Could not listen at the specified port !

This is the complete log

9:26:49: iom Driver v.2.0.0.0
9:26:49: Initializing application…
9:26:49 AM: Initializing IOM device…
9:26:49 AM: Initializing file playback…
9:26:49 AM: Initializing policy server at 0.0.0.0:42420
9:26:49 AM: Could not listen at the specified port !
9:26:49 AM: Initializing socket server at 0.0.0.0:8888
9:26:49 AM: Server listening at 0.0.0.0:8888

Log with hardware problem

Trouble shooting information can be found here.

The first section of this log file is normal. It goes through all the usual startup procedures and the driver was able to find the hardware and listen on the necessary network ports. These lines come a little bit later, and indicate that there is a problem with the hardware:

04:46:20 AM: Received LightStoneControlPacketTypeDeviceClosed packet

04:46:20 AM: Received LightStoneControlPacketTypeDeviceDataError packet

04:46:20 AM: Received LightStoneControlPacketTypeLightStoneStoppedRunning packet

The other notable thing about this log is that the connection is established and lost many times over a very short period of time. The section below is just a small part of the log file. In the full log, the connection is established and lost over 40 times over the course of a couple seconds.

04:46:06: iom Driver v.2.0.0.0
04:46:06: Initializing application…
04:46:06 AM: Initializing IOM device…
04:46:06 AM: Initializing callback…
04:46:06 AM: Received LightStoneControlPacketTypeLightStoneDeviceAdded packet

04:46:06 AM: Received LightStoneControlPacketTypeLightStoneStartedRunning packet

04:46:06 AM: Received LightStoneControlPacketTypeDeviceOpened packet

04:46:06 AM: Received LightStoneControlPacketTypeLightStoneStartedReading packet

04:46:06 AM: Received LightStoneControlPacketTypeLightStoneStoppedReading packet

04:46:06 AM: Received LightStoneControlPacketTypeDeviceClosed packet

04:46:06 AM: Received LightStoneControlPacketTypeLightStoneStoppedRunning packet

04:46:06 AM: Initializing policy server at 0.0.0.0:42420
04:46:06 AM: Server listening at 0.0.0.0:42420
04:46:06 AM: Initializing socket server at 0.0.0.0:8888
04:46:06 AM: Server listening at 0.0.0.0:8888
04:46:20 AM: Policy file request received…
04:46:20 AM: OnServerEvent: wxSOCKET_CONNECTION

04:46:20 AM: New client connection from 127.0.0.1:53461 accepted
04:46:20 AM: Received command message:
04:46:20 AM: Command: status
04:46:20 AM: Received command message:











04:46:20 AM: Command: start
04:46:20 AM: Received start command, gathering requested variables and parameters…
04:46:20 AM: Starting device…
04:46:20 AM: Received LightStoneControlPacketTypeLightStoneDeviceAdded packet

04:46:20 AM: Received LightStoneControlPacketTypeLightStoneStartedRunning packet

04:46:20 AM: Received LightStoneControlPacketTypeDeviceOpened packet

04:46:20 AM: Received LightStoneControlPacketTypeLightStoneStartedReading packet

04:46:20 AM: Received LightStoneControlPacketTypeLightStoneStoppedReading packet

04:46:20 AM: Received LightStoneControlPacketTypeDeviceClosed packet

04:46:20 AM: Received LightStoneControlPacketTypeDeviceDataError packet

04:46:20 AM: Received LightStoneControlPacketTypeLightStoneStoppedRunning packet

04:46:20 AM: Received LightStoneControlPacketTypeLightStoneDeviceAdded packet

04:46:20 AM: Received LightStoneControlPacketTypeLightStoneStartedRunning packet

04:46:20 AM: Received LightStoneControlPacketTypeDeviceOpened packet

04:46:20 AM: Received LightStoneControlPacketTypeLightStoneStartedReading packet

04:46:20 AM: Received LightStoneControlPacketTypeLightStoneStoppedReading packet

04:46:20 AM: Received LightStoneControlPacketTypeDeviceClosed packet

04:46:20 AM: Received LightStoneControlPacketTypeDeviceDataError packet

04:46:20 AM: Received LightStoneControlPacketTypeLightStoneStoppedRunning packet

04:46:21 AM: Received command message:











04:46:21 AM: Command: start
04:46:21 AM: Received start command, gathering requested variables and parameters…
04:46:21 AM: Starting device…
04:46:21 AM: Received LightStoneControlPacketTypeLightStoneDeviceAdded packet

04:46:21 AM: Received LightStoneControlPacketTypeLightStoneStartedRunning packet

04:46:21 AM: Received LightStoneControlPacketTypeDeviceOpened packet

04:46:21 AM: Received LightStoneControlPacketTypeLightStoneStartedReading packet

04:46:21 AM: Received LightStoneControlPacketTypeLightStoneStoppedReading packet

04:46:21 AM: Received LightStoneControlPacketTypeDeviceClosed packet

04:46:21 AM: Received LightStoneControlPacketTypeDeviceDataError packet

04:46:21 AM: Received LightStoneControlPacketTypeLightStoneStoppedRunning packet

04:46:21 AM: Received command message:











04:46:21 AM: Command: start
04:46:21 AM: Received start command, gathering requested variables and parameters…
04:46:21 AM: Starting device…
04:46:21 AM: Received LightStoneControlPacketTypeLightStoneDeviceAdded packet

04:46:21 AM: Received LightStoneControlPacketTypeLightStoneStartedRunning packet

04:46:21 AM: Received LightStoneControlPacketTypeDeviceOpened packet

04:46:21 AM: Received LightStoneControlPacketTypeLightStoneStartedReading packet

04:46:21 AM: Received LightStoneControlPacketTypeLightStoneStoppedReading packet

04:46:21 AM: Received LightStoneControlPacketTypeDeviceClosed packet

04:46:21 AM: Received LightStoneControlPacketTypeDeviceDataError packet

04:46:21 AM: Received LightStoneControlPacketTypeLightStoneStoppedRunning packet

ADDITIONAL INFORMATION and SUPPORT

Contact Support

If you are still experiencing issues with IomDriver or yoru IomPro or Lighstone hardware you can contact us at Technical Support for further assistance.

© Copyright Wild Divine, Inc. All rights reserved.