Jump to content

SENSBLUE ATLAS/Datasheet: Difference between revisions

From ATRONIA Wiki
No edit summary
No edit summary
Tag: Manual revert
 
(145 intermediate revisions by the same user not shown)
Line 1: Line 1:
[[File:SENSBLUE-ATLAS-Gateway.png|center|frameless|360x360px]]
{{DISPLAYTITLE:Datasheet}}
<div class="buy-now-container">
<span class="button-buy-now">[https://atronia.eu/product/sensblue-atlas/ Buy Now]</span>
</div>


[[File:SENSBLUE-ATLAS-Gateway.png|center|frameless|397x397px]]
== '''Datasheet''' ==
== '''Datasheet''' ==


=== 2. Table of SENSBLUE ATLAS Reference ID Model Number ===
=== 1. Table of SENSBLUE ATLAS Reference ID Model Number ===
{| class="wikitable"
{| class="wikitable"
|
|'''Reference Number'''
|
|'''Name'''
|
|'''Version'''
|
|'''RAM'''
|
|'''Modem'''
|
|-
|PA000000102
|ATLAS IoT SBC V1 CM4. 2GB M2.0 M1 PB0
|V1
|2GB
|Yes
|-
|-
|Paxxxxxxxx
|PA000000103
|
|ATLAS IoT SBC V1 CM4. 2GB M2.0 M0 PB0
|
|V1
|
|2GB
|
|Yes
|
|-
|-
|PAxxxxxxxx
|PA000000104
|
|ATLAS IoT SBC V1 CM4. 4GB M2.0 M1 PB0
|
|V1
|
|4GB
|
|No
|
|}
|}


=== 3. General Description ===
=== 2. General Description ===
SENSBLUE ATLAS is a single board computer that connects sensors and assets, runs control logic and ships to production without platform changes.
SENSBLUE ATLAS is a single board computer that connects sensors and assets, runs control logic and ships to production without platform changes.


Designed for industrial teams who need one dependable path from experiments to operations.
Designed for industrial teams who need one dependable path from experiments to operations.


==== 3.1 Key Features ====
==== 2.1 Key Features ====
'''Processor:'''
'''Processor:'''


Line 39: Line 46:
'''I/O:'''
'''I/O:'''


* 12 DO (Digital Outputs)
* 12 DIO (8 Digital Outputs and 4 Digital Input)
* 6 AI (Analog Inputs)
* 6 AIO (4 Analog Inputs and 2 Analog Outputs)
* 2 relays
* 2 relays


Line 63: Line 70:
* Other versions under request.
* Other versions under request.


=== 4. Hardware Specifications ===
=== 3. Hardware Specifications ===
{| class="wikitable tech-table" style="width: 100%;"
{| class="wikitable tech-table" style="width: 100%;"
!style="width: 50%;"|'''Parameter'''
!style="width: 50%;"|'''Parameter'''
Line 78: Line 85:
|-
|-
|RAM
|RAM
|4GB  LPDDR4
|2GB, 4GB  LPDDR4
|-
|-
|Storage
|Storage
Line 96: Line 103:
|}
|}


=== 5. Power ===
=== 4. Power ===
{| class="wikitable tech-table" style="width: 100%;"
{| class="wikitable tech-table" style="width: 100%;"
!style="width: 50%;"|'''Parameter'''
!style="width: 50%;"|'''Parameter'''
Line 123: Line 130:
|}
|}


=== 6. Digital Inputs ===
=== 5. Digital Inputs ===
{| class="wikitable tech-table" style="width: 100%;"
{| class="wikitable tech-table" style="width: 100%;"
!style="width: 50%;"|'''Parameter'''
!style="width: 50%;"|'''Parameter'''
Line 162: Line 169:
|}
|}


=== 7. Digital Outputs (Relay) ===
==== 5.1 Wiring ====
[[File:DIG IN.svg|center|frameless|500x500px]]
 
=== 6. Digital Outputs (Relay) ===
{| class="wikitable tech-table" style="width: 100%;"
{| class="wikitable tech-table" style="width: 100%;"
!style="width: 50%;"|'''Parameter'''
!style="width: 50%;"|'''Parameter'''
Line 186: Line 196:
|}
|}


=== 8. Digital Outputs (Transistor/ SSR) ===
==== 6.1 Wiring ====
[[File:RELAY.svg|center|frameless|500x500px]]
 
=== 7. Digital Outputs (Transistor/ SSR) ===
{| class="wikitable tech-table"
{| class="wikitable tech-table"
!style="width: 50%;"|'''Parameter'''
!style="width: 50%;"|'''Parameter'''
Line 210: Line 223:
|}
|}


=== 9. Analog Inputs ===
==== 7.1 Wiring ====
[[File:DIG OUT.svg|center|frameless|500x500px]]
 
=== 8. Analog Inputs ===
{| class="wikitable tech-table"
{| class="wikitable tech-table"
!style="width: 50%;"|'''Parameter'''
!style="width: 50%;"|'''Parameter'''
Line 255: Line 271:
|}
|}


=== 10. Analog Outputs ===
==== 8.1 Wiring ====
[[File:ANL IN.svg|center|frameless|500x500px]]
 
=== 9. Analog Outputs ===
{| class="wikitable tech-table"
{| class="wikitable tech-table"
!style="width: 50%;"|'''Parameter'''
!style="width: 50%;"|'''Parameter'''
Line 285: Line 304:
|}
|}


=== 11. Communication Interfaces ===
==== 9.1 Wiring ====
[[File:ANL OUT.svg|center|frameless|500x500px]]


==== 11.1 Ethernet ====
=== 10. Communication Interfaces ===
 
==== 10.1 Ethernet ====
{| class="wikitable tech-table"
{| class="wikitable tech-table"
! style="width: 50%;" | '''Parameter'''
! style="width: 50%;" | '''Parameter'''
Line 305: Line 327:
|}
|}


==== 11.2 RS-485 ====
==== 10.2 RS-485 ====
{| class="wikitable tech-table"
{| class="wikitable tech-table"
!style="width: 50%;"|'''Parameter'''
!style="width: 50%;"|'''Parameter'''
Line 323: Line 345:
|}
|}


==== 11.3 USB ====
===== 10.2.1 Wiring =====
[[File:RS485.svg|center|frameless|500x500px]]
 
==== 10.3 USB ====
{| class="wikitable tech-table"
{| class="wikitable tech-table"
!style="width: 50%;"|'''Parameter'''
!style="width: 50%;"|'''Parameter'''
Line 344: Line 369:
|}
|}


==== 11.4 HDMI ====
==== 10.4 HDMI ====
{| class="wikitable tech-table"
{| class="wikitable tech-table"
!style="width: 50%;"|'''Parameter'''
!style="width: 50%;"|'''Parameter'''
Line 359: Line 384:
|}
|}


=== 12. RF Communications ===
=== 11. RF Communications ===
{| class="wikitable tech-table"
{| class="wikitable tech-table"
!style="width: 50%;"|'''Technology'''  
!style="width: 50%;"|'''Technology'''  
Line 377: Line 402:
|}
|}


==== 12.1  Antenna Connectors ====
==== 11.1  Antenna Connectors ====
{| class="wikitable tech-table"
{| class="wikitable tech-table"
!style="width: 50%;"|'''Connector'''  
!style="width: 50%;"|'''Connector'''  
Line 389: Line 414:
|}
|}


=== 13. Local Peripherals ===
=== 12. Local Peripherals ===
{| class="wikitable tech-table"
{| class="wikitable tech-table"
!style="width: 50%;"|'''Peripheral'''
!style="width: 50%;"|'''Peripheral'''
Line 407: Line 432:
|}
|}


=== 14. HDMI ===
=== 13. HDMI ===


==== 14. 1 Display ====
==== 13. 1 Display ====
{| class="wikitable tech-table"
{| class="wikitable tech-table"
!style="width: 50%;"|'''Parameter'''
!style="width: 50%;"|'''Parameter'''
Line 433: Line 458:
|}
|}


==== 14. 2 Joystick ====
==== 13. 2 Joystick ====
{| class="wikitable tech-table"
{| class="wikitable tech-table"
!style="width: 50%;"|'''Parameter'''
!style="width: 50%;"|'''Parameter'''
Line 448: Line 473:
|}
|}


=== 15. Mechanical ===
=== 14. Mechanical ===
{| class="wikitable tech-table"
{| class="wikitable tech-table"
!style="width: 50%;"|'''Parameter'''
!style="width: 50%;"|'''Parameter'''
Line 466: Line 491:
|}
|}


=== 16. Environmental ===
=== 15. Environmental ===
{| class="wikitable tech-table"
{| class="wikitable tech-table"
!'''Parameter'''
!'''Parameter'''
Line 487: Line 512:
|}
|}


=== 17. Certifications ===
=== 16. Certifications ===
{| class="wikitable tech-table"
{| class="wikitable tech-table"
!style="width: 50%;"|'''Certification'''
!style="width: 50%;"|'''Certification'''
Line 505: Line 530:
|}
|}


=== 18. Connectivity ===
=== 17. Connectivity ===
{| class="wikitable tech-table"
{| class="wikitable tech-table"
!style="width: 50%;"|'''Parameter'''
!style="width: 50%;"|'''Parameter'''
Line 529: Line 554:
|}
|}


=== 19. Expansion ===
=== 18. Expansion ===
{| class="wikitable tech-table"
{| class="wikitable tech-table"
!style="width: 50%;"|'''Feature'''  
!style="width: 50%;"|'''Feature'''  
Line 553: Line 578:
|}
|}


=== 20. Mechanical Drawings ===
=== 19. External Interfaces ===


==== Front View ====
==== Front View ====
Line 562: Line 587:
[[File:Atlas bottomview.png|center|frameless|590x590px]]
[[File:Atlas bottomview.png|center|frameless|590x590px]]


=== 20. Pinouts ===


==== Top View ====
==== Top View ====
Line 569: Line 597:
'''Raspian'''
'''Raspian'''


Debian GNU/Linux 13 (trixie) Version 13.2 Linux atlas 6.12.47 +rpt-rpi-v8 #1 SMP PREEMPT
Debian GNU/Linux 13 (trixie) Version 13.2 Linux atlas 6.12.47+rpt-rpi-v8 #1 SMP PREEMPT


Debian 1 :6.12.47-1 +rpt1 (2025-09-16) aarch64 GNU/Linux.
Debian 1:6.12.62-1+rpt1 (2025-09-16) aarch64 GNU/Linux.


=== 22. Network Information ===
=== 22. Network Information ===
There is three ways to connect to the device. IP and state of the connection be checked on the LCD Network Interface.
There are three ways to connect to the device. The IP and connection status can be checked on the LCD by cycling to the Network screen.
 
==== 22.1 ETH1 ====
By default, the ETH1 port has the following configuration:
 
* Network interface: eth0
* Connection type: DHCP client.
* IP Address: Dynamic IP address provided by an external DHCP server.


==== 22.1 Eth1 (ethO) ====
==== 22.2 ETH2 ====
Client dynamic IP obtained by DHCP server.
By default, the ETH2 port has the following configuration:


==== 22.2 Eth2 (eth1) ====
* Network interface: eth1
Static IP: '''93.48.86.253'''
* Connection type: Static IP
* IP Address: 93.48.86.253


==== 22.3 Access Point (wlanO) ====
==== 22.3 Access Point ====
IP: '''192.168.30.1'''
By default, ATLAS provides an Access Point configured with the following settings:
 
* Network interface: wlan0
* SSID: '''atlas-<SERIAL_NUMBER>-AP'''
* Password: atlas_2025!
* Connection type: DHCP Server
* IP Address: 192.168.30.1


=== 23. Software Information ===
=== 23. Software Information ===
Line 591: Line 633:
|'''Grafana'''
|'''Grafana'''
|'''lnfluxDB'''
|'''lnfluxDB'''
|'''Operating System'''
|-
|-
|Version
|'''Version'''
|4.1.4
|4.1.4
|12.3.1
|12.3.1
|2.8.0
|2.8.0
|13 (Trixie)
|-
|-
|Port
|'''Port'''
|1880
|1880
|3000
|3000
|8086
|8086
|22
|-
|-
|State
|'''State'''
|Clean
|Clean
|Clean
|Clean
|Clean
|Clean
|N/A
|-
|-
|Authentication
|'''Authentication'''
|None
|None
|User/Pass (admin/admin)
|'''User:''' admin
|Not defined, configured on first time interface login.
'''Pass:''' admin
|Not defined, configured on first time interface login.
|'''User:''' pi
'''Pass:''' atlas2026
|-
|-
|GUI on
|'''GUI'''
|http://<device-ip>:1880
|http://<device-ip>:1880
|http://<device-ip>:3000
|http://<device-ip>:3000
|http://<device-ip>:8086
|http://<device-ip>:8086
|N/A
|}
|}


