navCenter - iConnect
iConnect - Device to Device Communication
iConnect enables copies of navCenter (nC) running on different devices to share both instrument data and control of a vessel's autopilot.
Bluetooth Low Energy (BLE) is used as the mode of communication. BLE is designed to use minimal power while still offering high speed data transfer. This design advantage makes BLE ideal for battery-powered devices such as smartphones and watches.
Within iConnect each copy of nC operates as either a 'Server' or as a 'Client'
iConnect Servers are able to:
- gather and display NMEA data from a vessel's instruments via a WiFi gateway
- controll the vessel's autopilot via the same WiFi gateway
- share all of their data with connected Clients
- accept commands from connected Clients
iConnect Clients are able to:
- gather and display NMEA data via their iConnect Server
- send commands to their iConnect Server
- controll the vessel's autopilot via their iConnect Server
Thus an iConnect Client is able to access all of a vessel's NMEA data and to control its autopilot without connecting to a Wifi gateway.
This approach has a number of advantages:
- A client has access to all of a vessel's NMEA data and control of its autopilot via BLE rather than WiFi; which results in a significant reduction in battery usage for the Client
- The NMEA data received by a Client has already been valiated by the Server and only changed values are transmitted to the Client. This approach results in much less data being transmiited and significently reduces the amount of work a Client has to do. Thus an iConnect Client benefits from a significant reduction in power usage; which translates to a much longer battery life.
- Up to 6 Clients can be simultaneously connected to a Server. Extending access to the vessel's NMEA data as WiFi gateways normally allow between 1 and 3 connections
Most Apple device can act as an iConnect Server but the Apple Watch may only operate as a Client. However iConnect greatly expands the Watch's usefulness as it is able to connect to any iConnect Server no matter what device is hosting it.
Thus nC running on a Watch is no longer limited to exclusively connecting to its partner iPhone as a Watch is now able to access a vessel's data and control its autopilot via an iConnect Server running on (say) an iPad or indeed another iPhone.
The Watch's connection to an iPad or iPhone is maintained simultaneously with any connection to its partner iPhone. Allowing the Watch to respond to messages, alerts etc from its partner iPhone while monitoring and controlling a vessel via iConnect.
A Watch's link to an iConnect Server is totally independant of its partner iPhone and will be maintained even if the iPhone is switched off.
iConnect - Overview
The following diagram is an example of how iConnect may be used to distribute data and autopilot control across a number of devices.
In the center of the diagram we have an iPad which is conected to the vessel's instruments via a WiFi gateway. The iPad is acting as an iConnect Server and is distributing its NMEA data and responding to commands from a range of connected devices.
On the left of the diagram an Apple Watch is connected to the iPad as an iConnect Client.
On the right of the diagram is an iPhone connected to the iPad as an iConnect Client. This iPhone is also connected to its partner Watch and is consequently sharing its data and responding to its Watch via Apple's WatchConnection software.
At the bottom of the diagram is a MacBook connected to the iPad as an iConnect Client.
By utilising iConnect all of the devices are able to view the vessel's MNEA data and control its autopilot but with only the iPad having to be connected to the WiFi gateway.
The iPad is doing all the heavy lifting of negotiating with the WiFi gateway, collating, interpreting, formatting the vessel's NMEA data as well as directly controlling the autopilot.
The iConnect Clients benefit from the Servers hard work allowing them to display data and control the autopilot exactly as the iPad can but with a significant reduction in their CPU requirements and thus battery usage.
Bluetooth Prompt
When you first attempt to setup an iConnect Server or an iConnect Client you will be presented with a prompt from iOS or WatchOS asking you to Allow navCenter to use Bluetooth.
If you do not grant permission for navCenter to use Bluetooth then you will not be able to use iConnect.
So be sure to Tap Allow whenever you are presented with this prompt or any variation of it.
Trust this computer Prompt
Depending on the device and version of the operating systems being used you may also be prompted to "Trust this computer" on one or both of the devices that you are attempting to pair for iConnect.
Depending on the device and version of the operating system it is running you may also be prompted to "Trust this computer" on one or both of the devices that you a are pairing for iConnect. This prompt is often presented when pairing with an Apple Watch.
Be sure to "Trust this computer" whenever you are presented with this prompt or any variation of it.
Set up an iConnect Server
Using the device designated to be connected to the WiFi gateway and act as an iConnect Server:
- Expose the menu bar and Tap 'Settings'.
- Tap the switch to activate 'iConnectServer'
- Tap 'Update' (top right of View) to expose 'Setup iConnect Server'
- Tap 'Setup iConnect Server'
Bluetooth
Connect a Client to a Server
Tap 'Stop Scanning' on both Client and Server.
- On the Client Device tap on the name of the Server that you wish to connect to. In the first screenshot below the Server is called 'Byron's iPad'
- The View (second screnshot) will now show that the chosen device has been selected but both the Server and navCenter running on that device are currently disconnected.
- Tap 'Connect'
The Client View will then be updated to show that both the Device and navCenter are now connected. Exit Client setup and Settings. You should now be receiving data from the iConnect Server. Provided, of course, that the Server is itself receiving data from the WiFi gateway.
The third screenshot has both the menu and info bars exposed. The info bar displays the status of iConnect and the name of the Server that the Client is connected to.
Server Found
Server Selected
Receiving Data
Connecting an Apple Mac to a Server
An Apple Mac or MacBook with Apple Silicon is able to run navCenter and thus operate as either an iConnect Server or Client.
The procedure to setup a Client or a Server is exactly the same as that for an iPhone or iPad.
However MacOS is fussier than iOS and so we have found that the best procedure is to first clear any Bluetooth connections that the Mac holds for the device intended to be the Client or Server and clear any Bluetooth connections that the Client or Server device holds for the Mac. Then close and restart navCenter on both devices.
You may find that on initially restarting navCenter you will need to prompt the connection. E.g. A Client may need to issue a Connect command and if a Mac is a Server it may need to advertise for a second or two after a Client has issued a connection request.
Once an iConnect connection has been setup successfully it will be stable and the connection will automatically be made and maintained whenever the devices are in range of each other.
Connecting an Apple Watch to a Server
navCenter running on an Apple Watch is able to use either Apples WatchConnection or iConnect to interact with a vessel's instruments. This choice must be made via Watch's Settings before an iConnection releationship can be specified.
The first Watch screenshot is displaying a Compass.
Near the top of the display the blue circles show that the Compass View is in the third Stack of four. The Diamond to the right tells us that the Compass is View is in the middle of the Stack.
At the bottom of the display is an information bar.
- The number to the right is the sequential Page number within the Stack sequence.
- The Apple to the left is white indicating that the Watch is connected to its partner iPhone. If the apple is orange then the Watch is not connected to its partner iPhone.
- To the right of the apple the radio icon is orange indicating that the Watch is not linked to a Server.
Navigate to the iConnect Server View on the device chosen to act as the Server and tap 'Start Scanning'. Then tap on the information bar on the Watch to display the Settings View as shown in the second screenshot.
- You are likely to see that 'WatchConnection' is selected. Tap this selection and instead select 'iConnection'as shown in the screenshot.
- Tap '<' to return to the the Watch menu and Tap 'Bluetooth'
- You will then be able to tap the 'Servers' button to return select an iConnect Server. The first time you do this there will be no Servers displayed.
- Tap 'Start Scanning' on the Watch.
- Once the chosen Server is displayed on the Watch View Tap 'Stop Scanning' on both devices.
- On the Watch Tap to select the Server from the list displayed. Then you will see a View confirming your selection. In the example here we have selected 'Byron's iPad'.
- Tap 'Connect' to establist the connection.
- Tap '<' to return to the the Watch menu
- Tap 'X' to exit from the Watch menu
You will then be returned to navCenters set of data Views. In the example here navCenter is displaying the compass.
On the info bar you can see:
- The apple is white; indicating that WatchConnection is active and avalable for all apps.
- Th WiFi symbol is blue; indicating that iConnection is active and being used by navCenter for data transfer and control.
