PAC connection problem

Discussion in 'C-Bus Wired Hardware' started by WernerUK, Mar 3, 2008.

  1. WernerUK

    WernerUK

    Joined:
    Mar 1, 2008
    Messages:
    1
    Likes Received:
    0
    Location:
    UK
    Hi

    This is my first post here, so please be gentle :)

    My Clipsal system has been installed for about six months and I do like it very much. It is a test install based in a single room, and the idea is to turn it into a full house installation as part of our extension work. At the moment I have a 6 button Saturn wall panel connected to an 8 channel dimmer and a PAC which is used as the programming interface to the c-bus as well as an RS232 interface to a Pronto TSU9600.

    I finally got round to programming the PAC last week to allow the Pronto to control scenes, and it occurred to me that I should move all the scenes from the wall panel to the PAC. I had some problems with the behaviour of the c-bus toolkit, so I went on to the forum for some inspiration.

    I found out that there was a new version of the toolkit (1.8.0) so I downloaded it and installed it on top of 1.7.4 which I had used so far.

    Ever since I upgraded the toolkit version I'm unable to connect to my PAC over the USB cable. The error message is 'Failed Identify'. (See pictures)

    I tried the following:

    Un-installing the USB driver
    Un-installing version 1.8.0 and reinstalling version 1.7.4
    Changing the COM assignment of the USB port to the PAC

    I'm using my Toshiba notebook (Satellite) and Vista Home Premium.
    The installed firmware on the PAC came with PICED 4.3.0 (PACA_3_13_0.mot).

    I would be grateful for any ideas/help, since I'm currently completely locked out from by C-Bus.

    Regards,

    Werner
     

    Attached Files:

    WernerUK, Mar 3, 2008
    #1
  2. WernerUK

    emillika

    Joined:
    Jan 28, 2007
    Messages:
    41
    Likes Received:
    0
    Did you get this figured out? I also recently upgraded my toolkit version and seemed to lose the PAC driver setup on my pc. So I just reinstalled the driver and all seems well now.
     
    emillika, Apr 1, 2008
    #2
Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.