=== 24. MQTT Broker ===
=== 24. Included Software Stack ===
port: 1883
<br>
[[File:AtlasCode.svg|center|frameless|583x583px]]


address: AP-> 192.168.30.1
<br>


Eth1: '''93.48.86.253'''
=== 25. Software Stack and IPC Architecture ===
<br>
[[File:Hardware Peripherals Library Architecture.svg|center|frameless|1934x1934px]]


user: < not needed>
=== 26. Related Products ===
 
{| class="wikitable"
login <not needed>
|'''PA'''
 
|'''Name'''
=== 25. Relay Outputs Actor ===
|'''Requirements'''
 
==== 25.1 App Interfacing ====
User App interface and functionalities exposed to the open part of the MQTT broker. Simplified interface to configure and obtain peripherals data. Connecting to the broker for this Area requires no credentials.
 
===== 25.1.1 Set/reset digital output pin/pins state =====
Both relays '''default''' state is '''open'''.
 
Req-Topic: relayOutputs/config/in
 
<syntaxhighlight lang="json">
{
  "id": "<TIMESTAMP>",
  "origin": "APP",
  "task": {
    "taskParams": {
      "D01": {
        "state": "open"
      },
      "D02": {
        "state": "open"
      }
    }
  }
}
</syntaxhighlight>Reply-Topic: relayOutputs/config/out
 
<syntaxhighlight lang="json">{
  "id": "<TIMESTAMP>",
  "origin": "APP",
  "task": {
    "taskResult": {
      "D01": {
        "success": true,
        "state": "open"
      },
      "D02": {
        "success": true,
        "state": "open"
      }
    }
  }
}</syntaxhighlight>
 
===== 25.1.2 Get all relays state =====
Req-Topic: relayOutputs/runtime/in<syntaxhighlight lang="json">
{
  "id": "<TIMESTAMP>",
  "origin": "APP",
  "task": {
    "action": "READ"
  }
}
</syntaxhighlight>Reply-Topic: relayOutputs/runtime/out <syntaxhighlight lang="json">
{
  "id": "<TIMESTAMP>",
  "origin": "APP",
  "task": {
    "taskResult": {
      "D01": {
        "success": true,
        "state": "open"
      },
      "D02": {
        "success": true,
        "state": "close"
      }
    }
  }
}
</syntaxhighlight>
 
===== 25.1.3 Set all relays state =====
Req-Topic: relayOutputs/runtime/in<syntaxhighlight lang="json">
{
  "id": "<TIMESTAMP>",
  "origin": "APP",
  "task": {
    "action": "SET",
    "taskParams": {
      "D01": {
        "state": "open"
      },
      "D02": {
        "state": "close"
      }
    }
  }
}
</syntaxhighlight>Reply-Topic: relayOutputs/runtime/out<syntaxhighlight lang="json">
{
  "id": "<TIMESTAMP>",
  "origin": "APP",
  "task": {
    "taskResult": {
      "D01": {
        "success": true,
        "state": "open"
      },
      "D02": {
        "success": true,
        "state": "close"
      }
    }
  }
}
</syntaxhighlight>
 
=== 26. RTC Actor ===
 
==== 26.1 App Interfacing ====
User App interface and functionalities exposed to the open part of the MQTT broker. Simplified interface to configure and obtain peripherals data. Connecting to the broker for this Area requires no credencials.
 
===== 26.1.1 Set timer/alarm interruption =====
'''mode:''' Timer, alarm or none.
 
'''alarmSet:''' Date and time for alarm interruption (No effect if mode is timer or none).
 
'''timerSetSeconds:''' Period in seconds for timer interruption (No effect if mode is alarm or none).
 
Req-Topic: clock/config/in<syntaxhighlight lang="json">
{
  "id": "<TIMESTAMP>",
  "origin": "APP",
  "task": {
    "taskParams": {
      "CLOCK_SET_MODE": {
        "mode": "timer",
        "alarmSet": "[timestamp epoch ms]",
        "timerSetSeconds": "<INT>"
      }
    }
  }
}
</syntaxhighlight>Req-Topic: clock/config/out<syntaxhighlight lang="json">
{
  "id": "<TIMESTAMP>",
  "origin": "APP",
  "task": {
    "taskResult": {
      "success": true,
      "CLOCK_SET_MODE": {
        "mode": "timer",
        "alarmSet": "[timestamp epoch ms]",
        "timerSetSeconds": "<INT>"
      }
    }
  }
}
</syntaxhighlight>
 
===== 26.1.2 Toggle RTC sync logic (described below) =====
'''tcState:''' State of the synchronization logic of the RTC, this value is '''non-persistent''' so every-time a reboot happens the value return to default (by default the value is '''ON''')
 
Req-Topic: clock/config/in<syntaxhighlight lang="json">
{
  "id": "<TIMESTAMP>",
  "origin": "APP",
  "task": {
    "action": "TOGGLE"
  }
}
</syntaxhighlight>Req-Topic: clock/config/out<syntaxhighlight lang="json">
{
  "id": "<TIMESTAMP>",
  "origin": "APP",
  "task": {
    "taskResult": {
      "success": true,
      "rtcState": "OFF"
    }
  }
}
 
</syntaxhighlight>
 
===== 26.1.3 Read clock configs =====
'''mode:''' Timer, alarm or none.
 
'''alarmSet:''' Date and time for alarm interruption (No effect if mode is timer or none).
 
'''timerSetSeconds:''' Period in seconds for timer interruption (No effect if mode is alarm or none).
 
'''rtcState:''' Current state of the synchronization logic of the RTC.
 
Req-Topic: clock/config/in<syntaxhighlight lang="json">
{
  "id": "<TIMESTAMP>",
  "origin": "APP",
  "task": {
    "action": "READ"
  }
}
 
</syntaxhighlight>Reply-Topic: clock/config/out<syntaxhighlight lang="json">
{
  "id": "<TIMESTAMP>",
  "origin": "APP",
  "task": {
    "taskResult": {
      "success": true,
      "CLOCK_CONFIGS": {
        "mode": "timer",
        "alarmSet": "[timestamp epoch ms]",
        "timerSetSeconds": "<INT>",
        "rtcState": "ON"
      }
    }
  }
}
 
</syntaxhighlight>
 
===== 26.1.4 Read clock =====
Req-Topic: clock/runtime/in <syntaxhighlight lang="json">
{
  "id": "<TIMESTAMP>",
  "origin": "APP",
  "task": {
    "taskResult": {
      "success": true,
      "timestamp": "[timestamp epoch ms]"
    }
  }
}
 
</syntaxhighlight>
 
==== 26.2 Synchronization loop flowchart (every 30 seconds) ====
 
 
'''RTC Actor - Overview'''
[[File:RTCActor Overview.svg|center|frameless|774x774px]]
 
=== 27. Core System Health Actor ===
 
==== 27.1 App Interfacing ====
User App interface and functionalities exposed to the open part of the MQTT broker.
 
This interface allows any external App to receive system-level metrics such as CPU load, RAM usage, disk usage, temperature, core frequency, system throttle status and uptime. No credentials are required to subscribe to this topic. The System Health Actor does not receive commands. It is fully autonomous and publishes its metrics every 1 second.
 
==== 27.2 Runtime Data ====
'''Topic: systemHea l th/runtime/ out'''
 
Publish rate: '''1 Hz''' (one message per second, clock-jump safe)
 
===== 27.2.1 Metrics Provided =====
{| class="wikitable tech-table"
!'''Key'''
!'''Description'''
!'''Unit'''
|-
|-
|cpu_percent
|PA000000074
|Current  CPU load
|[[SENSBLUE MONARCH|'''<u>SENSBLUE MONARCH Gateway</u>''']]
|%
|
|-
|-
|cpu_tempC
|}
|CPU  temperature read from Linux thermal zones
{{SimilarProductsTable}}
|ºC
 
=== 27. Accessories ===
{| class="wikitable"
|'''PA'''
|'''Name'''
|'''Requirements'''
|-
|-
|cpu0_freq
|
|CPU Core O current  frequency
|
|Hz
|
|-
|-
|cpul_freq
|
|CPU  Core 1 current frequency
|
|Hz
|
|-
|-
|cpu2_freq
|
|CPU Core 2 current frequency
|
|Hz
|
|-
|-
|cpu3_freq
|
|CPU  Core 3 current frequency
|
|Hz
|
|-
|-
|cpu0_throttle
|
|System  throttle status register
|
|Hex
|
|}
 
=== 28. Document History ===
{| class="wikitable"
|'''Version'''
|'''Description'''
|'''Date'''
|-
|-
|ram_percent
|SBADATAv0.1
|RAM usage
|First version of SENSBLUE ATLAS Datasheet
|%
|11/03/2026
|-
|-
|disk_percent
|
|Disk  usage for filesystem root /
|
|%
|
|-
|-
|uptime_sec
|
|Time  since last reboot
|
|seconds
|
|}
|}
=== 29. SENSBLUE ATLAS in-the-field ===
[IMAGE PLACEHOLDER]

