Sedona Framework TXS 1.1 FAQ

Sedona Framework™ TXS 1.1 M T h e S e d o n a F r a m e w o r k ™ T X S 1 . 1 s o f t w a r e p a c Page 1/3 TridiumEuropeFAQ_Sedona TXS1.1_v1 Can I use Sedona Framework TXS 1.1 with NiagaraAX 3.5 or earlier? No, Sedona Framework TXS 1.1 is designed to work with NiagaraAX 3.6 or later. Frequently Asked Questions Is Sedona Framework TXS 1.1 compatible with the Open Source Sedona Framework 1.0? Yes, Sedona Framework TXS 1.1 was built against the Sedona Framework 1.0 Open Source release Can I use a NiagaraAX 3.5 or earlier station containing Sedona Framework devices with NiagaraAX 3.6 or later? Yes, but you will need use the Station Migration Tool in order to convert the Niagara 3.5 or earlier station containing the Sedona Framework devices for use with Niagara 3.6 or later Do I need a license for my NiagaraAX Workbench in order to use it with Sedona Framework devices? Yes and the license features to enable a NiagaraAX Workbench to have the required functionality to work with Sedona Framework Ethernet/Wi-Fi and Jennic devices have been added to the license file. You should update your licenses because this has just recently been added Are there separate Sedona Framework network drivers for Ethernet/Wi-Fi devices and Jennic 802.15.4 devices? Yes, Ethernet/Wi-Fi devices require the same SedonaNetwork driver while Jennic devices require the SedonaJen6lpNetwork driver Do you need a Wi-Fi option card to talk to Wi-Fi enabled Sedona Framework devices? No, the Wi-Fi device will talk to a Wi-Fi Access Point. From there the JACE can communicate to the Wi-Fi Access Point using Ethernet or Wi-Fi Can the JACE act as a Wi-Fi access point for Wi-Fi enabled Sedona Framework devices? No, the JACE cannot act as a Wi-Fi Access Point. The Sedona Framework devices communicate through an external Wi-Fi Access Point to the JACE Can I use a SOX driver from a developer other than Tridium with my Sedona Framework devices? Yes, but many of the features and enhancements developed as part of Sedona Framework TXS 1.1 will not work with drivers from other manufactures. For example the SOX Tunneling feature developed by Tridium requires Tridium’s SOX driver and licensing feature Will the PAN Visualisation tool work with non-Jennic based RF Networks such as Wi-Fi Sedona Framework devices? No, the PAN Visualisation only works with Jennic-based Sedona Framework devices Is CHoPAN an open standard communication protocol? No, CHoPAN is a proprietary communication protocol developed by Tridium. Tridium did submit CHoPAN to the IETF (Internet Engineering Task Force) for adoption as an IETF standard communication protocol but they have since selected a different communication protocol called CoAP Does CHoPAN work with Ethernet or Wi-Fi Sedona Framework devices? Not at this time. Tridium’s current implementation of CHoPAN communication will only work with Jennic-based Sedona Framework devices. We are considering expanding this functionality to Ethernet/Wi-Fi devices in the future Is CHoPAN only used with hibernating battery powered Jennic-based devices? No, CHoPAN can be used by continuously powered devices as well. Using CHoPAN with continuously powered devices generates less network traffic vs. SOX, which allows for the deployment of larger Sedona Framework enabled Jennic wireless device networks Can I use CHoPAN communication to program, provision or commission a Sedona Framework device? No, CHoPAN is only for exchanging data. You still need to use SOX communication for programming, provisioning or commissioning the Sedona Framework device Can I use the Sedona Framework Workbench with all of the Sedona Framework TXS1.1 features? No, the Sedona Framework Workbench only allows the Workbench Tool to connect directly with the Sedona Framework enabled devices for programming, provisioning and commissioning that device. It does not allow you to make a station connecting between the Sedona Framework Workbench Tool and a NiagaraAX station. Thus, several of the NiagaraAX Sedona Framework Network features such as PAN Visualization are not accessible using the Sedona Framework Workbench Tool Can I use SOX Tunneling to tunnel through a NiagaraAX Supervisor and NiagaraAX JACE simultaneously in order to engineer my Sedona Framework device connected to the JACE? No, the currently implementation of the SOX Tunneling feature only allows you to tunnel through a single NiagaraAX station. Tridium is looking into ways to support this capability as part of a future release Sedona Framework™ TXS 1.1 Frequently Asked Questions Page 2/3 TridiumEuropeFAQ_Sedona TXS1.1_v1 Tridium Europe Ltd 1 The Grainstore, Brooks Green Road, Coolham, West Sussex, RH13 8GR, UK Telephone: +44 (0) 1403 740290 www.tridiumeurope.com Page 3/3 TridiumEuropeFAQ_Sedona TXS1.1_v1 Sedona Framework™ TXS 1.1 Frequently Asked Questions Can I use the IOS30P controller with Sedona Framework TXS1.1? Yes. You can use the IOS30P controller with NiagaraAX 3.4.x, 3.5.x and 3.6.x but you must ensure that the correct files are copied from the support image pack into the correct folders in your Workbench and JACE. For more details please refer to the IOS30P Quick Start Guide. Can I connect an unlimited number of Sedona devices to an AX Supervisor? No. The connection of Sedona devices to the AX Supervisor is treated the same way as other AX Supervisor open drivers such as BACnet IP and LON IP. There is ‘Sedona IP Driver with 500 points’ and ‘Additional 500 Sedona points’ products available for the AX Supervisor Can I connect an unlimited number of Sedona devices to an AX JACE? No. The number of Sedona devices that can be connected to an AX JACE is determined by the capacity of the JACE in the same way as other AX JACE open drivers. The license features required for the operation of Sedona TXS 1.1 in all varieties of AX JACE are included as standard ‘Open Drivers’ along with, for example; Modbus, BACnet IP/MSTP, LON, KNX-IP and SNMP. In other words, if BACnet is restricted to 8 devices then Sedona is similarly restricted to 8 devices