The third media for device to device communication
In the building cellars of Norway thousands of PINGO devices are retrieving energy data every hour
When wireless fail, PINGO can do it
The third media for device to device communication
In the building cellars of Norway thousands of PINGO devices are retrieving energy data every hour
When wireless fail, PINGO can do it
IoT normally rely on two methods for data communication:
By hardware PINGO is implemented as a DINGO plug-in. This plug-in can be installed either in a DINGO Base Board (DBB) or into DINGO Pass-through Modem.
PINGO is a master-slave technology. That is to say a single master always initiates a communication to slaves. The slaves form a mesh network, extending the communication range to tenths and even hundreds of kilometers.
Broadcasting a message to a group of slaves in one command is possible. Very practical for example in lighting control.
For working on all 3 phases of a 3-phase power-line network, 3 plug-ins have to be installed in the master DBB, but just single plug-in is needed in the slave DBBs (or Pass-through Modem).
The DINGO software stack implements a very powerful support for PINGO in it's Peripheral Manager. In addition it implements a so called APDU-to-APDU BACnet Virtual Gateway. This is because N-PLC technology is "narrow", or simpler said, "slow". The gateway overcomes the slow communication, by buffering values from multiple slaves in the master DINGO. By doing that the data in the slaves is immediately ready when requested from any BACnet client. Similar approach is used when writing to a PINGO slave.
Implementing this gateway makes it possible for PINGO enabled devices to show up as normal BACnet devices behind a BACnet router.
More about the PINGO plug-in in section 5 here...
More about the DINGO Passthrough Modem products here...
More about the BACnet APDU to APDU Virtual Gateway in section 5 here...