Latest revision as of 11:03, 27 August 2026

Datasheet

1. Table of SENSBLUE ATLAS Reference ID Model Number

Reference Number Name Version RAM Modem
PA000000102 ATLAS IoT SBC V1 CM4. 2GB M2.0 M1 PB0 V1 2GB Yes
PA000000103 ATLAS IoT SBC V1 CM4. 2GB M2.0 M0 PB0 V1 2GB Yes
PA000000104 ATLAS IoT SBC V1 CM4. 4GB M2.0 M1 PB0 V1 4GB No

2. General Description

SENSBLUE ATLAS is a single board computer that connects sensors and assets, runs control logic and ships to production without platform changes.

Designed for industrial teams who need one dependable path from experiments to operations.

2.1 Key Features

Processor:

  • Raspberry Pi CM4 (quad-core Cortex-A72)

I/O:

  • 12 DIO (8 Digital Outputs and 4 Digital Input)
  • 6 AIO (4 Analog Inputs and 2 Analog Outputs)
  • 2 relays

Industrial Bus:

  • RS-485
  • CAN
  • 2× Ethernet port (Independently managed)

Communication:

  • Integrated LTE
  • Wi-Fi
  • BLE
  • USB

Interface & Services:

  • 1.47″ IPS TFT display + joystick for local setup and feedback.
  • Includes 1 GB of data (up to 500 MB LTE + 500 MB DB storage) via sensblue.cloud — no external SIM required.
  • EU-hosted servers, TLS, weekly backups, VPN on request.
  • Other versions under request.

