Hi @Sakthivelj,
The Ping360 has an ethernet communications interface option, from which you can connect it to the network hardware you desire. A couple of potentially useful components are this adaptor (to connect to a standard ethernet cable) and/or our Ethernet Switch (to connect to a local network, potentially including a wifi radio connection).
Ping Viewer can find and connect to Ping360 devices that are accessible on the local network, so to receive data over the internet requires using a VPN between a computer that is locally networked to the device and the computer you’re running Ping Viewer on. That should be possible using ZeroTier (for context, we run the ZeroTier BlueOS extension on the onboard Raspberry Pi when we’re doing remote connections for internal vehicle testing).
A couple of things to consider:
- Internet connectivity is generally less reliable than a tethered connection, which may result in loss of data
- The Ping360’s network communication is done via UDP, which does not check for packet delivery success, so if some of the data request commands or returned profile data messages get lost in transit then they won’t automatically be re-requested/re-sent, and may cause lag spikes while Ping Viewer is waiting for a response from the device
- Not all internet connections are equal - consider the upload bandwidth of the device side and the download bandwidth of the control computer side
- It’s unlikely this will be a problem, especially since scanning sonar data is much lower bandwidth than a video stream, for example, but it’s worth keeping in mind, especially if you’re planning to use a low bandwidth mobile data setup or something