Copyright 2008-2010 Mode Lighting Ltd. All rights reserved.Control4Mode Lighting Ltd.07/01/2008 12:00 PM07/07/2011 12:00 PMTCP MBus InterfaceTCP MBus Interface150devices_sm/c4modI_16.gifdevices_lg/c4modI_32.giflua_genotherstruemodelighting_tcp_mbusDriverWorks57600 8 none 1 noneAlwaysOnLights16Serial 2321TrueFalseFalseFalseRS_23226Mode Lighting MBus1FalseFalseFalseFalseMODE_MBUS60016Lighting Processor Connection4TrueFalseFalseTrueTCP2222TruetruetrueControl4 certified on 8/23/2012 for software released versions: 2.2.2 This is the MBUS Interface driver. This driver is used to allow communication between a CONTROL4 controller and a Mode Lighting MBUS enabled module. The MBUS Interface driver should always be added FIRST to a project BEFORE adding any other Mode Lighting MBUS enabled drivers. This is because the other 'client' drivers are designed to 'Auto-Bind' to the MBUS Interface driver when they are added. If the MBUS Interface is not present when other drivers are added, they cannot auto-bind, and therefore they would need to EACH be manually bound at a later time. When using the Network Processor Unit . Download the software for the Network Processor Unit, this can be found at control4.eu/download. . Log in to the Network Processor Unit and update the firmware and the webapp aplication. (ipaddress)/firmware.html . Go to Connections in composer - Network and type in the IP address of the unit. . Set the driver properties so Control4 is not master. Connection StatusSTRINGtrueMBus MasterLISTNoYesNofalseDebug ModeLISTOffPrintLogPrint and LogOfffalseList MBus DevicesLIST_DEVICESList C4/MBus BindingsLIST_BINDINGSRebuild C4/MBus BindingsRESET_DEVICE_MAPControl4 certified on 8/23/2012 for software released versions: 2.2.2ip