• 1. Glossary
• 2. Abstract
• 3. How to use the OceanPulse
  • 3.1. Using the command line (Expert mode)
  • 3.2. Using the OceanPulse Realtime UI
    • 3.2.1. Up to version 1.17
    • 3.2.2. From version 1.18
    • 3.2.3. Calibrating Sensors
    • 3.2.4. Monitoring Data
    • 3.2.5. Managing Device Settings
• 4. General settings for OceanPulse
  • 4.1. Bill of materials (BOM)
  • 4.2. Used OS
• 5. Creating SD card for Raspberry
  • 5.1. Create the SD card
  • 5.2. Prerequisites
  • 5.3. Config helper
  • 5.4. Hostname
  • 5.5. DNS
  • 5.6. Users and groups
  • 5.7. Static Wired Address
  • 5.8. WiFi Configuration
  • 5.9. Date Settings
  • 5.10. SSH Key Configuration
• 6. Compilation
  • 6.1. X86
  • 6.2. STM
    • 6.2.1. Install toolchain
    • 6.2.2. Install rootfs
    • 6.2.3. Compile
    • 6.2.4. Execute at startup
• 7. Filesystem
• 8. OceanPulse PCB
• 9. Mounting instructions
• 10. Mechanical
• 11. Sensors
• 12. Communication via MQTT protocol
  • 12.1. PUBLISH and SUBSCRIBE
  • 12.2. Responses and Errors
  • 12.3. Password
  • 12.4. Mosquitto Helper
• 13. Data Storage
  • 13.1. Recover data from Raspberry
  • 13.2. Clear file system
• 14. Configuration Files
  • 14.1. Boards
  • 14.2. General
  • 14.3. Admin Tunnel
  • 14.4. MqttTunnel
  • 14.5. Mqtt access
• 15. Log
• 16. SSH access
• 17. Calibration procedure
  • 17.1. General
  • 17.2. EC
  • 17.3. DO
  • 17.4. pH
  • 17.5. Pixie
• 18. Architecture
  • 18.1. HW/SW Component architecture
  • 18.2. Software Architecture
• 19. Raspberry pin-out
• 20. Serial helper
• 21. Remote tunnel helper
• 22. SD CARD copy
• 23. Experimantal
  • 23.1. Bluetooth
    • 23.1.1. bluetoothd
    • 23.1.2. obexpushd
    • 23.1.3. Note

This project focuses on the development of a marine multisensor system capable of monitoring key parameters including Electrical Conductivity (EC), pH, Oxidation-Reduction Potential (ORP), and pressure. The system is designed to acquire, process, and transmit data to the surface for storage or visualization through a graphical interface.

The OceanPulse system represents a significant advancement in marine/freshwater environmental monitoring, offering real-time data collection and analysis capabilities that are crucial for understanding and preserving our oceans. By integrating multiple sensors into a single, robust platform, we enable comprehensive monitoring of water quality parameters that are essential indicators of marine ecosystem health.

To begin using the OceanPulse system, follow these steps to establish the initial connection:

1. Connect your PC and the OceanPulse device to a router with DHCP enabled using ethernet cables.

2. Power on the OceanPulse device by connecting the USB-C power cable.

3. Wait approximately 1 minute for the system to fully boot up.

4. The OceanPulse will automatically obtain an IP address from your router's DHCP server.

