A User-Interfaced Arduino Mega Pro with Ebyte LoRa Radio.
It's like a RF-Node but call it a 'Tode'.
- Arduino Mini Mega 2560 compatible Micro-Controller
- 1.8" TFT Display and 6-Button Keypad
- User friendly On-Controller IO configuration
See the docs/ Users-Guide for device support list and usage details including MQTT OpenHab connection abilities.
Benefits of the Tode over ESP32 LoRa Modules
- Big enough to be practical. Small enough to be handy.
- 5V TTL-IO (Ebyte-RF 5V match, 200mW/IO power, Ready-fit for 5V Sensors)
- 54-IO pins (leaving (46) with display, keypad, radio connected)
- 30dbm (T30D) Transmission Power with Ebyte LoRa Modules (A good 5-mile distance)
- 3-Piece plug-together assembly keeps individual parts easy to swap/salvage.
Due to button sticking issues the buttons are now just black tops shown in first image.
Purchase pre-made at...
- Firmware at https://github.com/TGit-Tech/Tode-RC-Firmware
- Be sure to set Backplane model in config.h
- Side-IO Screw Terminals #SIOST (pictured) https://github.com/TGit-Tech/Tode-IO
- Back-IO Pin Header Array #BIOPH https://github.com/TGit-Tech/Tode-IO
USE Tode-RC.BD241S. It supports 1W(T30D) or 1/4W(T20D) Ebyte Radios.
Double Check that the PCB doesn't have the below design error.
Model SD23CF(In-Design/BETA) supports 2W(T33D) Radios but only 7-IO pins.
- Previous Release Notes NEW changes. The old model SA212K with analog keypad will become obsolete (not supported). All future designs will have digital keypads as analog was spotty with moisture and temperature change. Secondary Power Supplies are On-PCB now for both SD23CF(Side-IO) and BD241S(Back-IO). Firmware will auto-detect E32-433T20D/T30D, E22-400T30D/900T30D and E220-400T30D Ebyte Radios.
The Tode Ecosystem offers a robust, flexible, and secure solution for managing devices in an environment where infrastructure is not required. It’s designed to seamlessly integrate with the RF-DITS protocol, providing a communication framework for device control, alarm propagation, and security.
The Tode Ecosystem empowers devices to function autonomously or in P2P (peer-to-peer) networks, providing an infrastructure-free solution for industrial, home, and remote applications. With its 5V EMT-resistant hardware and powerful virtual device logic for alarm processing, it brings resilience and versatility to the edge of your network.
-
Non-Infrastructure Communication: Operates without requiring an internet connection, server, or cloud dependencies. Devices communicate peer-to-peer between nodes, allowing for seamless data exchange and control.
-
RF-DITS Protocol: The core communication protocol used by the Tode ecosystem. This protocol allows secure, fast, and efficient communication between Master and Remote nodes using Device Index Tables (DIT) with integrated security.
-
5V EMT Resistance: Built to handle harsh environments, the Tode ecosystem is engineered to withstand electromagnetic interference (EMI), providing reliable operation in industrial settings.
-
Virtual Device Logic: The Virtual Device Logic allows users to implement custom control logic directly on the device, enabling real-time alarm processing, device manipulation, and other control functions.
-
Quick Firmware Updates: The firmware can be quickly updated by plugging the Tode node into a wiring interface, making updates straightforward without requiring specialized equipment.
-
SecNet (Security Network): The Tode ecosystem utilizes SecNet, a user-set security code embedded in each packet. This ensures data integrity and security. The SecNet code is also used as part of a challenge-response mechanism during SETVAL operations, preventing replay attacks and ensuring secure value updates.
-
Packet Integrity: Every packet transmitted in the Tode network is verified for authenticity with the SecNet code. Only authorized devices can send or receive data securely. SETVAL operations are particularly secured to ensure legitimate communication.
-
Alarm Security: Alarm messages are pushed to the designated Remote nodes when a condition is triggered. The SecNet code ensures that only authorized recipients receive the alarm notifications.
-
Device Setup: The Tode ecosystem doesn’t require centralized infrastructure or cloud servers. Each Master node stores the configuration of its attached devices and is capable of sharing this configuration with Remote nodes using the RF-DITS protocol. Remote nodes can pull configurations and control devices according to those settings.
-
Time-Sensitive Updates: Alarm conditions are pushed immediately to all Remote nodes without unnecessary overhead. Value updates can be requested by the remote node through the RF-DITS protocol, ensuring efficient communication.
| Key Advantage | Tode Ecosystem (RF-DITS) | Common IoT Platforms |
|---|---|---|
| Infrastructure | Operates without internet or server dependencies, functioning in peer-to-peer mode. | Requires cloud, servers, or centralized hubs for device control |
| Portability | Portable control with remote nodes in P2P communication. | Typically dependent on fixed infrastructure |
| Data Integrity | Secured communication with SecNet protecting packets and ensuring valid data exchange. | Often lacks robust security or packet verification |
| Low Airtime Communication | Optimized communication with DIT table, reducing airtime usage for value exchanges. | Typically uses more airtime due to polling systems and continuous communication |
| Alarm Handling | One-time push of alarms to Remote nodes, minimizing network traffic. | Continuous polling for alarm conditions, leading to higher network usage |
| Device Control | Full control over devices with direct value setting, updating, and logic processing. | Remote devices may be read but not easily controlled depending on the platform |
| EMT Resistance | Designed to handle electromagnetic interference (EMI) in industrial environments. | Sensitive to environmental EMI interference, which can disrupt performance |
| Firmware Updates | Easy and fast firmware updates via a wiring interface—no internet or specialized equipment needed. | Over-the-air updates typically require internet access and cloud dependencies |
| Flexible Control Logic | Virtual device logic allows for custom control and alarm processing locally on the device. | Often lacks flexibility for local control and relies on cloud logic |
Each node maintains a Device Index Table (DIT) that lists the connected devices by index. This table helps the Master node store and transmit configurations for each attached device to Remote nodes.
- Master Node: Stores and manages the configuration of devices, pushes alarm notifications, and shares device settings with Remote nodes.
- Remote Node: Pulls device configurations from the Master node and can manipulate values according to the stored configuration.
- Alarm Handling: When an alarm condition is triggered on the Master node, an alarm packet is sent to all Remote nodes on the recipient list.
- No Acknowledgment Required: The alarm is a one-time push with no response required from the Remote nodes.
- Alarm Recipient List: The Master node stores a list of Remote node addresses, which is dynamically updated with each communication, including value requests. Manual pruning of the list is also possible.
While the Tode ecosystem operates without the need for internet infrastructure, it can optionally integrate with systems such as MQTT, OpenHAB, or Home Assistant through an MQTT bridge.
This optional feature allows:
- Pulling Device Values: Remote nodes can request device values from Master nodes on a regular schedule or based on events.
- Pushing Alarms: When an alarm condition is triggered, the Master node can push the alarm data to an MQTT broker, which allows external systems to act on the alarm.
However, it's important to note that Tode's core functionality works without cloud connectivity, and the MQTT integration is entirely optional.
Tode nodes are designed to operate in industrial environments where electromagnetic interference (EMI) is common, and devices need to withstand harsh conditions. The 5V EMT-resistant hardware ensures the Tode ecosystem works reliably even in settings that may disrupt other IoT systems.
- Set Up the Master Node: Connect and configure devices on the Master node. Store configurations and define which devices you want to control.
- Add Remote Nodes: Manually enter the Master node's address into the Remote nodes to establish communication and pull device configurations.
- Manage Alarms and Control: Configure alarm conditions on the Master node. Alarms will be pushed to all Remote nodes.
- Firmware Updates: Simply plug the Tode node into the wiring interface to update its firmware without requiring internet access.
The Tode Ecosystem offers a resilient, flexible, and secure solution for edge-device control in environments where infrastructure is not an option. Its core RF-DITS protocol and 5V EMT resistance provide reliable communication, while its optional integration with systems like MQTT makes it versatile for a range of applications.