Introduction
The EOS Connected Bridge allows you to collect information and statistics about your EOS network. The information is sent to EOS Connected, Bever Innovations’ own web portal. The EOS Connected portal allows you to keep track of your EOS luminaries’ power usage, device availability, ambient light and temperature and more.
When the EOS Connected Bridge is connected to an IC-U or Sign Controller in a price totem, it also allows you to manage display prices from within EOS Connected.
The bridge can connect to the internet either using a wired Ethernet connection or by connecting to a cellular (mobile) network.
Device monitoring
At startup the bridge will obtain a list of devices from EOSConnected so it knows what devices are located at the site where it is installed. This device list will be created using the EOS Manager during project commissioning. The Bridge will keep track of these devices by monitoring statistics like power usage and temperature.
Additionally the bridge will check the availability of each device on an hourly basis. Normally a devices availability will be 100%. When a device can’t be reached for an hour – for example due to power loss - the availility will drop down to 0%. If a device can only periodically be reached the availiability will be somewhere between 100% and 0%. This situation could indicate a coverage problem in the EOS network.
Configuration
Basic configuration
Basic configuration tab | Range | Default |
Bridge host | ||
Bridge own network idThe network of the bridge itself. The EOS Connected bridge can listen to multiple networks (1-30) but also needs a network of its own. | 1-30 | Not set |
Use cellular modemUse the cellular modem to connect to the internet instead of the wired ethernet connection. This will require a working SIM card. | Yes/No | No |
Bridge cellular to secondary LANEnables cellular connection bridging to the secondary LAN connection (eth1). This allows you to connect external devices to the internet through the bridge. ‘Use cellular modem’ should be set to Yes for this option to work. | Yes/No | No |
Cellular APN selectionFor some mobile providers a custom APN (access point name) should be used. 0: Automatically find APN based on provider name. This option will work with most major providers. 1: reserved. 2 and up: use provider-specific APN. Please refer to the table in chapter 5 of this document. | 0..999 | 0 |
Listen to networksThe Eos network(s) the bridge needs to listen to. | Network 1-30, Own/All networks | None |
Primary LAN DHCPEnables DHCP on the primary LAN connection (eth0). This allows the bridge to automatically obtain an IP address and other network settings from a router. | Yes/No | Yes |
Primary LAN static IP addressWhen using a static LAN configuration, use this IP address. When DHCP is set to Yes, this setting will be ignored. | 0.0.0.0 – 255.255.255.255 | 0.0.0.0 |
Primary LAN static netmaskWhen using a static LAN configuration, use this netmask. When DHCP is set to Yes, this setting will be ignored. | 0.0.0.0 – 255.255.255.255 | 0.0.0.0 |
Primary LAN static broadcastWhen using a static LAN configuration, use this broadcast address.When DHCP is set to Yes, this setting will be ignored. | 0.0.0.0 – 255.255.255.255 | 0.0.0.0 |
Primary LAN static gatewayWhen using a static LAN configuration, use this gateway address. When DHCP is set to Yes, this setting will be ignored. | 0.0.0.0 – 255.255.255.255 | 0.0.0.0 |
UART | ||
Protocol inWhat price protocol is used when receiving price data from other equipment. At this moment no receiving protocol is implemented. | 0-100 | 0 |
Protocol outWhat price protocol is used when sending price data to external equipment such as a sign controller. Currently, only protocol 26 (iDP) is supported. | 0-100 | 0 |
DNS | ||
Primary DNSPrimary DNS to use. Only needed when not using DHCP. | 0.0.0.0 – 255.255.255.255 | 8.8.8.8 |
Alternative DNSSecondary DNS to use. Only needed when not using DHCP. | 0.0.0.0 – 255.255.255.255 | 8.8.4.4 |
SMS | ||
Use SMSUse Centaure SMS-protocol to receive prices instead of the API | Yes/No | No |
Advanced configuration
Advanced configuration tab | Range | Default |
Bridge | ||
EOS Connected timeoutTimeout in seconds for a HTTP request to the EOS Connected server | 1s-60h | 10s |
EOS Connected post intervalInterval at which the bridge connects to the EOS Connected server. | 1s-60h | 5m |
Max device logs to postHow many devices are send to EOS Connected each time, maximum. | 0-500 | 100 |
Min device logs to postHow many device logs should be present to initiate posting to EOS Connected. This can reduce traffic overhead when using a cellular connection. | 0-500 | 1 |
Max data logs to postHow many device logs are send to EOS Connected each time, maximum. | 0-500 | 100 |
Min data logs to postHow many device logs should be present to initiate posting to EOS Connected. This can reduce traffic overhead when using a cellular connection. | 0-500 | 10 |
Broadcast hops for own packetsNumber of hops on transmitted packets. | 0-20 | 4x |
Network completeness intervalTime between network completeness calculation. | 1s-60h | 1h |
Automatic request suspendEnabling this feature puts the EOS Connected bridge in suspend mode. This means it will not request data from the EOS networks for 2 minutes when someone is connected to the network with EOS Manager. This will reduce traffic in the network, thus allowing better performance in EOS Manager in larger networks (20+ devices). | Yes/No | No |
EOS | ||
Device network identifierThe network of the bridge itself. The EOS Connected bridge can listen to multiple networks (1-30) but also needs a network of its own. | 1-30 | Not set |
EOS compatibility modeA device operating in compatibility mode is able to be discovered by non-EOS compatible devices using the EOS Manager.
| Yes/No | No |
In a larger network, for example with 100 or more devices, it might be necessary to change some of the settings to ‘fine tune’ the bridge to the situation.
Expert configuration
Expert configuration tab | Range | Default |
Bridge | ||
Queue max device logsMaximum number of device logs in the queue. | 0-500 | 100 |
Queue max data logsMaximum number of data logs in the queue. | 0-500 | 500 |
Presence request intervalSets how often device presence is requested. | 1s-60h | 5m |
Presence discovery counterEvery nth presense requests, do a discovery instead of a check of known devices. This speeds up device discovery after the bridge has just started. | 0-20 | 3x |
Presence request retry intervalTime between presence request retries. Should be higher in large networks (20+ devices). | 1s-20s | 5s |
Presence request retriesHow many presence requests are sent to each device. The corresponding number of replies determines a devices availability percentage. | 0-20 | 3 |
Data request intervalTime between data requests. At each data request, the bridges tries to retrieve statistics from each device in the network. | 1s-60h | 15m |
Data request retry intervalTime between data request retries. Should be higher for large networks (20+ devices). | 1s-60h | 10s |
Data request retriesHow many attempts are made to retrieve a statistic from a device. | 0-20 | 3 |
Request queue intervalSets the amount of milliseconds between transmitted request packets. | 300ms | |
Request queue max sizeMaximum number of requests in the request queue. | 0-500 | 500 |
Use discovery modeFind EOS devices instead of retrieving it from EOS Connected. | YES/NO | NO |
Operating mode | ||
Sniffer modeEOS packet sniffer mode. (0: disabled. 1: usb storage. 2: API) | 0 | 0..2 |
Force suspend modeDo not transmit EOS packets when this option is enabled | YES/NO | NO |
List of custom APNs
In case a custom APN is required for internet access through a cellular connection, one of the following APNs can be used:
Option | Provider | APN |
0 | Automatic |
|
1 | Reserved |
|
2 | Matooma | matooma.m2m |
3 | T-mobile | smartsites.t-mobile |
This list will be expanded in the future.
Document history
Revision | Date | Description |
1 | 9-2-2021 | First release. |
2 | 22-6-2021 | Added status LED colors. |
3 | 5-12-2022 | Added settings. Updated layout. |
4 | 20-12-2022 | Moved document to Freshdesk. |