Charmed Quark Systems, Ltd. - Support Forums and Community
Kramer Protocol 2000 driver and VS-1616v Help Please! - 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: Kramer Protocol 2000 driver and VS-1616v Help Please! (/showthread.php?tid=10384)



Kramer Protocol 2000 driver and VS-1616v Help Please! - NightLight - 09-12-2017

I'm trying to get an old analogue video matrix working. It's a Kramer VS-1616v. I am having no luck getting it to connect with the Protocol 2000 driver. I've tried multiple cables and checked port settings. Not sure what I am missing. 

Linked to the manual. RS-232 spec on the second last page. 

http://k.kramerav.com/downloads/manuals/vs-1616v.pdf  

Thoughts?


RE: Kramer Protocol 200 driver and VS-1616v Help Please! - NightLight - 09-12-2017

Code:
09/12 00:58:13-CORE, CQCServer, CQCDrv_kThread49
{
   CQCGenDrvS, MEng.System.CQC.Drivers.Kramer.Protocol_2k.DriverImpl.898, Status/App Status
   <Connect> [DISCONNECT] Proper reply not received.
}
09/12 00:58:15-CORE, CQCServer, CQCDrv_kThread49
{
   CQCKit, CQCDriver_DriverBase.cpp.3502, Status/App Status
   Driver 'k' is trying to connect to its device
}
09/12 00:58:15-CORE, CQCServer, CQCDrv_kThread49
{
   CQCGenDrvS, MEng.System.CQC.Drivers.Kramer.Protocol_2k.DriverImpl.875, Status/App Status
   <Connect> Entering Connect function, Version 1.0
}
09/12 00:58:15-CORE, CQCServer, CQCDrv_kThread49
{
   CQCGenDrvS, MEng.System.CQC.Drivers.Kramer.Protocol_2k.DriverImpl.232, Status/App Status
   <Send> Msg sent: 1011 10000000 10000000 10000001
}
09/12 00:58:15-CORE, CQCServer, CQCDrv_kThread49
{
   CQCGenDrvS, MEng.System.CQC.Drivers.Kramer.Protocol_2k.DriverImpl.472, Status/App Status
   <GetMessage>: Entering function
}
09/12 00:58:17-CORE, CQCServer, CQCDrv_kThread49
{
   CQCGenDrvS, MEng.System.CQC.Drivers.Kramer.Protocol_2k.DriverImpl.898, Status/App Status
   <Connect> [DISCONNECT] Proper reply not received.
}
09/12 00:58:19-CORE, CQCServer, CQCDrv_kThread49
{
   CQCKit, CQCDriver_DriverBase.cpp.3502, Status/App Status
   Driver 'k' is trying to connect to its device
}
09/12 00:58:19-CORE, CQCServer, CQCDrv_kThread49
{
   CQCGenDrvS, MEng.System.CQC.Drivers.Kramer.Protocol_2k.DriverImpl.875, Status/App Status
   <Connect> Entering Connect function, Version 1.0
}
09/12 00:58:19-CORE, CQCServer, CQCDrv_kThread49
{
   CQCGenDrvS, MEng.System.CQC.Drivers.Kramer.Protocol_2k.DriverImpl.232, Status/App Status
   <Send> Msg sent: 1011 10000000 10000000 10000001
}
09/12 00:58:19-CORE, CQCServer, CQCDrv_kThread49
{
   CQCGenDrvS, MEng.System.CQC.Drivers.Kramer.Protocol_2k.DriverImpl.472, Status/App Status
   <GetMessage>: Entering function
}
09/12 00:58:21-CORE, CQCServer, CQCDrv_kThread49
{
   CQCGenDrvS, MEng.System.CQC.Drivers.Kramer.Protocol_2k.DriverImpl.898, Status/App Status
   <Connect> [DISCONNECT] Proper reply not received.
}
09/12 00:58:23-CORE, CQCServer, CQCDrv_kThread49
{
   CQCKit, CQCDriver_DriverBase.cpp.3502, Status/App Status
   Driver 'k' is trying to connect to its device
}
09/12 00:58:23-CORE, CQCServer, CQCDrv_kThread49
{
   CQCGenDrvS, MEng.System.CQC.Drivers.Kramer.Protocol_2k.DriverImpl.875, Status/App Status
   <Connect> Entering Connect function, Version 1.0
}
09/12 00:58:23-CORE, CQCServer, CQCDrv_kThread49
{
   CQCGenDrvS, MEng.System.CQC.Drivers.Kramer.Protocol_2k.DriverImpl.232, Status/App Status
   <Send> Msg sent: 1011 10000000 10000000 10000001
}
09/12 00:58:23-CORE, CQCServer, CQCDrv_kThread49
{
   CQCGenDrvS, MEng.System.CQC.Drivers.Kramer.Protocol_2k.DriverImpl.472, Status/App Status
   <GetMessage>: Entering function
}
09/12 00:58:25-CORE, CQCServer, CQCDrv_kThread49
{
   CQCGenDrvS, MEng.System.CQC.Drivers.Kramer.Protocol_2k.DriverImpl.898, Status/App Status
   <Connect> [DISCONNECT] Proper reply not received.
}
09/12 00:58:27-CORE, CQCServer, CQCDrv_kThread49
{
   CQCKit, CQCDriver_DriverBase.cpp.3502, Status/App Status
   Driver 'k' is trying to connect to its device
}
09/12 00:58:27-CORE, CQCServer, CQCDrv_kThread49
{
   CQCGenDrvS, MEng.System.CQC.Drivers.Kramer.Protocol_2k.DriverImpl.875, Status/App Status
   <Connect> Entering Connect function, Version 1.0
}
09/12 00:58:27-CORE, CQCServer, CQCDrv_kThread49
{
   CQCGenDrvS, MEng.System.CQC.Drivers.Kramer.Protocol_2k.DriverImpl.232, Status/App Status
   <Send> Msg sent: 1011 10000000 10000000 10000001
}
09/12 00:58:27-CORE, CQCServer, CQCDrv_kThread49
{
   CQCGenDrvS, MEng.System.CQC.Drivers.Kramer.Protocol_2k.DriverImpl.472, Status/App Status
   <GetMessage>: Entering function
}
09/12 00:58:29-CORE, CQCServer, CQCDrv_kThread49
{
   CQCGenDrvS, MEng.System.CQC.Drivers.Kramer.Protocol_2k.DriverImpl.898, Status/App Status
   <Connect> [DISCONNECT] Proper reply not received.
}
09/12 00:58:31-CORE, CQCServer, CQCDrv_kThread49
{
   CQCKit, CQCDriver_DriverBase.cpp.3502, Status/App Status
   Driver 'k' is trying to connect to its device
}
09/12 00:58:31-CORE, CQCServer, CQCDrv_kThread49
{
   CQCGenDrvS, MEng.System.CQC.Drivers.Kramer.Protocol_2k.DriverImpl.875, Status/App Status
   <Connect> Entering Connect function, Version 1.0
}
09/12 00:58:31-CORE, CQCServer, CQCDrv_kThread49
{
   CQCGenDrvS, MEng.System.CQC.Drivers.Kramer.Protocol_2k.DriverImpl.232, Status/App Status
   <Send> Msg sent: 1011 10000000 10000000 10000001
}
09/12 00:58:31-CORE, CQCServer, CQCDrv_kThread49
{
   CQCGenDrvS, MEng.System.CQC.Drivers.Kramer.Protocol_2k.DriverImpl.472, Status/App Status
   <GetMessage>: Entering function
}



