Charmed Quark Systems, Ltd. - Support Forums and Community
RCS V2 Driver - Printable Version

+- Charmed Quark Systems, Ltd. - Support Forums and Community (http://www.charmedquark.com/vb_forum)
+-- Forum: General Discussion (http://www.charmedquark.com/vb_forum/forumdisplay.php?fid=3)
+--- Forum: CQC Support (http://www.charmedquark.com/vb_forum/forumdisplay.php?fid=9)
+--- Thread: RCS V2 Driver (/showthread.php?tid=10611)



RCS V2 Driver - kblagron - 06-06-2018

Dean,

You had mentioned on a previous post about being interested in my inability to connect using the RCS V2 driver.  I have posted the logs in high verbosity, but not sure if it is going to tell you much.  The driver connects, but no RCS data is populated to it, and then it will lose connection after a few minutes, then reconnect with the same results.

I am using V 1.9 driver from Kirk Kanak, and it works fine.  I did make one slight change to that driver because it was giving 5-6 bad messages per minute when I initially used it.  Maybe that is the problem.   I am comfortable using the other driver, so there is no need to do anything based on my input.

I have two RCS units, and two serial drivers installed:

RCS ZCV4 - Version V01.06.02  - Controls two zones with damper, although able to control 4, if needed
RCS  TR80 - (No Version Shown) - Controls one zone

Code:
06/07 00:50:33-CQCSERVER, CQCServer, CIDOrbSrvWorkThread_1
{
   CQCServer, CQCServer_DriverCtrl.cpp.202, Status/App Status
   A request to resume driver HVACTest was received, starting operation
}
06/07 00:50:34-CQCSERVER, CQCServer, CQCDrv_HVACTestThread8860
{
   CQCKit, CQCDriver_DriverBase.cpp.3298, Status/App Status
   Driver 'HVACTest' is beginning initialization
}
06/07 00:50:34-CQCSERVER, CQCServer, CQCDrv_HVACTestThread8860
{
   CQCGenDrvS, MEng.System.CQC.Drivers.RCS.SerialRS485V2.DriverImpl.849, Status/App Status
   Could not parse the source names prompt value
}
06/07 00:50:34-CQCSERVER, CQCServer, CQCDrv_HVACTestThread8860
{
   CQCKit, CQCDriver_DriverBase.cpp.3445, Status/App Status
   Driver 'HVACTest' is trying to get its comm resource
}
06/07 00:50:34-CQCSERVER, CQCServer, CQCDrv_HVACTestThread8860
{
   CQCKit, CQCDriver_DriverBase.cpp.3484, Status/App Status
   Driver 'HVACTest' has its comm resource
}
06/07 00:50:34-CQCSERVER, CQCServer, CQCDrv_HVACTestThread8860
{
   CQCKit, CQCDriver_DriverBase.cpp.3502, Status/App Status
   Driver 'HVACTest' is trying to connect to its device
}
06/07 00:50:40-CQCSERVER, CQCServer, CQCDrv_HVACTestThread8860
{
   CQCKit, CQCDriver_DriverBase.cpp.3544, Status/App Status
   Driver 'HVACTest' has connected to its device
}
06/07 00:51:45-CQCSERVER, CQCServer, CIDOrbSrvWorkThread_3
{
   CQCServer, CQCServer_DriverCtrl.cpp.202, Status/App Status
   A request to pause driver HVAC2 was received, starting operation
}
06/07 00:52:26-CQCSERVER, CQCServer, CQCDrv_HVACTestThread8860
{
   CQCKit, CQCDriver_DriverBase.cpp.7255, Status/Lost Connection
   Driver 'HVACTest' has lost connection to it's device
}
06/07 00:52:29-CQCSERVER, CQCServer, CQCDrv_HVACTestThread8860
{
   CQCKit, CQCDriver_DriverBase.cpp.3502, Status/App Status
   Driver 'HVACTest' is trying to connect to its device
}
06/07 00:52:35-CQCSERVER, CQCServer, CQCDrv_HVACTestThread8860
{
   CQCKit, CQCDriver_DriverBase.cpp.3544, Status/App Status
   Driver 'HVACTest' has connected to its device
}
06/07 00:52:49-CQCSERVER, CQCServer, CIDOrbSrvWorkThread_4
{
   CQCServer, CQCServer_DriverCtrl.cpp.147, Status/App Status
   Remote client forcing load of driver. Moniker=HVACTest2. M/M/V=RCS/TR16/TR40-V2/1.0
}
06/07 00:52:49-CQCSERVER, CQCServer, CQCDrv_HVACTest2Thread8866
{
   CQCGenDrvS, MEng.System.CQC.Drivers.RCS.SerialRS485V2.DriverImpl.849, Status/App Status
   Could not parse the source names prompt value
}
06/07 00:53:40-CQCSERVER, CQCServer, CQCDrv_HVACTestThread8860
{
   CQCKit, CQCDriver_DriverBase.cpp.7255, Status/Lost Connection
   Driver 'HVACTest' has lost connection to it's device
}
06/07 00:53:43-CQCSERVER, CQCServer, CQCDrv_HVACTestThread8860
{
   CQCKit, CQCDriver_DriverBase.cpp.3502, Status/App Status
   Driver 'HVACTest' is trying to connect to its device
}
06/07 00:53:49-CQCSERVER, CQCServer, CQCDrv_HVACTestThread8860
{
   CQCKit, CQCDriver_DriverBase.cpp.3544, Status/App Status
   Driver 'HVACTest' has connected to its device
}
06/07 00:54:43-CQCSERVER, CQCServer, CQCDrv_HVACTest2Thread8866
{
   CQCKit, CQCDriver_DriverBase.cpp.7255, Status/Lost Connection
   Driver 'HVACTest2' has lost connection to it's device
}
06/07 00:54:46-CQCSERVER, CQCServer, CQCDrv_HVACTest2Thread8866
{
   CQCKit, CQCDriver_DriverBase.cpp.3502, Status/App Status
   Driver 'HVACTest2' is trying to connect to its device
}
06/07 00:54:51-CQCSERVER, CQCServer, CQCDrv_HVACTest2Thread8866
{
   CQCKit, CQCDriver_DriverBase.cpp.3544, Status/App Status
   Driver 'HVACTest2' has connected to its device
}
06/07 00:55:15-CQCSERVER, CQCServer, CIDOrbSrvWorkThread_3
{
   CQCKit, CQCDriver_DriverBase.cpp.1443, Failed/Not Ready, Error: 906/0/0
   Driver 'HVAC1' is not currently connected to its device
     <CQCServer> CIDOrb_ThisFacility.cpp - 536
     <CQCServer> CQCKit_CQCSrvAdminClientProxy.cpp - 586

}
06/07 00:55:19-CQCSERVER, CQCServer, CQCDrv_HVACTest2Thread8866
{
   CQCKit, CQCDriver_DriverBase.cpp.7255, Status/Lost Connection
   Driver 'HVACTest2' has lost connection to it's device
}
06/07 00:55:22-CQCSERVER, CQCServer, CQCDrv_HVACTest2Thread8866
{
   CQCKit, CQCDriver_DriverBase.cpp.3502, Status/App Status
   Driver 'HVACTest2' is trying to connect to its device
}
06/07 00:55:27-CQCSERVER, CQCServer, CQCDrv_HVACTest2Thread8866
{
   CQCKit, CQCDriver_DriverBase.cpp.3544, Status/App Status
   Driver 'HVACTest2' has connected to its device
}



RE: RCS V2 Driver - Dean Roddey - 06-07-2018

It looks like it's not happy with something in the manifest. That's something I can test without having to connect to yours probably, so let me take a look at that.


RE: RCS V2 Driver - Dean Roddey - 06-10-2018

OK, this should be happy in 5.2.918.