Live debug is supported by some hardware models. Live debug works exactly like simulate mode with one huge exception: The program is actually executed on live hardware connected via the network. You can single step and set breakpoints just like in simulation. You can set I/O values, although in this case the inputs are likely to be overwritten by actual input hardware scanning. Setting outputs will actually turn things on. The live debug can take place on a live network with numerous other devices online. This means writing registers that result in network communications to other devices will actually have effect on those other devices while you are debugging. WARNING: Live debug is powerful, but potentially dangerous. You are advised to manually override or disable power on devices that could cause harm by inadvertant or badly timed switching on of the device. When you set breakpoints or single step a program, it means you are purposely interferring with functionality that might otherwise provide some element of safety. Live debug mode is entered when you check Live, then click the Reset icon next to the Debug (green bug) button. When the device is connected via Ethernet, you need to enter its IP address. Some devices may be connected via the serial port, in which case you select the appropriate COM port instead of TCP/IP. Target ID is either a BACnet device instance, or Modbus slave ID.
There is one minor difference about the watch list in live debug versus simulation. While in simulation, the watch list is populated automatically. For live debug, you need to explicitly request the registers or objects by entering the name or number in the add/change box and clicking Get. When you make changes to your drawing, you must first exit debug mode, which includes disconnecting from the debug target. Edit and rebuild code the same way you would for simulation. When you re-enter debug mode and reconnect to your live target, clicking Reset (yellow arrow icon in debug toolbar) will cause the updated code to be automatically downloaded to your target device's debug environment. Note that this download does not upload the code file into the target device's file system. It only temporarily loads the code into the target's debug environment. To permanently load the program, use the upload method supported for the particular device (may vary by model). |