3. Hardware Specifications

Parameter Specification
Platform Raspberry Pi Compute Module 4 (CM4)
Processor Broadcom BCM2711 Quad-core Cortex-A72 (ARM v8)
CPU Frequency 1.5 GHz
RAM 2GB, 4GB LPDDR4
Storage 32 GB eMMC
Selected Variant CM4102032-4 GB RAM/ 32 GB eMMC / Wi-Fi / BLE
PCle 1 x PCle Gen 2.0 (1 lane)
HDMI 1 interfaces
USB 2 x USB 2.0

4. Power

Parameter Specification
Input voltage 12-24 VDC ± 5%
Reverse polarity protection Yes
Overcurrent protection Resettable PTC fuse
Surge protection TVS clamp for transient events
Isolation No isolation
Typical consumption < 15 W
Maximum consumption 25 W (all peripherals active)

5. Digital Inputs

Parameter Specification
Channels 4
Input voltage 0-24 VDC
Logic LOW Acording to EN 61131-2 Type I and Ill
Logic HIGH Acording to EN 61131-2 Type I and Ill
Input type Sourcing (PNP)
Input current Acording to EN 61131-2 Type I and Ill
Isolation Funcional Safety Gavanic isolation
Isolation Voltage Functional isolation between channels on the field side +- 60V
Isolation Voltage DIN VDE V 0884-11 Maximum working isolation voltage 400V RMS
Isolation Voltage DIN VDE V 0884-11 Maximum surge isolation voltage 1 kV RMS
Special feature Can be used as fast inputs until 100Hz