5. You can connect to the device in one of two ways:

   a. Using the hostname:

   ssh [email protected]

   b. Using the IP address (if hostname resolution doesn't work):

   • Find the IP address assigned to OceanPulse from your router's DHCP client list
   • Connect using:

   ssh IDRO@<ip_address>

   In both cases, the default password is IDRO.

To use the OceanPulse Realtime UI, follow these steps:

1. Unzip the ui-Oceanpulse.zip file.
2. Open the Chrome browser on your PC.
3. Drag and drop the ui.html file into the browser.
4. Enter the IP address of the OceanPulse device in the input field (or IDRO.local if you are on the same network and using the hostname).
5. Use port 8181.
6. Click "Connect."
7. The OceanPulse Realtime UI will load, displaying real-time data from the connected sensors.
8. Use the UI to monitor sensor readings, saves, calibrate sensors, and manage device settings.

From OceanPulse version 1.18 the UI is ALSO available at http://<ip_address>:8181/index.html

1. Open the Chrome browser on your PC.
2. Go to http://<ip_address>:8181/index.html
3. Enter the IP address of the OceanPulse device in the input field (or IDRO.local).
4. Use port 8181.
5. Click "Connect."
6. The OceanPulse Realtime UI will load, displaying real-time data from the connected sensors.
7. Use the UI to monitor sensor readings, saves, calibrate sensors, and manage device settings.

Important notes about saving data from the UI:

• The data is temporarily saved in the browser, so you must save it before closing the browser. Do not refresh the page before saving data.
• Once the Save button is pressed, the data is downloaded from the browser and saved in your Downloads folder.

The OceanPulse Realtime UI allows you to calibrate various sensors (DO, EC, PH). Follow the instructions in the "Calibrating Sensors" section of the user manual for detailed steps.

The UI provides real-time graphs and data displays for all connected sensors.

Two button are available:

• Reboot
• Clear (data and logs)

Raspberry Pi OS Lite (32-bit) on Raspberry 4B Raspberry OS

You can directly use the OceanPulse pre-created SD card. In this case, skip the sections up to section 8.0 (OceanPulse PCB).

The Raspberry Pi OS Lite is chosen for its lightweight nature, which is ideal for our headless operation and maximizes system resources for data collection and processing.

A basic knowledge of Linux system is required for this section.

1. Download the Raspberry Pi Imager from https://www.raspberrypi.com/software/
2. Install and launch the Raspberry Pi Imager (this operation can be accomplished on any system that supports the Raspberry Pi Imager)
3. Click "Choose OS" and select "Raspberry Pi OS (32-bit)"
4. Click "Choose Storage" and select your SD card
5. Click "Write" to begin the installation process

Power on the Raspberry Pi and connect it to your router using an Ethernet cable. The Raspberry Pi will automatically obtain a DHCP address. Check your router to find the IP address assigned to the Raspberry Pi.

To access the Raspberry Pi remotely, use SSH with the following command:

ssh pi@<board IP address>

The default password is raspberry.

Next, update the package list and upgrade all installed packages:

sudo apt update && sudo apt full-upgrade

Install the required packages:

sudo apt install libxml2-utils autossh screen libboost-dev mosquitto htop cmake git i2c-tools jq libx11-dev libxkbfile-dev libsecret-1-dev gdbserver avahi-daemon lighttpd

Enable and start the Avahi daemon service:

sudo systemctl enable avahi-daemon
sudo systemctl start avahi-daemon

Disable the Mosquitto service:

sudo systemctl disable mosquitto

For configuration, use:

sudo rpi-config

• Activate i2c and w1
• Configure wifi (optional)
• Set hostname to IDRO
• Activate ssh access

If needed (for some reason the previous operation failed) manual change hostname to IDRO:

Open and change these files using sudo:

/etc/hostname
/etc/hosts

DNS can have problems on the local network and the IDRO.local address may not work. Make sure that the avahi-daemon service is running to enable the DNS resolution of the IDRO.local hostname:

sudo systemctl start avahi-daemon

We suggest forcing the hostname to IDRO: Change the configuration file (/etc/avahi/avahi-daemon.conf) by adding the following parameter:

host-name=IDRO

Add user IDRO:

sudo useradd -m -G sudo,video,netdev,gpio,i2c,input,admin IDRO
sudo passwd IDRO
<IDRO>
sudo passwd
<IDRO>

sudo chmod -R 775 /var/www/html

In this case we suggest to use the same password for IDRO and root.

At the end you will have these users:

usr: IDRO
pwd: IDRO

user: root
pwd: IDRO

Important note:the applications and script are started form root.

To set up a static wired IP address, connect via SSH and use:

sudo nmtui

Follow the steps shown in the images:

Note that after configuration, the Raspberry Pi will only be accessible through the selected address on a wired connection.

WiFi can be configured using either nmtui or raspi-config.

To use raspi-config, run:

sudo raspi-config

Follow the steps shown in the images:

Then, set your SSID and password.

In the file /etc/default/locale, add the following line:

LC_TIME="C.UTF-8"

Create an SSH key and copy it to IDRO:

For Linux users:

ssh-keygen
ssh-copy-id [email protected]

For Windows users you can use putty application.

A advanced knowledge of Linux system and c++ programming language is required for this section.

Clone the OceanPulse repository:

git clone https://github.com/triccyx/OceanPulse

Compilation on X86 host is for debugging purpose

cd OceanPulse
mkdir build
cd build
cmake -DX86=ON -DCMAKE_BUILD_TYPE=Debug -DCMAKE_INSTALL_PREFIX=<your install folder> ..
make install

We will execute a cross-compilation.

From https://github.com/Pro/raspi-toolchain Releases button, download raspi-toolchain.tar.gz

Untar and copy Raspberry toolchain in ./OceanPulse/cross-pi-gcc.

tar -xzvf raspi-toolchain.tar.gz
cp -r raspi-toolchain ./OceanPulse/cross-pi-gcc

Copy from Raspberry the rootfs. Insert the Raspberry SDCARD in the PC and run:

rsync -vR --progress -rl --delete-after --safe-links [email protected]:/{lib,usr,etc/ld.so.conf.d,opt/vc/lib} ./OceanPulse/rootfs

cd OceanPulse
mkdir build
cd build
cmake -DX86=OFF -DCMAKE_BUILD_TYPE=Debug ..
make install
make DeployToBox

Add to /etc/rc.local using sudo.

cd /home/IDRO
./runIdro.sh

+-- home/IDRO
 +-- IDRO
 +-- runidro.sh
 +-- script
 |   +-- idromosquitto.sh
 |   +-- mqtttunnel.sh
 |   +-- mqttwstunnel.sh
 |   +-- wifireconnector.sh
 |   +-- admintunnel.sh
 +-- configuration
 +-- boardconfig.json
 +-- logconfig.json
 +-- mosquittoserver
 +-- idro.conf
 +-- pwd.txt
 +-- log
 +-- archive
 +-- data

The Gerber files for the OceanPulse PCB board version 1.3 are available in the repository. HW folder.

Mounting steps:

• Start with a naked Raspberry Pi. {width=500px}
• Insert the SD card
• Mount two Atlas Scientific i3 InterLink boards over the naked Raspberry Pi. And the small DO/PH/EC boards. Use only the isolated slot (number 1 or 2) {width=500px}
• Mount the OceanPulse PCB over the i3 InterLink boards. {width=500px}
• Connect the STM cable.
• Connect the temperature cables.
• Connect the pressure sensor cable.
• Connect the light meter sensor cable. {width=500px}

Support for Raspberry Pi and HAT Boards The Raspberry Pi and its three HAT boards are supported by a 3D-printed structure (refer to attached photos). This structure is designed to hold the Raspberry Pi vertically, with USB cables running along the enclosure's cylinder. The 3D-printed structure facilitates easy installation and removal of components.

Watertight Enclosure Tube The primary enclosure is an aluminium watertight tube with a diameter of 130 mm and a length of 300 mm (model BR-101409-300 from Bluerobotics). This tube, featuring precision-machined O-ring interfaces, a locking cord, and an anti-rotation feature, is rated for depths up to 950 meters. Each end of the tube is sealed with end caps from Bluerobotics, providing a reliable seal and allowing for the connection of various cables and connectors needed for external sensors.

WetLink Penetrators To route sensor cables from the Raspberry Pi to the exterior, various WetLink penetrators are used (models BR-100870-155 and BR-100870-345). These penetrators are installed on the enclosure's end caps, ensuring a watertight connection for cables leading to the external sealed sensors.

Assembly Component Mounting: The Raspberry Pi and HAT boards are mounted on the 3D-printed support, which is then slid into the watertight tube, fitting snugly. Cable Connections: Sensor cables are routed through the WetLink Penetrators, and secured to the tube's end caps. These penetrators were selected for their ability to maintain a watertight seal, crucial for safe system operation in a marine environment. Sealing and Closing: After closing and tightening the end caps, a vacuum pump is used to create a vacuum inside the enclosure. The pressure is reduced by approximately 15 inHg and monitored for 15-20 minutes to ensure the vacuum remains stable.

{width=500px} {width=500px} {width=500px}

The 3D printer-ready file is in the Mechanics folder.

Note: This table provides an overview of the sensors used in the system, including their names, types, versions (where applicable), and the bus they communicate on.

The communication with external systems is achieved using the MQTT (Message Queuing Telemetry Transport) protocol. This protocol supports two transport methods: WebSocket and TCP (Transmission Control Protocol). Both WebSocket and TCP can be utilized simultaneously for enhanced flexibility and redundancy. MQTT enables efficient, lightweight messaging between the OceanPulse system and external clients or servers. This dual-protocol approach ensures robust connectivity across various network environments and client capabilities.

In simpler terms, MQTT is like a postal service for the OceanPulse box. It helps the box send and receive messages to and from other devices or systems. By using two different ways to send these messages (WebSocket and TCP), we make sure that the OceanPulse box can always stay connected, no matter what kind of network it's on. This means you can easily control and configure the OceanPulse box from anywhere, even if you're not a tech expert.

The box PUBLISH over:

*Additional values are sent only if ShortMessage is false

The box SUBSCRIBE over:

* Available settings: BoxId, TestId,Latitude, Longitude, SamplingTimeInMsec, AutoStart,PublishEqualValues, ShortMessage,TemperatureCorrection, EnableDataWriting

Note: msgid is the msg identifier, it is inserted in the answer. It should be incremental. Can not be 0

The OceanPulse system provides responses and error messages to communicate the status of operations and any issues that may arise during its operation. These messages are crucial for monitoring the system's health, troubleshooting problems, and ensuring proper functionality.

Responses and error messages are published on the MQTT topic <BoxName>/Response, where <BoxName> is the unique identifier for the OceanPulse device. This allows for easy integration with monitoring systems and user interfaces.

The messages are formatted as JSON objects, containing the following fields:

• msgid: A unique identifier for the message, corresponding to the command that triggered the response.
• value: A numeric code indicating the type of response or error.
• timestamp: The date and time when the message was generated, in the format "DD-MM-YYYY_HH:MM:SS.mmm".
• info: Additional information about the response or error (if applicable).
• testId: The current test identifier.
• latitude and longitude: The geographical coordinates of the device.

Available on topics: <BoxName>/Response

Format: {"msgid":<id>,"value":<code>,"timestamp":"22-08-2024_22:03:46.948","info":"","testId":"Test1","latitude":44.4056,"longitude":8.9463}

Note: msgid is the msg identifier, it is inserted in the incoming msg. It should be incremental. . Can not be 0

No password is configured

Some bash commands for test the system from a Linux host system:

Publish commands to the Box:

mosquitto_pub -h <Box ip address>  -t Box1/command/ -m '{"msgid":1,"type":"calibrate","boardsensortype":"EC","value":34,"calibrationtype":"dry"}' -p 1883
mosquitto_pub -h <Box ip address>  -t Box1/command/ -m '{"msgid":1,"type":"start","value":true}' -p 1883

Subscribe to the Box:

mosquitto_sub -h <Box ip address>  -t "Box1/#"  -p 1883

The system uses a FilePublisher class to store sensor data locally. Key features include:

• Data is stored in a "./data" directory
• Each sensor type can have its own file
• Data format: " <sensor_data>"
• Automatically creates the data directory if it doesn't exist
• Appends new data to existing files

To recover the data, you can use the FileZilla application. FileZilla is a free and open-source FTP client that allows you to transfer files between your local computer and a remote server. By connecting to the device running the OceanPulse system, you can navigate to the "./data" directory and download the stored sensor data files to your local machine for further analysis or backup.

Configuration: host:IDRO.local user:root pwd:IDRO Protocol:Sftp folder:/home/IDRO/data

To clear the file system, you can use the FileZilla application to connect to the device and manually delete the files in the "./data" directory. Follow these steps:

1. Open FileZilla and connect to the device using the following configuration:

   • Host: IDRO.local
   • User: root
   • Password: IDRO
   • Protocol: SFTP
   • Folder: /home/IDRO/data

2. Navigate to the "./data" directory and clear files

3. Navigate to the "./archive" directory and clear files

4. Navigate to the "./log" directory and clear files

The OceanPulse system uses configuration files to manage various settings and parameters. These files allow for easy customization and adjustment of the system's behavior without modifying the source code. The main configuration file is located at:

./configuration/boardconfig.json

This JSON file contains settings for individual sensor boards, general system parameters, and MQTT connection details. Below is an overview of the main sections and their key configuration options:

Note: These configuration options define the characteristics and behavior of each sensor board in the system. Ensure each board is properly configured for optimal performance.

Note that all boards have the same admin tunnel configuration.

Note that all boards have the same mqtt tunnel configuration.

There are three connections possible:

local connection on localhost:

Note: These settings are for local MQTT connections on the device itself. The Broker address (127.0.0.1) refers to localhost, meaning the MQTT broker is running on the same device. This configuration is typically used for testing or when all components are on a single machine.

remote connection over LAN:

remote connection via bridge over WAN:

It is possible to test the MQTT connection usign a simple bash command: <MqttTunnelPort>=10071 check in boardconfig.json

mosquitto_sub -h www.saltwatercloud.com -t "#" -p 10071 #Tcp
mosquitto_sub -h www.saltwatercloud.com -t "#" -p 10072 #Websocket

A debug log is prresent in /home/IDRO/log/mylog.log

Date                       Severity      Module Message
16-09-2024_23:03:29.065 | (Error****) | (INOU) | Failed to send single read board:DO

Note that our DNS configuration via avahi-daemon assign the IDRO.local address to the Box. The ssh access can be done in three ways:

1. local:

ssh [email protected]

2. remote over LAN

ssh IDRO@<ip address>

3. remote via bridge over WAN (only if the board is connected to the internet) for maintenance only: You need the ssh-key of the saltwatercloud server.

<AdminPort>=10020 check in boardconfig.json

ssh [email protected] -p <AdminPort>

The calibration procedure for sensors can be initiated and controlled using MQTT messages with the "type":"calibrate" format. Here's a general overview of how to use these messages:

1. Message Structure: The calibration MQTT message should have the following structure:

   {
     "msgid": <unique_message_id>,
     "type": "calibrate",
     "boardsensortype": "<sensor_type>",
     "value": <calibration_value>,
     "calibrationtype": "<calibration_point>"
   }

2. Sensor Types: Replace <sensor_type> with one of the following: "EC", "PH", "DO", "ORP" or "PIXIE".

3. Calibration Points: The "calibrationtype" field can be set to:

   • "dry" for dry calibration (where applicable)
   • "low" for low-point calibration
   • "mid" for mid-point calibration
   • "high" for high-point calibration

4. Example Messages:

   • For EC dry calibration:

{
    "msgid": 1,
    "type": "calibrate",
    "boardsensortype": "EC",
    "value": 0,
    "calibrationtype": "dry"
}

- For pH mid-point (pH 7) calibration:

{
    "msgid": 2,
    "type": "calibrate",
    "boardsensortype": "PH",
    "value": 7,
    "calibrationtype": "mid"
}

5. Publishing Messages: Use mosquitto_pub or another MQTT client to send these messages. For example:

   mosquitto_pub -h <broker_address> -t <box_name>/command/ -m '{"msgid":1,"type":"calibrate","boardsensortype":"EC","value":0,"calibrationtype":"dry"}' -p <port>

Remember to follow the specific calibration procedures for each sensor type as outlined in the subsequent sections, using these MQTT messages to initiate and control the calibration process.

The EC (Electrical Conductivity) sensor calibration involves the following steps:

1. Prepare calibration solutions: Obtain at least two standard solutions with known EC values (12880 μS/cm and 80000 μS/cm). This is the two-point calibration.
2. Clean the sensor: Rinse the EC probe with distilled water and gently dry it.
3. Verify calibration temperature: Ensure the calibration solution kit is at the correct temperature, typically 25C. Refer to the calibration solution kit box for details.
4. Dry calibration: Expose the dry sensor to air and calibrate for 0 μS/cm.
5. Low-point calibration: Submerge the sensor in the low EC standard solution and wait for the reading to stabilize. Press the corresponding button on the UI.
6. High-point calibration: Rinse the sensor, then submerge it in the high EC standard solution and wait for stabilization. Press the corresponding button on the UI.
7. Verify calibration: Test the sensor in a solution with a known EC value to confirm accuracy.

Note: Only the two-point calibration is supported for EC. Single-point calibration is supported from version 1.16.0 onwards.

To calibrate the DO (Dissolved Oxygen) sensor, follow these steps:

1. Set up the calibration environment: Obtain a zero oxygen solution.
2. Clean the sensor: Rinse the DO probe with distilled water and gently dry it.
3. Verify calibration temperature: Ensure the calibration solution kit is at the correct temperature, typically 25C. Refer to the calibration solution kit box for details.
4. Atmospheric calibration: a. Leave the probe exposed to the air. b. Allow the reading to stabilize. c. Press the corresponding button on the UI.
5. Zero calibration: a. Immerse the sensor in a zero oxygen solution. b. Allow the reading to stabilize. c. Press the corresponding button on the UI.
6. Confirm calibration: Test the sensor in a solution with a known DO value or compare it with a recently calibrated DO meter.

The pH sensor calibration procedure typically involves these steps:

1. Prepare buffer solutions: Obtain at least two pH buffer solutions, typically pH 4, 7, and 10.
2. Clean the sensor: Rinse the pH probe with distilled water and dry it gently.
3. Verify calibration temperature: Ensure the calibration solution kit is at the correct temperature, usually 25C. Check on the calibration solution kit box.
4. Select a calibration method.
5. Single-point calibration: a. Use a pH 7 buffer: Immerse the sensor and wait for the reading to stabilize. Press the corresponding button on the UI.
6. Two-point calibration: a. Begin with a pH 7 buffer: Immerse the sensor and wait for the reading to stabilize. Press the corresponding button on the UI. b. Rinse and repeat with either a pH 4 buffer (for acidic range) or a pH 10 buffer (for alkaline range). Press the corresponding button on the UI.
7. Three-point calibration: a. Start with a pH 7 buffer: Immerse the sensor and wait for the reading to stabilize. Press the corresponding button on the UI. b. Rinse and repeat with a pH 4 buffer. c. Rinse and repeat with a pH 10 buffer.
8. Confirm calibration: Test the sensor in a buffer solution not used during the calibration process.

The Pixie fluorometer sensor calibration involves the following steps:

1. Prepare calibration solutions: You'll need a blank solution (typically distilled water) and at least one standard solution with a known fluorescence value.
2. Clean the sensor: Rinse the Pixie probe with distilled water and dry it gently.
3. Dark reading calibration: a. Place the sensor in a completely dark environment (e.g., cover with an opaque material). b. Wait for the reading to stabilize. c. Calibrate for the dark reading (zero point).
4. Blank calibration: a. Immerse the sensor in the blank solution (distilled water). b. Wait for the reading to stabilize. c. Calibrate for the blank reading.
5. Standard solution calibration: a. Rinse the sensor with distilled water. b. Immerse the sensor in the standard solution with known fluorescence. c. Wait for the reading to stabilize. d. Calibrate using the known value of the standard solution.
6. Multi-point calibration (optional): If higher accuracy is required across a wide range of concentrations, repeat step 5 with additional standard solutions of different known concentrations.
7. Temperature compensation: Ensure the meter is set to the correct temperature, as temperature can affect fluorescence readings.
8. Verify calibration: Test the sensor in a solution with a known fluorescence value that wasn't used in the calibration process. Note: The Pixie sensor may have multiple channels. Repeat the calibration process for each channel if necessary, using appropriate standard solutions for each channel's target fluorophore.

The parameters that can be calibrated are for each channel: SGAIN SPGAIN SATTEN

In UML format

@startuml

package "OpenCTD" #LightGray {
 interface i2c
 interface w1
 interface SMA
 i2c - [Atlas_EC]
 i2c - [Atlas_PH]
 i2c - [Atlas_DO]
 SMA - [Atlas_Board]
 w1 - [DS18B20 ]
 component Atlas_Board #LightGreen
 component Atlas_EC #LightBlue
 component Atlas_PH #LightBlue
 component Atlas_DO #LightBlue
    note left of SMA: Connector to probe
}

