Frequently asked questions

Below are a few frequently asked questions (FAQs) about the Sox Tools.

Q: Is there any difference between the Sox tools that are available in Sedona Framework TXS-enabled Niagara Workbench and those available in Sedona Workbench?
Q: What is a PAR file?
Q: Is there a relationship between the schema of a Sedona Framework device and its platform archive, and if so, what?
Q: How can I avoid the situation where a kit fails to install on a Sedona Framework device due to insufficient space?
Q: Why do certain provisioning operations fail on my JACE-2 series controller?
Q: On my JACE with a TXS 1.2 Sedona Network, would I ever need to open a Sox session connection to a device directly or make a Sox-tunnel connection to a device?
Q:

Is there any difference between the Sox tools that are available in Sedona Framework TXS-enabled Niagara Workbench and those available in Sedona Workbench?

A:

The same provisioning tools are available and the tools function the same in both versions of Workbench. You will notice a difference when you are provisioning through a Sedona network on a JACE, see the discussion on, Changes to provisioning tools for TXS 1.2.

NoteTo use the Sedona tools under a networked Sedona Device on a JACE station, you must first configure the JACE controller via a platform connection, using the "Sedona Environment Manager" view.

Q:

What is a PAR file?

A:

The Platform Archive (PAR) file is a zip file with a .par extension. The PAR provides a way of distributing various files and metadata about a platform into a single entity. Basically, it describes the platform. For more information on platform archive, refer to the Sedona Tools terms in the Preface section.

Q:

Is there a relationship between the schema of a Sedona Framework device and its platform archive, and if so, what?

A:

No, the schema is completely independent of the platform archive. For more information on schema and platform archive, refer to the Sedona Tools terms in the Preface section.

Q:

How can I avoid the situation where a kit fails to install on a Sedona Framework device due to insufficient space?

A:

Currently, there is no way to avoid this. The maximum file size is device-dependent. Sedona does not provide a way to know a device’s maximum file size.

Q:

Why do certain provisioning operations fail on my JACE-2 series controller?

A:

On the JACE-2 series”, the maxHeap license feature is required in order to compile scode. Provisioning operations that involve compiling the scode will fail without the maxHeap feature. For more details on this, refer to, Provisioning fails when compiling scode on JACE-2 series platform.

Q:

On my JACE with a TXS 1.2 Sedona Network, would I ever need to open a Sox session connection to a device directly or make a Sox-tunnel connection to a device?

A:

A Sox connection would be necessary if you are using Sedona Workbench or if you have a standalone Sedona device with no Niagara integration. Also, it may also be useful for testing and troubleshooting purposes to open a Sox session connection to a device (either direct Sox or Sox-tunneled). Using a Sox connection, scode and sax files compile faster on your PC compared to on the JACE. You may find other ways in which performance is better with a Sox connection.

NoteCopying/pasting from one app to another where the schemas are different could cause unexpected behavior. In cases of schema mismatch, the Workbench connected via a Sox session protects against potential problems by not allowing the paste operation, whereas the Sox Gateway via the Workbench connected to the Niagara Station on the JACE does not.