#AITHACore
AITHA Core
Can AITHA be the base of your connected product? See what you can reuse from AITHA Core, what gets adapted to your device and what we need to know to answer you.
When AITHA Core makes sense
Your product needs to connect, report and update remotely, and you would rather not build that base from scratch.
- Connected product with sensors, alerts or remote control.
- Industrial machine that must report its status.
- Equipment spread across many sites.
- Remote device with limited power or coverage.
- Gateway between the field (RS485, Modbus, CAN) and the cloud.
- Telemetry to AITHANEX or to your own platform.
- OTA updates without site visits.
- Multiple connectivity: 4G, WiFi, Bluetooth, plus Ethernet or LoRa depending on the variant.
Application examples
Conceptual cases that illustrate where this base fits. They are design examples, not references to executed projects.
Industrial machinery
A machine that must report its status and receive adjustments without bringing a computer to it.
Distributed equipment
Hundreds of units spread across different sites, monitored from one place.
Field gateway
A unit that gathers signals over RS-485, Modbus or CAN and takes them to your cloud.
What can be reused
Depending on your project configuration.
- Multi-network connectivity with automatic failover.
- Base firmware and A/B OTA updates with rollback.
- Local logging offline, synced later.
- Pairing and configuration (provisioning) over Bluetooth.
- Field interfaces available depending on the variant.
- Telemetry over MQTT and HTTP.
- Integration with AITHANEX or your own systems.
What must be adapted
What is specific to your product is not solved in advance.
- Power supply.
- Sensors and actuators.
- The specific interfaces of your device.
- Mechanics and enclosure.
- Application-specific firmware.
- Certification of the final product, which is part of the project scope.
- Integration with your equipment.
- Backend, if you do not use AITHANEX.
What we need to know
With these details we can tell you whether AITHA Core fits, and where.
| Item | What it helps us assess |
|---|---|
| Application | What the product must measure, report or control. |
| Volume | Pilot, short run or recurring production. |
| Environment | Outdoor, indoor, temperature, vibration, coverage. |
| Power | Available voltage, battery or target consumption. |
| Interfaces | RS485, Modbus, CAN, inputs and outputs, sensors. |
| Connectivity | 4G, WiFi, Ethernet, LoRa or Bluetooth. |
| Existing platform | Whether you will use AITHANEX or integrate with your systems. |
| Certifications | Markets and standards the final product must meet. |
| Stage | Idea, prototype, pilot or product in the field. |
When not
If your product needs a very specific electronic design and little of this base would apply, AITHA Core is not the shortest path. In that case, see the engineering services from Grupo Unlix.
Connectivity, location and remote operation
Each product activates only what it needs.
Products using this base
Each product reuses the needed functions and adds its own interfaces and logic.
Capabilities reused across products
Hybrid connectivity, location, field buses (Modbus, CAN, RS485) and remote updates available depending on the variant.
AITHA Core integrates LTE, WiFi, Bluetooth, Ethernet, GNSS, IMU, Modbus/CAN/RS485 and A/B OTA. Check voltages, chips and pins in the technical datasheet.
Frequently asked questions
Which networks is it compatible with?
AITHA Core includes 4G, WiFi and Bluetooth; Ethernet and LoRa depend on the variant. It switches automatically between available connections.
Can it be updated remotely?
Yes. Remote OTA updates keep two versions. If the new one fails or doesn't boot, the previous one is restored automatically.
Does it integrate with existing systems?
Yes. It integrates via AITHANEX or directly with your systems over MQTT and HTTP.
What happens when there's no coverage?
AITHA Core stores data without coverage and syncs it with AITHANEX when coverage returns, within the configured capacity.
Can I use my own cloud platform instead of AITHANEX?
Yes. The device can send telemetry directly to your systems over MQTT or HTTP. AITHANEX is optional.
Who owns the application firmware?
The scope is agreed per project. We describe what is reused from the AITHA base and what is developed for your product before starting.
What volume does it make sense for?
It depends on the project. Tell us whether you are at pilot, short run or recurring production and we will assess it with you.
Documentation in PDF
Download the product document.
Evaluate AITHA Core for your product
Tell us the application, volume and stage. We will tell you what is reused, what is adapted and whether AITHA Core fits.