package "PAM" #LightGray {
 component Pixie_Board #LightBlue
 component Pixie_sensor #LightGreen
 interface Serial
 Serial - [Pixie_Board]
}

package "Core" #LightGray {
 component Raspberry #LightBlue
 component Mosquitto #yellow
 component IDRO #yellow
 interface Mqtt
 Raspberry ..> i2c
 Raspberry ..> Serial
 Mqtt - [Raspberry]
    note left of Mqtt: Mqtt on WebSocket
    note left of Mosquitto: SW
    note left of IDRO: SW main app
}

package "UserInteface" #LightGray {
 component WebApp #yellow
 component AndroidApp #yellow
 WebApp ..> Mqtt
 AndroidApp ..> Mqtt
}
@enduml

The software architecture of the OceanPulse system is designed to be modular, extensible, and efficient. Below is a high-level overview of the main components and their interactions:

@startuml
package "Core" {
[Main Application] as Main
[Sensor Manager] as SensorMgr
[MQTT Client] as MQTTClient
[Data Logger] as Logger
}
package "Sensors" {
[EC Sensor] as EC
[pH Sensor] as pH
[DO Sensor] as DO
[Temperature Sensor] as Temp
[Pressure Sensor] as Pressure
[PIXIE Sensor] as PIXIE
}
package "Communication" {
[MQTT Broker] as MQTTBroker
}
package "Storage" {
[File System] as FileSystem
}
package "External Interfaces" {
[Web Application] as WebApp
[Mobile Application] as MobileApp
}
Main --> SensorMgr : manages
Main --> MQTTClient : uses
Main --> Logger : logs data
SensorMgr --> EC : reads
SensorMgr --> pH : reads
SensorMgr --> DO : reads
SensorMgr --> Temp : reads
SensorMgr --> Pressure : reads
SensorMgr --> PIXIE : reads
MQTTClient <--> MQTTBroker : publishes/subscribes
Logger --> FileSystem : writes
MQTTBroker <--> WebApp : communicates
MQTTBroker <--> MobileApp: communicates
@enduml

