Interruption to PAC Transfer

Hi Folks,

I've had a terrible issue occur whereby my laptop froze during a PAC logic file transfer via USB. And... after rebooting the laptop (necessary) I can't seem to connect to the PAC any longer.

Any suggestions on how to get the PAC reset etc?

Thanks in advance.

 

look like you must wait until 24 hours before use the pac again.
let the backup power inside the pac drown off, then it will reset it..
or maybe the firmware of the pac are crashed.. if it is, the the only way it to sent it to technical support..

 

There are some brief things to check in the FAQ topic "Can't connect to PAC".

Were you updating the firmware at the same time, or just the project?

Set your PICED log to save to a file and enable the C-Touch/PAC messages. Try to connect to the unit, and post the results (just the relevant part of the log) here, or send to tech support.

 

The power supply in the PAC will maintain power to the processor for a fraction of a second after power failure. It will make no difference whether you wait for 2 seconds or 2 days before using the PAC again.

The only "backup power" is used for maintaining the time, but this will not affect the operation of the PAC.

You should always be able to re-connect to a PAC, even if you only transferred part of the firmware or project. The only time you would normally need to return a unit is if there is some sort of hardware fault.

 

I was updating project logic only.

Ok, when I scan the unit now in toolkit -- it produces an error "Secondary Firmware Version was not Loaded" and "Could not Communicate with the Physical Unit". Strangely it is able to get the status of the unit when I click on the Status tab.

When I try to "Connect to Unit" in PICED I receive the error:

Could not connect to unit.
Communications Failed.

Select Change Port to change the port and try again.

Log in Piced is empty. I definitely have the correct connection settings, and connecting via CBUS fails.

Is it one for technical support (contact details handy please? )? Anything else to try?

Thank you!

 

So the PAC appears when you scan the network ? If so then at least half of the PAC is working

If you get the message "Secondary Firmware Version was not Loaded", it probably means that the C-Bus half of the unit is not communicating with the other half. If this is the case, it is probably a hardware fault.

If the log is empty, you must have some of the required options switched off. You will need to select:
- Show Info Messages
- Show C-Touch/PAC Messages
- Show Event Time
- Save to File

You should see something like this in the log (this is the bit we need to see):
11/09/2009 9:22:47 AM Info : Connecting to unit at 9600 baud
11/09/2009 9:22:47 AM PAC : Tx "80 00 00 06 FF 7A "
11/09/2009 9:22:47 AM PAC : Rx "FF FF 00 06 FD FC "
11/09/2009 9:22:47 AM Info : Connecting to unit at 38400 baud
11/09/2009 9:22:47 AM PAC : Tx "80 00 00 06 FF 7A "
11/09/2009 9:22:48 AM PAC : Tx "80 00 00 06 FF 7A "
11/09/2009 9:22:48 AM PAC : Rx "FF FF 00 06 FD FC "
11/09/2009 9:22:48 AM PAC : Tx "8E 00 00 06 FF 6C "
11/09/2009 9:22:49 AM PAC : Tx "8E 00 00 06 FF 6C "
11/09/2009 9:22:49 AM PAC : Rx "8E 01 00 0A DE AD BA BA FC 68 "

They will probably need to forward this particular enquiry to me anyway.

There are a few other things to check:
- are there any PAC LEDs flashing?
- In your Windows Device Manager, do you see a COM port for the PAC?

 

In terms of PAC LEDs -- both are lit up (CBUS and UNIT COMMS) and the UNIT COMMS flashes twice periodcially every 2 seconds.

The connection between the PC and the PAC are fine since I am able to connect between another/other PAC and the PC. Or is there something else to check there?

 

What is the status LED doing?

See if you can get the log messages for us.

If a different PAC works OK, it might be a hardware fault.