Peer-to-peer configuration example

Chopan points can also allow Jennic-based devices to directly exchange data (peer-to-peer). Engineering is similar to the previous example, beginning with Chopan Virtual gateway access to the client (requesting) SedonaJen6lpDevice in the station. See Figure 13.

Figure 13. Chopan Virtual gateway used to make Chopan (client) points in peer-to-peer data exchange


Chopan Virtual gateway used to make Chopan (client) points in peer-to-peer data exchange

In the Figure 13 example, the SedonaJen6lpDevice for Dev_1 has its Chopan Virtual gateway accessed in order to add a ChopanDevice representing Dev_3 under its ChopanNetwork. Then, as shown on the left side, Chopan points are added under that device—in this case one Float Point for a count slot in the Dev_3, and another Boolean Writable for the in slot of a relay 4 output in Dev_3.

This creates Chopan points in the client device’s app (ChoFltPt, ChoBoolWr), which are then typically linked into other components in the app (in order to read/use remote count value, write remote relay output). Note that Chopan points persist only in the requesting client Jennic-based device (Dev_1).

In this case, Dev_1 requires Chopan client configuration, and Dev_3 requires Chopan server configuration. Note that both devices could also be (additionally) configured in a complimentary fashion, say if Dev_3 required client access to read or write values served by Dev_1. However, this is not shown here.

Because of the underlying JenNet tree structure of the wireless network of Jennic-based devices, the communications path of CHoPAN messaging between devices may not be directly between the client and server nodes. For example in the network in Figure 13, Dev_3 may be a child node of Dev_2 (acting as a router), such that Dev_1 to Dev_3 messaging involves Dev_2. Note that JenNet uses a “self-healing” tree architecture, such that it automatically re-configures if routing changes are warranted.