Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Kramer Protocol 2000 driver and VS-1616v Help Please!
#1
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?
Reply
#2
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
}
Reply
#3
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]
Reply
#4
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.
Dean Roddey
Software Geek Extraordinaire
Reply
#5
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
Mykel Koblenz
Illawarra Smart Home
Reply
#6
If I could sell a CQC license to control this thing. Would you write me a driver?
Reply
#7
Sure, it would be easy enough. Is just mapping input to output sufficient?
Dean Roddey
Software Geek Extraordinaire
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  Next V2 driver problem kjaerligkatt 9 184 09-05-2017, 01:33 PM
Last Post: kjaerligkatt
  RCS Thermostat Driver help sic0048 10 531 08-19-2017, 08:01 AM
Last Post: Dean Roddey
  Harmony Hub driver tom 43 4,008 08-17-2017, 09:00 AM
Last Post: Dean Roddey
  ISY Driver not able to change value on a specific switch Sendero 9 586 07-18-2017, 09:54 AM
Last Post: Dean Roddey
  If you got a notification from Nest about the CQC driver Dean Roddey 1 258 07-12-2017, 02:44 PM
Last Post: potts.mike
  Variable Driver Trigger Error zra 4 371 07-06-2017, 01:00 PM
Last Post: zra
  Marantz V2 Driver Feature Request zra 21 1,017 07-06-2017, 10:02 AM
Last Post: Dean Roddey
  Nest V2 driver potts.mike 16 1,009 06-23-2017, 08:48 AM
Last Post: potts.mike
  Really simple CML driver questions znelbok 322 36,076 06-18-2017, 01:12 PM
Last Post: Dean Roddey
  C-Bus driver loading error znelbok 4 343 06-16-2017, 01:12 AM
Last Post: znelbok

Forum Jump:


Users browsing this thread: 1 Guest(s)