Charmed Quark Systems, Ltd. - Support Forums and Community
C-Bus V5.1 driver for CQC V3 - Printable Version

+- Charmed Quark Systems, Ltd. - Support Forums and Community (https://www.charmedquark.com/vb_forums)
+-- Forum: Third Party Development (https://www.charmedquark.com/vb_forums/forumdisplay.php?fid=8)
+--- Forum: Third Party Development (General) (https://www.charmedquark.com/vb_forums/forumdisplay.php?fid=22)
+--- Thread: C-Bus V5.1 driver for CQC V3 (/showthread.php?tid=5966)

Pages: 1 2 3


C-Bus V5.1 driver for CQC V3 - trouble - 01-17-2010

Rohan

Thanks, will keep my fingers crossed.


Paul


C-Bus V5.1 driver for CQC V3 - trouble - 03-11-2010

Hi Rohan

Have you had a chance to look at updating the driver to supports extended status? I went down the CQC path to control our c-bus enabled house, and keep having an issue that what CQC thinks, and what C-Bus thinks are different. I have rules that at sunset, CQC closes the blinds and windows (which are using c-bus window/blind relay modules), but sometimes (ie at least once per week), at least 1 of the windows or blinds will not close, and thats becuse CQC has the status as closed, while really its open.
Also i find that if i open a blind using a DLT switch and then half way while its opening, i press the DLT switch again to stop it half way, CQC thinks the blind has opened all the way. The only time it gets the open value correct is if i use CQC to open it and stop it half way.

Thanks
Paul


C-Bus V5.1 driver for CQC V3 - znelbok - 03-24-2011

Just loaded this again today and it threw an error. I know whay it produced an error, there were bad characters in the translate file, but this appears to be a different issue with the $BadMsg field being marked as a boolean isntead of a Card4

Code:
}

03/25 09:46:10-RACKSERVER, CQCServer, CQCDrv_Lighting_Thread11
{
    CQCKit, CQCKit_DriverBase.cpp.5063, Failed/Type Match, Error: 2015/0/0
    Field 'Lighting.$BadMsg' was accessed as a MEng.Boolean type, but it's type is MEng.Card4
}

03/25 09:46:10-RACKSERVER, CQCServer, CQCDrv_Lighting_Thread11
{
    CQCKit, CQCKit_MEngErrHandler.cpp.69, Status/App Status
    A C++ exception occured during macro execution
}

03/25 09:46:10-RACKSERVER, CQCServer, CQCDrv_Lighting_Thread11
{
    CQCKit, CQCKit_DriverBase.cpp.5063, Failed/Type Match, Error: 2015/0/0
    Field 'Lighting.$BadMsg' was accessed as a MEng.Boolean type, but it's type is MEng.Card4
}

CQC V3.4.13
C-Bus 5.0 (as released with CQC)

Mick


C-Bus V5.1 driver for CQC V3 - Dean Roddey - 03-24-2011

Oh well, it won't happen unless there's a failed message in which case it's not going to matter if this happens since the driver i is already probably going to scram in that case. So I guess it's something that's livable given that we don't have the source for the driver.


C-Bus V5.1 driver for CQC V3 - rhamer - 03-24-2011

What, a problem after all this time? Confusedhock:

What is the issue?

Rohan


C-Bus V5.1 driver for CQC V3 - Dean Roddey - 03-24-2011

That particular error generally occurs when one of the field id members doesn't get set. The driver then accesses what it thinks is the right field id, but the id has just been left at zero since it was never set. The real 0 field id is always the $BadMsg field. If the type of the field the driver thinks it's accessing is different, then you'll get that kind of error.


C-Bus V5.1 driver for CQC V3 - znelbok - 03-20-2013

This driver has not been added to the default list of drivers deployed with CQC.

Can we have it added in please?

SOme more development of it would be great as well (Rohan please). If not can we have someone else who is willing to take over the role of development (its an encrypted driver so Rohan will have to of course give his blessing to it first).

Mick


C-Bus V5.1 driver for CQC V3 - znelbok - 03-22-2013

Started noticing that the driver was dropping offline every so often so I set it to high logging and found that there are bad messages going out to the bus.

Not sure why or what is causing this.

Code:
{
    CQCKit, MEng.System.CQC.Runtime.CQCLogger.1395, Status/App Status
    C-Bus - ProcessMsg Entering with AAB3
}
03/23 12:41:04-Zeus01, CQCServer, CQCDrv_lightingThread20
{
    CQCKit, MEng.System.CQC.Runtime.CQCLogger.810, Status/App Status
    C-Bus - CheckMsgType Checking the message type for AAB3
}
03/23 12:41:04-Zeus01, CQCServer, CQCDrv_lightingThread20
{
    CQCKit, MEng.System.CQC.Runtime.CQCLogger.814, Status/App Status
    C-Bus - CheckMsgType Got a badly formed message = AAB3
}
03/23 12:41:04-Zeus01, CQCServer, CQCDrv_lightingThread20
{
    CQCKit, MEng.System.CQC.Runtime.CQCLogger.1670, Status/App Status
    C-Bus - ProcessMsg Message Unknown AAB3
}
03/23 12:41:04-Zeus01, CQCServer, CQCDrv_lightingThread20
{
    CQCKit, MEng.System.CQC.Runtime.CQCLogger.1680, Status/App Status
    C-Bus - ProcessMsg Exiting
}
03/23 12:41:04-Zeus01, CQCServer, CQCDrv_lightingThread20
{
    CQCKit, MEng.System.CQC.Runtime.CQCLogger.1395, Status/App Status
    C-Bus - ProcessMsg Entering with D83858AAAAAAAA6A000000000000000000000000000000000086
}
03/23 12:41:04-Zeus01, CQCServer, CQCDrv_lightingThread20
{
    CQCKit, MEng.System.CQC.Runtime.CQCLogger.810, Status/App Status
    C-Bus - CheckMsgType Checking the message type for D83858AAAAAAAA6A000000000000000000000000000000000086
}
03/23 12:41:04-Zeus01, CQCServer, CQCDrv_lightingThread20
{
    CQCKit, MEng.System.CQC.Runtime.CQCLogger.834, Status/App Status
    C-Bus - CheckMsgType Got an MMI = D83858AAAAAAAA6A000000000000000000000000000000000086
}
03/23 12:41:04-Zeus01, CQCServer, CQCDrv_lightingThread20
{
    CQCKit, MEng.System.CQC.Runtime.CQCLogger.991, Status/App Status
    C-Bus - ProcessMMI Entering with D83858AAAAAAAA6A000000000000000000000000000000000086
}
03/23 12:41:04-Zeus01, CQCServer, CQCDrv_lightingThread20
{

The only thing that changed was about a month ago I moved to server 2008, but the PCI is connected to a Digi Etherlite and the old server and new server are both setup exactly the same in the way it communicates with the PCI.

The above error crops up quote a few times - the message being different but always short and not long like the next one shown in the example above.

Mick


C-Bus V5.1 driver for CQC V3 - rhamer - 03-23-2013

Try running the C-Bus diagnostic utility (the current one is the best) at the same time and it will show you the generating unit, and the full message.

I'm not surprised it breaks when it gets messages it doesn't understand, the documentation that was available at the time it was written didn't mention a lot of messages that I now know exist.

Cheers

Rohan


C-Bus V5.1 driver for CQC V3 - znelbok - 03-23-2013

There appears to be no bad values on the network. The driver looks like it is not getting the full MMI comming back. The values hown are the tail end of the message.

This changes in length and is not a pettern [so far].

Mick