Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
HAI OmniProII Driver problems
#1
I have the following setup:

HAI OmniProII with Firmware v3.14a (fully configured)


CQC v5.0 installed on Windows 8.0

The OmniProII TCP driver v2 does not seem to be able to sustain a thread connection to the OmniProII. It goes from "Wait for Connect" to "Wait for Comm Resource" 

Also, it seems to fail on reading one of the OmniProII Zones i.e. "PatioMot"

Any assistance on how to troubleshoot would be appreciated.


here is the verbose log:

12/24 10:28:21-MM-MediaCentre, CQCServer, CQCDrv_OPII_Dv2Thread6
{
    HAIOmniTCP2S, HAIOmniTCP2S_DriverImpl.cpp.672, Status/App Status
    Connecting to Omni at address '10.0.0.9:4369'
}
12/24 10:28:21-MM-MediaCentre, CQCServer, CQCDrv_OPII_Dv2Thread6
{
    HAIOmniTCP2S, HAIOmniTCP2S_DriverImpl3.cpp.50, Status/App Status
    Attempting to create session
}
12/24 10:28:21-MM-MediaCentre, CQCServer, CQCDrv_OPII_Dv2Thread6
{
    HAIOmniTCP2S, HAIOmniTCP2S_DriverImpl3.cpp.70, Status/App Status
    Requesting new session
}
12/24 10:28:21-MM-MediaCentre, CQCServer, CQCDrv_OPII_Dv2Thread6
{
    HAIOmniTCP2S, HAIOmniTCP2S_DriverImpl3.cpp.144, Status/App Status
    Attempting to start encrypted session
}
12/24 10:28:21-MM-MediaCentre, CQCServer, CQCDrv_OPII_Dv2Thread6
{
    HAIOmniTCP2S, HAIOmniTCP2S_DriverImpl3.cpp.188, Status/App Status
    Session was established
}
12/24 10:28:21-MM-MediaCentre, CQCServer, CQCDrv_OPII_Dv2Thread6
{
    CQCKit, CQCDriver_DriverBase.cpp.6046, Failed/Initialization Failed, Error: 2003/0/0
    Field 'MOT#_PatioMot' could not be initialized. Driver='OPII_Dv2'
    Field names must start with a character and contain only characters, numbers, hyphen or underscore
      <CQCServer> CQCDriver_DriverBase.cpp - 6219

}
12/24 10:28:21-MM-MediaCentre, CQCServer, CQCDrv_OPII_Dv2Thread6
{
    CQCKit, CQCDriver_DriverBase.cpp.7284, Status/Lost Connection
    Driver 'OPII_Dv2' has lost its communcations resource
}
12/24 10:28:26-MM-MediaCentre, CQCServer, CQCDrv_OPII_Dv2Thread6
{
    CQCKit, CQCDriver_DriverBase.cpp.3445, Status/App Status
    Driver 'OPII_Dv2' is trying to get its comm resource
}
12/24 10:28:26-MM-MediaCentre, CQCServer, CQCDrv_OPII_Dv2Thread6
{
    CQCKit, CQCDriver_DriverBase.cpp.3484, Status/App Status
    Driver 'OPII_Dv2' has its comm resource
}
12/24 10:28:26-MM-MediaCent
Reply
#2
It looks like that zone is named _PatioMot maybe? The driver is trying to use the names in the Omni, and it attempts to adjust those names to meet CQC's field name requirements, but maybe it's not catching that one of something starting with a leaning underscore? Check it and see if that's the case. If so, get rid of the underscore. If not, let me know and we can dig deeper.
Dean Roddey
Explorans limites defectum
Reply
#3
Now that the driver has gotten the names, it's not going to go back to the Omni again to get them, so you'll need to change the name on the CQC side. Right click on the driver in the browser and select the Client Interface. Find that zone and see if it starts with an underscore. If so, edit it and get rid of that and save those changes and see if that makes it happy.
Dean Roddey
Explorans limites defectum
Reply
#4
Hi Dean,

I have removed the PatMot field in the Omni and reloaded the driver in CQS. There are no entries in "Driver Client" / "Client Interface"

It still seems as if the driver is in "Wait for Comm Resource" mode mostly.

Also, the "_PatMot" warning message has disappeared but now I get: "Could not bind any listening interfaces on %(1)"

Any idea what this be?

thanks
Marius
Reply
#5
I'm guessing that the binding error isn't from the Omni driver? Can you post an example of that one? The most common reason for that is that you installed our web server but there's something else talking port 80 on that machine. If so, you would either have to find that other thing and stop it, or re-run the installer and set our web server to another port.

On the Omni not being able to get its comm resource, can you post some log entries of it trying to connect now so that we can see what is going on?
Dean Roddey
Explorans limites defectum
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  TTS II Driver requirements znelbok 1 227 05-20-2019, 09:34 PM
Last Post: Dean Roddey
  CQC to PowerView Hub via Serial Driver Deane Johnson 18 3,520 05-14-2018, 01:11 PM
Last Post: Deane Johnson
  HAI Driver Issue avtexan 6 2,180 04-06-2018, 02:06 PM
Last Post: Dean Roddey
  Monoprice 8x8 HDMI matrix Driver NightLight 13 6,125 09-04-2017, 09:45 AM
Last Post: Dean Roddey
  ELK V2 Driver - AreaArm field & Triggers? sic0048 4 2,281 08-19-2017, 04:46 PM
Last Post: Dean Roddey
  UPB Driver Issue tcmcgec 6 3,695 01-27-2017, 07:18 PM
Last Post: Dean Roddey
  Onkyo NR646 and Universal Integra Driver? Sendero 6 3,426 10-31-2016, 11:22 PM
Last Post: Sendero
  Train HTTP Trigger Driver jkmonroe 24 10,053 10-25-2016, 11:55 AM
Last Post: karenlee
  ISY driver repeatedly losing connection Sendero 14 5,560 09-28-2016, 07:44 PM
Last Post: Dean Roddey
  EventGhost alternatives to getting driver/field *TO* SmartPhone? IVB 37 9,578 08-13-2016, 07:32 PM
Last Post: IVB

Forum Jump:


Users browsing this thread: 1 Guest(s)