Occupancy Sensor mismatch

When adding units to a new project there are 2 options for each Occupancy Sensor model i.e. 5750WPL (SENPIRSS or SENPIROA), 5751L (SENPIRSS or SENPIRIA), and 5753L (SENPIRSS or SENPIRIB).

Question. If you pick the model with SENPIRSS as it's unit type why doesn't the network recognise and match up with the database unit? The only way to match units is to match serial numbers and manually input the Group Addresses and Part Name because you get an error message that unit types are different and cannot transfer database programming.

 

Which version of Toolkit are you using?

 

Reply

Using 1.3.0.

New project written yesterday. All output modules and KIU's scanned and updated no problems but 5750WPL's, 5751L's, and 5753L's all wouldn't match when trying to Set Address to Database after scanning new unit.

 

Hi Pronga,

Using Toolkit 1.3.2.

If you select the Database Unit you can readdress it to match the Network Unit. If you then open the Database Unit Toolkit will convert the type of the database unit to the actual unit found on the network.. the pair can then be readdressed back to your original database address.

This is quite cruddy, as you've probably found its not possible to address the Network Unit to match the Database..

This will be improved in a future release (probably the next one).