5.1 Wiring

6. Digital Outputs (Relay)

Parameter Specification
Channels 2
Type Mechanical relay
Switching capacity 2 A@ 30 VDC
Isolation 1000 VAC galvanic isolation
Lifetime (nominal load) ≥ 100,000 cycles
Lifetime (no load) ≥ 100,000,000 cycles

6.1 Wiring

7. Digital Outputs (Transistor/ SSR)

Parameter Specification
Channels 8
Type PNP (sourcing) SSR
Maximum current 300 mA per channel
Maximum voltage 24 VDC
Isolation Funcional Safety Gavanic isolation
Isolation Voltage DIN VDE V 0884-17 Maximum transient isolation voltage 1 kV RMS

7.1 Wiring

8. Analog Inputs

Parameter Specification
Channels 4
Mode Voltage or current configurable per channel
Voltage range 0-10 V
Current range 0/4-20 mA
ADC resolution 16 bits
ADC Sample Rate 32 samples/sec
Accuracy ≤ ±1.0% FSR
Input impedance (voltage) > 100 kΩ
Input impedance (current) 100 Ω
Protection TVS + analog filtering
Sampling rate ≥ 10 Hz per channel
Isolation Funcional Safety Gavanic isolation
Isolation Voltage Maximum transient isolation voltage 1 kV RMS

