Sox tunneling through station for native Sedona configuration

NoteStarting in Sedona TXS-1.2 with AX-3.7 and later, the importance of Sox tunneling has diminished in favor of the Sox Gateway and Sedona Tools now available under each networked Sedona device. However, in some cases Sox tunneling may still be a desired method to open a networked device. For related details, see the Sedona Framework TXS 1.2 Networks Guide sections “Sox Gateway” and “Sedona device ‘tools’ views”, as well as the Sedona Framework TXS Sedona Tools Guide.

Provided that the JACE’s license has the tunneling feature, with its attribute “sox=”true””, and it has the SoxTunnel component (from the nsedona module) copied into the station’s Services container, you can use Workbench to “tunnel” through the JACE to open Sox connections to devices in its network. Once Sox-connected to a device, you can make Sedona Framework app configuration changes, or use any of the Sedona Tools (Application Manager, Backup/Restore Tool, Kit Manager).

Figure 3 below shows the right-click “Open Sox Tunnel Session” menu option on a Jen6lp device, and the resulting authentication popup dialog.

Figure 3. Sox tunneling as right-click option on SedonaJen6lpDevice


Sox tunneling as right-click option on SedonaJen6lpDevice

When sox tunneled to a Jen6lp device, you can use Sox Tools or work in its app, as shown in Figure 4.

Figure 4. Sox tunnel session through JACE to wireless Jennic-based device


Sox tunnel session through JACE to wireless Jennic-based device

Figure 4 shows the wire sheet view of a folder in the Sedona Framework app, with components that have shapes and behavior that are similar to NiagaraAX components. As when working in the station database, when working in a Sedona Framework app you must explicitly save changes, to write to the device’s Flash memory. Otherwise, RAM-resident changes are lost on the next device restart/reboot.

For Sox tunneling details, see the Sedona Framework Sox Tunneling - Engineering Notes document.