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
  Nest driver disconnecting and reconnecting dogman 58 1,709 01-17-2018, 12:24 PM
Last Post: Dean Roddey
  SSL certificate for HTTP trigger driver RichardU 7 92 01-16-2018, 09:50 AM
Last Post: Dean Roddey
  Variables Driver jkmonroe 10 141 01-05-2018, 08:29 PM
Last Post: jkmonroe
  Does GC-100 Driver Support Tri-Port Cable? Jnetto 14 389 12-26-2017, 02:06 PM
Last Post: RichardU
  Russound V2 Driver - no install button bpaetzold 1 75 12-24-2017, 07:13 PM
Last Post: Dean Roddey
  Is there a driver out there for the Honeywell Wi-Fi Smart Thermostat? ghurty 18 3,311 12-21-2017, 06:29 PM
Last Post: Dean Roddey
  Logitech Media Server/squeezebox driver freezes Admin interface lleo 7 715 10-21-2017, 11:11 AM
Last Post: Dean Roddey
  music & movie driver experiences and or suggestions zane 2 488 10-18-2017, 06:48 AM
Last Post: pjgregory
  Really simple CML driver questions znelbok 327 55,009 10-11-2017, 09:19 PM
Last Post: znelbok
  Next V2 driver problem kjaerligkatt 9 696 09-05-2017, 01:33 PM
Last Post: kjaerligkatt

Forum Jump:


Users browsing this thread: 1 Guest(s)