Configuring the Adept Controller as a DeviceNet Slave
The following text describes how to configure the Adept controller as a DeviceNet slave. It includes the ESD information that will be required by the Master device. This example configures 8 inputs and 8 outputs for the Adept controller that can be accessed by the DeviceNet master. For general information on DeviceNet, see the MV Controller User's Guide for V+ 13.0 and Later.
Adept Controller Configuration
Using the Adept CONFIG_C utility, add the following lines in the DeviceNet section of the V+ system configuration:
LOCAL = "/MACID 2 /BAUD 500"
MAPPING 1 = "/MACID 2 /BYTE 1 /BIT 1 /BIT_LENGTH 8 /SIGNAL
65"
MAPPING 2 = "/MACID 2 /BYTE 1 /BIT 1 /BIT_LENGTH 8 /SIGNAL
1065"
After the lines have been added and saved:
- Verify that the Device Net master is online and that the CAN bus has power.
- Reboot the controller.
- Type DEV at the monitor prompt after the controller has been rebooted to display the current DeviceNet hardware status.
- Verify that the status indicates ONLINE. If the status does not indicate ONLINE, issue a DN.RESTART at the monitor prompt and recheck the status when it completes.
Adept ESD Hardware info required by Master device
| Mac ID | 2 (for this example) |
| Input size | 64 (bytes) |
| Output size | 64 (bytes) |
| Vendor ID | 279 |
| Device type | 12 |
| Product Code | 1 |
Mapping inputs on the Master device for Mac ID 2 starting at Byte 1 and Bit 1 with a bit length of 8 will connect those Master device inputs to Adept Controller outputs 65-73 (for this example).
Mapping outputs on the Master device for Mac ID 2 starting at Byte 1 and Bit 1 with a bit length of 8 will connect those Master device outputs to Adept controller inputs 1065-1073 (for this example).
|
Last modified on: 01/23/2006
|
|
|
