Network integration of Jennic-based devices (and proxy points)

As the “coordinator” node, the Sedona Jennic-equipped JACE supports a network of wireless Jennic-based devices. Station integration requires a “SedonaJen6lpNetwork”, where you set its properties PanId and Channel to match the equivalent properties in the installed devices (App:service:plat).

Figure 1. SedonaJen6lpNetwork has properties related directly to Sedona Jennic option card


SedonaJen6lpNetwork has properties related directly to Sedona Jennic option card

In the configuration of the SedonaJen6lpNetwork, you also specify an IPV4 address base to use for mapping the Jennic-based device into the station—this must be an unused “private IP subnet” using either a Class A, B, or C formatted IP address. It cannot be the same IP subnet used by the JACE.

If properly configured, when you enable the SedonaJen6lpNetwork, the JACE coordinator automatically broadcasts a message that results in responses back from the Jennic-based devices. Corresponding entries in the network’s “Address Map” table auto-populate, where for each Jennic-based node a unique IPV4 address is associated for that device (listed by its unique 64-bit MAC address).

In the default “Sedona Jen6lp Device Manager” view of the network, a “Discover” simply shows the IPV4 addresses of the existing address map entries, as shown in Figure 1 above.

You add discovered devices to the SedonaJen6lpNetwork, using the Add dialog. Device type is always Sedona Jen6lp Device, with address entries typically left at default, as shown in Figure 2 below.

Figure 2. Add dialog in Sedona Jen6lp Device Manager with defaults shown


Add dialog in Sedona Jen6lp Device Manager with defaults shown

Often at first you leave device Names at the default “dev IP address”, until you can associate each component with a specific physical device. Then you can rename with more meaningful text.

Device components each have a points extension in which you can discover Sedona Framework components, and select child properties and actions to model as NiagaraAX proxy points.