Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Unable to connect to VRC0P
#1
I replaced a defective dimmer switch today, excluding the old one and including a new one. In the process, the Installer Tool started running by itself and messed up the network. I got everything re-included and than updated the VRC0P which indicated success in the Installer Tool app.

Now the CQC driver won't connect to the VRC0P. In trying different things, I noted that I had been using V1. I updated to driver V2, but I still get "wait to connect".

I've gone through it multiple times and can't find the reason.
Reply
#2
You won't want to use the V2 driver, not yet. If you were on the old V1 driver stay there for now. The V2 one has a much different setup and that would introduce too much difference, best to get it working again with the old driver.

Once you get back to the V1 driver, and be sure to load the V1 client side driver, do you get to the driver's configuration interface?
Dean Roddey
Explorans limites defectum
Reply
#3
No joy with v.1. Yes I get the interface to do the Moniker etc.
Reply
#4
Oh, no I meant can you get to the client side driver interface where you set up the modules? If so, use the Rescan button to make it rescan the Z-Wave network.
Dean Roddey
Explorans limites defectum
Reply
#5
I don't believe so. I remember that scan function, but I don't seem to find it. The Currently Loaded Client Drivers shows the driver.

I think I found the screen. In red it says "This device seems to be offline at this time."
Reply
#6
You have to load the client side driver for the Z-Wave driver. I assume you had done that before in order to configure your Z-Wave units, right? So, unless you unloaded it, it should still be there. Though, if the driver won't come online, in the V1 driver it might just be showing that the driver is offline. But, if you do have the client side driver interface, you would just press the Rescan button generally to make it happy.

If you aren't able to get to the client side interface, then more drastic action will have to be taken.

The V2 driver is much better in this regard, but it also requires that you have 'device info' files for each module type you have, and it also only supports modules that report their status automatically, so you might have trouble using it immediately.
Dean Roddey
Explorans limites defectum
Reply
#7
Also, if you can get me some log output, that would help probably. If you can put the driver into verbose logging, bring up the log monitor and hit the clear button, then let the driver run for a minute, right click in the log output window and copy the text, and paste it here, then take the driver back out of verbose mode.
Dean Roddey
Explorans limites defectum
Reply
#8
11/30 17:40:49-Asus, CQCServer, CQCDrv_VRC0P-V1Thread24
{
ZWaveLeviS, ZWaveLeviS_DriverImpl3.cpp.329, Failed/Timeout, Error: 1002/0/0
Timed out waiting for message
<CQCServer> ZWaveLeviS_DriverImpl3.cpp - 209
<CQCServer> ZWaveLeviS_DriverImpl.cpp - 1018

}

11/30 17:41:04-Asus, CQCServer, CQCDrv_VRC0P-V1Thread24
{
CQCKit, CQCDriver_DriverBase.cpp.3562, Status/App Status
Driver 'VRC0P-V1' is trying to connect to its device
}

11/30 17:41:04-Asus, CQCServer, CQCDrv_VRC0P-V1Thread24
{
CQCKit, ZWaveLeviS_DriverImpl.cpp.519, Status/App Status
(Driver=VRC0P-V1) - Trying to connect to Z-Wave controller
}

11/30 17:41:09-Asus, CQCServer, CQCDrv_VRC0P-V1Thread24
{
ZWaveLeviS, ZWaveLeviS_DriverImpl3.cpp.329, Failed/Timeout, Error: 1002/0/0
Timed out waiting for message
<CQCServer> ZWaveLeviS_DriverImpl3.cpp - 209
<CQCServer> ZWaveLeviS_DriverImpl.cpp - 1018

}

11/30 17:41:24-Asus, CQCServer, CQCDrv_VRC0P-V1Thread24
{
CQCKit, CQCDriver_DriverBase.cpp.3562, Status/App Status
Driver 'VRC0P-V1' is trying to connect to its device
}

11/30 17:41:24-Asus, CQCServer, CQCDrv_VRC0P-V1Thread24
{
CQCKit, ZWaveLeviS_DriverImpl.cpp.519, Status/App Status
(Driver=VRC0P-V1) - Trying to connect to Z-Wave controller
}

11/30 17:41:29-Asus, CQCServer, CQCDrv_VRC0P-V1Thread24
{
ZWaveLeviS, ZWaveLeviS_DriverImpl3.cpp.329, Failed/Timeout, Error: 1002/0/0
Timed out waiting for message
<CQCServer> ZWaveLeviS_DriverImpl3.cpp - 209
<CQCServer> ZWaveLeviS_DriverImpl.cpp - 1018

}

11/30 17:41:44-Asus, CQCServer, CQCDrv_VRC0P-V1Thread24
{
CQCKit, CQCDriver_DriverBase.cpp.3562, Status/App Status
Driver 'VRC0P-V1' is trying to connect to its device
}

11/30 17:41:44-Asus, CQCServer, CQCDrv_VRC0P-V1Thread24
{
CQCKit, ZWaveLeviS_DriverImpl.cpp.519, Status/App Status
(Driver=VRC0P-V1) - Trying to connect to Z-Wave controller
}

11/30 17:41:49-Asus, CQCServer, CQCDrv_VRC0P-V1Thread24
{
ZWaveLeviS, ZWaveLeviS_DriverImpl3.cpp.329, Failed/Timeout, Error: 1002/0/0
Timed out waiting for message
<CQCServer> ZWaveLeviS_DriverImpl3.cpp - 209
<CQCServer> ZWaveLeviS_DriverImpl.cpp - 1018

}

11/30 17:42:04-Asus, CQCServer, CQCDrv_VRC0P-V1Thread24
{
CQCKit, CQCDriver_DriverBase.cpp.3562, Status/App Status
Driver 'VRC0P-V1' is trying to connect to its device
}