8.1 Wiring

9. Analog Outputs

Parameter Specification
Channels 2
Output type Current
Range 0-20 mA
Optional range 4-20 mA (software configurable)
Resolution 12
Accuracy ≤ ±1.0% FSR
Isolation Funcional Safety Gavanic isolation
Isolation Voltage Maximum transient isolation voltage 1 kV RMS

9.1 Wiring

10. Communication Interfaces

10.1 Ethernet

Parameter Specification
Ports 2 x RJ45
Port 1 10/100 Mbps
Port 2 0/100/1000 Mbps (native CM4)
Indicators Link + Activity LEDs

10.2 RS-485

Parameter Specification
Mode Half-duplex
Control TX_EN line
Protocol Transparent/ any
Isolation None
10.2.1 Wiring

10.3 USB

Parameter Specification
Ports 2
Type USB-A
Standard USB 2.0 Host
Maximum current 400 mA per port
Protection Overcurrent protection

10.4 HDMI

Parameter Specification
Ports 1
Connector HDMI full-size
Maximum resolution Depends on CM4 and OS

11. RF Communications

Technology Specification
Wi-Fi Integrated in CM4
BLE Integrated in CM4
LTE M.2 NGFF modem SIM7600G
SIM External access

11.1  Antenna Connectors

Connector Usage
RP-SMA Wi-Fi / BLE
SMA LTE

