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
  RCS V2 Driver kblagron 2 64 06-10-2018, 04:35 PM
Last Post: Dean Roddey
  New Z-Wave driver preview Dean Roddey 13 1,032 05-17-2018, 01:02 PM
Last Post: Dean Roddey
  Sonos Driver with Sonos Connect Amp zra 5 277 05-05-2018, 09:43 AM
Last Post: Dean Roddey
  Radio RA driver issue dogman 7 382 04-22-2018, 08:33 AM
Last Post: Dean Roddey
  Elk Driver fails Ron Haley 11 704 03-08-2018, 07:28 PM
Last Post: Ron Haley
  Nest driver disconnecting and reconnecting dogman 59 5,373 03-08-2018, 05:23 PM
Last Post: dogman
  Aeotec USB stick, existing zWave (v3) driver? IVB 3 314 03-05-2018, 08:57 PM
Last Post: znelbok
  Problem with Jetstream Driver RichardU 16 1,075 02-27-2018, 03:05 PM
Last Post: batwater
  Problem with fooBarV2 driver pjgregory 2 367 02-21-2018, 01:01 PM
Last Post: Dean Roddey
  Does GC-100 Driver Support Tri-Port Cable? Jnetto 18 1,740 01-29-2018, 08:16 AM
Last Post: RichardU

Forum Jump:


Users browsing this thread: 1 Guest(s)