My ZUMNET-JBOX or ZUMLINK device reports as an UNDEFINED model type?
Sometimes, ZUMNET-JBOXs or ZUMLINK-* devices will report as an "UNDEFINED" model type when queried in Network Device Tree view or using the "ppndiscover" Text Console Command.
In this case, it is necessary to connect to the ZUMNET-JBOX and run a specific text console command to correct the device.
The command to run takes the format: rcon [netID].[CID] setmodel [modelNumber]
Once the command has been run, reboot the ZUMNET-JBOX using the reboot command. Refer to the table below for the [modelNumber] for each device. The [netID] for all ZUMNET-JBOXs is "1". ZUMLINK devices landed on Net 2 of a DIN-CENCN-2 will require a [netID] of "2", while ZUMLINK devices landed directly on a processor will not have a [netID].
For example, a ZUMLINK-DT-QUATTRO-DLS at CID 05 reporting as a ZUMLINK-OCC-VAC-UNDEFINED-DLS should be corrected with the command: rcon 1.5 setmodel 3
Undefined Model | Correct Model | Model Number |
ZUMLINK-OCC-VAC-UNDEFINED-DLS | ZUMLINK-IR-QUATTRO-DLS | 1 |
ZUMLINK-OCC-VAC-UNDEFINED-DLS | ZUMLINK-IR-QUATTRO-HD-DLS | 2 |
ZUMLINK-OCC-VAC-UNDEFINED-DLS | ZUMLINK-DT-QUATTRO-DLS | 3 |
ZUMLINK-OCC-VAC-UNDEFINED-DLS | ZUMLINK-US-QUATTRO-DLS | 4 |
ZUMLINK-OCC-VAC-UNDEFINED-DLS | ZUMLINK-US-ONEWAY-DLS | 5 |
ZUMLINK-OCC-VAC-UNDEFINED-DLS | ZUMLINK-US-HALLWAY-DLS | 6 |
ZUMLINK-OCC-VAC-UNDEFINED-DLS | ZUMLINK-IR-QUATTRO-DLS-RLY | 7 |
ZUMLINK-OCC-VAC-UNDEFINED-DLS | ZUMLINK-IR-QUATTRO-HD-DLS-RLY | 8 |
ZUMLINK-OCC-VAC-UNDEFINED-DLS | ZUMLINK-DT-QUATTRO-DLS-RLY | 9 |
ZUMLINK-OCC-VAC-UNDEFINED-DLS | ZUMLINK-US-QUATTRO-DLS-RLY | 10 |
ZUMLINK-OCC-VAC-UNDEFINED-DLS | ZUMLINK-US-ONEWAY-DLS-RLY | 11 |
ZUMLINK-OCC-VAC-UNDEFINED-DLS | ZUMLINK-US-HALLWAY-DLS-RLY | 12 |
ZUMNET-UNDEFINED | ZUMNET-JBOX-16A-LV | 1 |
ZUMNET-UNDEFINED | ZUMNET-JBOX-DALI | 2 |
ZUMLINK-UNDEFINED | ZUMLINK-JBOX-16A-LV | 3 |
ZUMLINK-UNDEFINED | ZUMLINK-JBOX-20A-SW | 4 |
ZUMLINK-UNDEFINED | ZUMLINK-JBOX-20A-PLUG | 5 |