12. Local Peripherals

Peripheral Description
Temperature sensor Internal board temperature monitoring
Non-volatile memory Persistent storage
Security IC Microchip ATECC608A
RTC Real Time Clock with battery backup

13. HDMI

13. 1 Display

Parameter Specification 
Type IPS TFT LCD
Interface SPI
Size 1.47"
Resolution ≥ 172 X 320
Backlight LED
Mounting Front mounted with transparent window

13. 2 Joystick

Parameter Specification 
Positions 5 (Up/ Down/ Left/ Right/ Enter)
Type Mechanical tactile switch
Interface GPIO Expander

14. Mechanical

Parameter Specification 
Mounting DIN rail (EN 60715)
Enclosure MAT0091092 (same as iSense / iCee)
Protection rating IP20
Mounting method DIN rail snap-fit

15. Environmental

Parameter Specification 
Operating temperature -10 °C to +60 °C
Storage temperature -20 °C to +80 °C
Humidity 5-95% non-condensing
Vibration IEC 60068-2-6
Shock IEC 60068-2-27

16. Certifications

Certification Standard  
CE Yes
EMC 2014/30/EU
Radio 2014/53/EU (RED)
Ro HS 2011/65/EU

17. Connectivity

Parameter Specification  
Connector type Pluggable System Terminal Block
Pitch 3.5 mm
Layout Dual-row
Identification Side panel silk screen
Fixation Mechanical locking or spring clamp
Protection Mechanical reverse insertion protection

18. Expansion

Feature Description 
Piggyback area Reserved PCB area
Compatibility Fully compatible with existing FW
Power rails available Vin, 5 V, 3.3 V
Interfaces available 12C, SPI, UART, GPIO
External 1/0 lines 32 lines routed to external connectors
Storage expansion M.2 NVMe SSD connector