screen /dev/ttyUSB0 115200

Check remote tunnel status:

cd helper
./checktunnel.sh

If you have the image file, you can copy it to the SDCARD using the following command on Linux:

dd if=./oceanpulse.img of=/dev/sda status=progress

Bluetooth can be used for Wi-Fi configuration; however, this feature is not yet implemented.

Prerequisites

sudo apt-get install bluez-alsa-utils
sudo apt install obexpushd

Check in file /etc/bluetooth/main.conf DiscoverableTimeout = 0 PairableTimeout = 0

Check in file /etc/systemd/system/dbus-org.bluez.service ExecStart=/usr/lib/bluetooth/bluetoothd --noplugin=sap -C

add in file /etc/systemd/system/obexpushd.service

[Unit]
Description=OBEX Push Daemon
After=bluetooth.service
Requires=bluetooth.service

[Service]
ExecStart=/usr/bin/obexpushd -B -o /home/IDRO/ExtConfig -n
Restart=always

[Install]
WantedBy=multi-user.target

sudo systemctl enable obexpushd
sudo systemctl start obexpushd

https://www.raspberrypi.org/forums/viewtopic.php?p=961827#p961827 https://www.kynetics.com/docs/2018/pairing_agents_bluez/ https://forums.raspberrypi.com/viewtopic.php?t=146328