SENSBLUE ATLAS: Difference between revisions

== '''Datasheet''' ==

{| class="wikitable"

|

|}

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.

'''Processor:'''

* Other versions under request.

{| class="wikitable tech-table" style="width: 100%;"

!style="width: 50%;"|'''Parameter'''

|}

{| class="wikitable tech-table" style="width: 100%;"

!style="width: 50%;"|'''Parameter'''

|}

{| class="wikitable tech-table" style="width: 100%;"

!style="width: 50%;"|'''Parameter'''

|}

[[File:DIG IN.svg|center|frameless|500x500px]]

{| class="wikitable tech-table" style="width: 100%;"

!style="width: 50%;"|'''Parameter'''

|}

[[File:RELAY.svg|center|frameless|500x500px]]

{| class="wikitable tech-table"

!style="width: 50%;"|'''Parameter'''

|}

[[File:DIG OUT.svg|center|frameless|500x500px]]

{| class="wikitable tech-table"

!style="width: 50%;"|'''Parameter'''

|}

[[File:ANL IN.svg|center|frameless|500x500px]]

{| class="wikitable tech-table"

!style="width: 50%;"|'''Parameter'''

|}

[[File:ANL OUT.svg|center|frameless|500x500px]]

{| class="wikitable tech-table"

! style="width: 50%;" | '''Parameter'''

|}

{| class="wikitable tech-table"

!style="width: 50%;"|'''Parameter'''

|}

[[File:RS485.svg|center|frameless|500x500px]]

{| class="wikitable tech-table"

!style="width: 50%;"|'''Parameter'''

|}

{| class="wikitable tech-table"

!style="width: 50%;"|'''Parameter'''

|}

{| class="wikitable tech-table"

!style="width: 50%;"|'''Technology'''  

|}

{| class="wikitable tech-table"

!style="width: 50%;"|'''Connector'''  

|}

{| class="wikitable tech-table"

!style="width: 50%;"|'''Peripheral'''

|}

{| class="wikitable tech-table"

!style="width: 50%;"|'''Parameter'''

|}

{| class="wikitable tech-table"

!style="width: 50%;"|'''Parameter'''

|}

{| class="wikitable tech-table"

!style="width: 50%;"|'''Parameter'''

|}

{| class="wikitable tech-table"

!'''Parameter'''

|}

{| class="wikitable tech-table"

!style="width: 50%;"|'''Certification'''

|}

{| class="wikitable tech-table"

!style="width: 50%;"|'''Parameter'''

|}

{| class="wikitable tech-table"

!style="width: 50%;"|'''Feature'''  

|}

==== Front View ====

==== Top View ====

[[File:Atlas topview.png|center|frameless|688x688px]]

'''Raspian'''

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

There is three ways to connect to the device. IP and state of the connection be checked on the LCD Network Interface.

Client dynamic IP obtained by DHCP server.

Static IP: '''93.48.86.253'''

IP: '''192.168.30.1'''

{| class="wikitable"

|

|}

port: 1883

login <not needed>  

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.

Both relays '''default''' state is '''open'''.  

}</syntaxhighlight>

Req-Topic: relayOutputs/runtime/in<syntaxhighlight lang="json">

{

</syntaxhighlight>

Req-Topic: relayOutputs/runtime/in<syntaxhighlight lang="json">

{

</syntaxhighlight>

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.

'''mode:''' Timer, alarm or none.

</syntaxhighlight>

'''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''')

</syntaxhighlight>

'''mode:''' Timer, alarm or none.

</syntaxhighlight>

Req-Topic: clock/runtime/in <syntaxhighlight lang="json">

{

</syntaxhighlight>

[[File:RTCActor Overview.svg|center|frameless|774x774px]]

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.

'''Topic: systemHea l th/runtime/ out'''

Publish rate: '''1 Hz''' (one message per second, clock-jump safe)

{| class="wikitable tech-table"

!'''Key'''

</syntaxhighlight>

  In order get the peripherals health we had to implement a SystemHealth actor in each bus manager (busi2c­O, busi2c-1, etc. ... ).

[[File:Peripherals health.svg|center|frameless|792x792px]]

'''For busi2c-0:'''

</syntaxhighlight>

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.

Req-Topic: tempSensor/config/in

</syntaxhighlight>

Req-Topic: tempSensor/config/in

</syntaxhighlight>

* unit: Temperature unit of measure

</syntaxhighlight>

User App interface and functionalities exposed to the open part of the MQTT broker. Simplified interface to control and interact with the TFT display, or frontal panel LCD screen. Connecting to the broker for this Area requires no credentials.

  The TFT Actor is responsible for:

* Providing feedback to the application via MQTT

The TFT actor maintains an '''ordered list of screens''' (carousel).

- RIGHT on last screen --> first screen

The TFT actor supports the following screen types:

* No user interaction required

'''Carousel Navigation:'''

{| class="wikitable"

|}

At system boot:

# Actor waits for runtime commands

* TFT actor does not expose joystick state

* Confirmation screens always require explicit CENTER press

Enabling interaction with the carousel using the topic tft/runtime/in . Actions available will be public to the user.

</syntaxhighlight>

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.

'''  Topic: analoglnputs/config/in - Set ADC channels configurations'''

</syntaxhighlight>

'''Topic: analoglnputs/runtime/in.'''

</syntaxhighlight>

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.

Req-Topic: analogOutputs/config/in

</syntaxhighlight>

Req-Topic: analogOutputs/runtime/in

</syntaxhighlight>

Req-Topic: analogOutputs/runtime/in

</syntaxhighlight>

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.

The '''fast''' speed setting supports edge detection speed up to 100 Hz and the '''slow''' speed settings supports up to 10 Hz.

</syntaxhighlight>

Req-Topic: digitallnputs/runtime/in<syntaxhighlight lang="json">

{

</syntaxhighlight>

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.

Req-Topic: digitalOutputs/runtime/in<syntaxhighlight lang="json">

{

</syntaxhighlight>

Req-Topic: digitalOutputs/runtime/in<syntaxhighlight lang="json">

{

</syntaxhighlight>

If the busi2c-3 is not powered, we will get this:

</syntaxhighlight>

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.

Req-Topic: joystick/runtime/in<syntaxhighlight lang="json">

{

</syntaxhighlight>

[[File:AtlasCode.svg|center|frameless|583x583px]]

[IMAGE PLACEHOLDER]

{| class="wikitable"

|'''PA'''

|}

{| class="wikitable"

|'''PA'''

|}

{| class="wikitable"

|'''Version'''

|}

[IMAGE PLACEHOLDER]