19. External Interfaces

Front View


Bottom View


20. Pinouts

Top View

21. System Type

Raspian

Debian GNU/Linux 13 (trixie) Version 13.2 Linux atlas 6.12.47+rpt-rpi-v8 #1 SMP PREEMPT

Debian 1:6.12.62-1+rpt1 (2025-09-16) aarch64 GNU/Linux.

22. Network Information

There are three ways to connect to the device. The IP and connection status can be checked on the LCD by cycling to the Network screen.

22.1 ETH1

By default, the ETH1 port has the following configuration:

  • Network interface: eth0
  • Connection type: DHCP client.
  • IP Address: Dynamic IP address provided by an external DHCP server.

22.2 ETH2

By default, the ETH2 port has the following configuration:

  • Network interface: eth1
  • Connection type: Static IP
  • IP Address: 93.48.86.253

22.3 Access Point

By default, ATLAS provides an Access Point configured with the following settings:

  • Network interface: wlan0
  • SSID: atlas-<SERIAL_NUMBER>-AP
  • Password: atlas_2025!
  • Connection type: DHCP Server
  • IP Address: 192.168.30.1

23. Software Information

Node-Red Grafana lnfluxDB Operating System
Version 4.1.4 12.3.1 2.8.0 13 (Trixie)
Port 1880 3000 8086 22
State Clean Clean Clean N/A
Authentication None User: admin

Pass: admin

Not defined, configured on first time interface login. User: pi

Pass: atlas2026

GUI http://<device-ip>:1880 http://<device-ip>:3000 http://<device-ip>:8086 N/A

24. Included Software Stack



25. Software Stack and IPC Architecture


PA Name Requirements
PA000000074 SENSBLUE MONARCH Gateway
Name Firmware v. Requirements
PA000000065 SENSBLUE RS-485 Dissolved Oxygen Probe AT-SB-PROBE-DO-P-C1, w/ 15m cable w/connector
PA000000085 SENSBLUE RS-485 Dissolved Oxygen Probe AT-SB-PROBE-DO-T-C1, w/ 15m cable w/connector 10.70
PA000000091 SENSBLUE RS-485 Dissolved CO2 Sensor Probe AT-SB-PROBE-CO2-P-5000-C1, w/ 15m cable w/connector
PA000000086 SENSBLUE RS-485 Low Conductivity Probe AT-SB-PROBE-LC-P-C1, w/ 15m cable w/connector 10.70
PA000000087 SENSBLUE RS-485 Medium Conductivity Probe AT-SB-PROBE-MC-P-C1, w/ 15m cable w/connector 10.70
PA000000068 SENSBLUE RS-485 High Conductivity Probe AT-SB-PROBE-HC-P-C1, w/ 15m cable w/connector 10.70
PA000000089 SENSBLUE RS-485 Salinity/Conductivity/TDS Probe AT-SB-PROBE-S-P-C1, w/ 15m cable w/connector
PA000000067 SENSBLUE RS-485 pH Probe AT-SB-PROBE-pH-P, w/ 15m cable w/conector 10.70
PA000000088 SENSBLUE RS-485 ORP Probe POM AT-SB-PROBE-ORP-P, w/ 15m cable w/conector
PA000000069 SENSBLUE RS-485 Nitrates (NO3) Probe AT-SB-PROBE-NO3-P, w/ 15m cable w/connector 10.70
PA000000090 SENSBLUE RS-485 Ammonia Nitrogen (NH4-N) Sensor Probe AT-SB-PROBE-NH4-P-C1, w/ 15m cable w/connector
PA000000066 SENSBLUE RS-485 Turbidity Probe AT-SB-PROBE-T-P, w/ 15m cable w/connector 10.70
PA000000073 SENSBLUE RS-485 Multiparameter Probe AT-SB-PROBE-MP-P-C1, w/ 15m cable w/connector 10.71

27. Accessories

PA Name Requirements

28. Document History

Version Description Date
SBADATAv0.1 First version of SENSBLUE ATLAS Datasheet 11/03/2026

29. SENSBLUE ATLAS in-the-field

[IMAGE PLACEHOLDER]