RE: Kramer Protocol 2000 driver and VS-1616v Help Please! - NightLight - 09-12-2017

Update - I was able to make a serial connection using the Kramer k-Router software. Device worked as expected. Now to get CQC connected.. It should work with the Protocol 2000 driver no? 

Thank you!

[Image: rleJkI9.png]


RE: Kramer Protocol 2000 driver and VS-1616v Help Please! - Dean Roddey - 09-12-2017

That protocol described in the manual doesn't bear any relation to the one that the 2K protocol driver uses, so apparently they've changed it yet again. It's a super-simple, one way ASCII protocol, whereas the 2K one was binary.

It's so stupidly simple that doing a PDL driver would be straightforward, other than the command that does multiple I/O connections at once. You'd want to stick to single operations and just do multiples from your actions. Since there appears to be no means to query state, it couldn't be V2 compatible.


RE: Kramer Protocol 2000 driver and VS-1616v Help Please! - znelbok - 09-12-2017

I would not even bother with a driver specifically for it as there is no feedback other than a confirmation of receiving a valid command.

Just use one of the generic pass-through drivers and send the required string

You will probably only use the Y command and that's pretty easy to grasp

**Y3,4!!

I'd say that this unit is older than the 2K protocol


RE: Kramer Protocol 2000 driver and VS-1616v Help Please! - NightLight - 09-12-2017

If I could sell a CQC license to control this thing. Would you write me a driver?


RE: Kramer Protocol 2000 driver and VS-1616v Help Please! - Dean Roddey - 09-12-2017

Sure, it would be easy enough. Is just mapping input to output sufficient?