Specifications

PICED FAQ

Page 28

1. The serial ports (for sending debugging messages)

2. The User LED (for showing simple status)

3. Sending messages to PICED to warn of errors The

Transfer | Control Unit | Log PAC

Messages

menu item can be used to monitor any PAC Error Messages and the PAC usage.

See the logic manual for more details on using the PICED software debugging features.

Note that you can create pages and components in a PAC project, even though the PAC doesn't

use them. This allows you to test a PAC project in PICED by controlling and monitoring C-Bus

through the use of C-Bus Components. You can also use the log and other PICED debugging

features.

1.3.3.6 Can't connect to PAC

Problem

Problems with connecting to PAC from the PICED Software.

Solution

Check that the PAC is recognised when it is plugged in. If not, re-install the PAC USB driver.

Check that you have the correct Serial Port selected.

Problem

On connecting there is an error 14603 - "Could not connect to Unit. Wrong device type".

Cause

The device you are trying to connect to is not a PAC unit.

Solution

Check that you are actually connected to a PAC unit.

Check that you have the correct Serial Port selected.

1.3.3.7 PAC Serial Ports

The PAC serial ports do not support hardware or software flow control.

To connect a device to a PAC, you will need a "null modem" cable. The wiring diagram for this is

shown below. In this case, the handshaking lines can be used to power the PAC serial port from

the user device. The dotted lines in the PAC show the "loop back" connections to make hardware

handshaking work. This is the cable supplied with the PAC.