11/30 17:42:04-Asus, CQCServer, CQCDrv_VRC0P-V1Thread24
{
CQCKit, ZWaveLeviS_DriverImpl.cpp.519, Status/App Status
(Driver=VRC0P-V1) - Trying to connect to Z-Wave controller
}

11/30 17:42:09-Asus, CQCServer, CQCDrv_VRC0P-V1Thread24
{
ZWaveLeviS, ZWaveLeviS_DriverImpl3.cpp.329, Failed/Timeout, Error: 1002/0/0
Timed out waiting for message
<CQCServer> ZWaveLeviS_DriverImpl3.cpp - 209
<CQCServer> ZWaveLeviS_DriverImpl.cpp - 1018

}

11/30 17:42:24-Asus, CQCServer, CQCDrv_VRC0P-V1Thread24
{
CQCKit, CQCDriver_DriverBase.cpp.3562, Status/App Status
Driver 'VRC0P-V1' is trying to connect to its device
}

11/30 17:42:24-Asus, CQCServer, CQCDrv_VRC0P-V1Thread24
{
CQCKit, ZWaveLeviS_DriverImpl.cpp.519, Status/App Status
(Driver=VRC0P-V1) - Trying to connect to Z-Wave controller
}

11/30 17:42:29-Asus, CQCServer, CQCDrv_VRC0P-V1Thread24
{
ZWaveLeviS, ZWaveLeviS_DriverImpl3.cpp.329, Failed/Timeout, Error: 1002/0/0
Timed out waiting for message
<CQCServer> ZWaveLeviS_DriverImpl3.cpp - 209
<CQCServer> ZWaveLeviS_DriverImpl.cpp - 1018

}

11/30 17:42:44-Asus, CQCServer, CQCDrv_VRC0P-V1Thread24
{
CQCKit, CQCDriver_DriverBase.cpp.3562, Status/App Status
Driver 'VRC0P-V1' is trying to connect to its device
}

11/30 17:42:44-Asus, CQCServer, CQCDrv_VRC0P-V1Thread24
{
CQCKit, ZWaveLeviS_DriverImpl.cpp.519, Status/App Status
(Driver=VRC0P-V1) - Trying to connect to Z-Wave controller
}

11/30 17:42:49-Asus, CQCServer, CQCDrv_VRC0P-V1Thread24
{
ZWaveLeviS, ZWaveLeviS_DriverImpl3.cpp.329, Failed/Timeout, Error: 1002/0/0
Timed out waiting for message
<CQCServer> ZWaveLeviS_DriverImpl3.cpp - 209
<CQCServer> ZWaveLeviS_DriverImpl.cpp - 1018

}

11/30 17:43:04-Asus, CQCServer, CQCDrv_VRC0P-V1Thread24
{
CQCKit, CQCDriver_DriverBase.cpp.3562, Status/App Status
Driver 'VRC0P-V1' is trying to connect to its device
}

11/30 17:43:04-Asus, CQCServer, CQCDrv_VRC0P-V1Thread24
{
CQCKit, ZWaveLeviS_DriverImpl.cpp.519, Status/App Status
(Driver=VRC0P-V1) - Trying to connect to Z-Wave controller
}

11/30 17:43:09-Asus, CQCServer, CQCDrv_VRC0P-V1Thread24
{
ZWaveLeviS, ZWaveLeviS_DriverImpl3.cpp.329, Failed/Timeout, Error: 1002/0/0
Timed out waiting for message
<CQCServer> ZWaveLeviS_DriverImpl3.cpp - 209
<CQCServer> ZWaveLeviS_DriverImpl.cpp - 1018

}
Reply
#9
That doesn't really appear to be anything to do with your having changed the configuration or anything. The VRCOP just isn't responding. Just to make sure you haven't whacked it somehow, go unplug it for a minute then plug it back in. If the driver comes back on line, and I'm guessing it might, then somehow you freaked out the VRCOP. If it still doesn't, have the Leviton software reinitialize the VRCOP as well after you plug it back in
Dean Roddey
Explorans limites defectum
Reply
#10
That seem to have done it. It came up connected. I have the "Rescan" screen.
Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  Extron 200 and now Crosspoint 300 no connect AceCannon 1 1,557 07-14-2017, 10:49 AM
Last Post: Dean Roddey
  New VRC0P 3 appears to be working Deane Johnson 8 3,949 11-11-2014, 02:54 PM
Last Post: Deane Johnson
  System crashed, unable to get it going again. Deane Johnson 43 12,709 11-11-2014, 04:50 AM
Last Post: Mark Stega
  Determined to finally get Z-Wave VRC0P Working Hiller 121 30,403 08-05-2014, 05:15 PM
Last Post: jkmonroe
  Elk Driver Waiting to Connect in 3.02 electriclight 8 2,758 07-23-2009, 08:59 AM
Last Post: electriclight
  Client Unable to Connect to the Master Server MavRic 9 3,077 06-13-2009, 03:41 PM
Last Post: MavRic
  Elk driver not connect Trioxide 4 2,229 06-13-2009, 10:06 AM
Last Post: Trioxide
  Serial connect Denon 3805 EST 15 5,129 04-29-2009, 05:33 AM
Last Post: wuench
  Using Domain - now computer won't connect sic0048 17 5,170 03-17-2009, 01:11 PM
Last Post: sic0048
  Unable to connect CQC to C-Bus trouble 9 2,916 01-02-2009, 01:30 PM
Last Post: znelbok

Forum Jump:


Users browsing this thread: 1 Guest(s)