multi-protocol
There are 15 repositories under multi-protocol topic.
mRemoteNG/mRemoteNG
mRemoteNG is the next generation of mRemote, open source, tabbed, multi-protocol, remote connections manager.
pnoker/iot-dc3
IoT DC3 is a fully open-source distributed Internet of Things (IoT) platform built on Spring Cloud. It accelerates IoT project development and simplifies IoT device management, providing comprehensive solutions for building robust IoT systems.
nosqlbench/nosqlbench
The open source, pluggable, nosql benchmarking suite.
daq-tools/kotori
A flexible data historian based on InfluxDB, Grafana, MQTT, and more. Free, open, simple.
soligen2010/RC_RX_CABELL_V3_FHSS
RC Reciever firmware using arduino and NRF24L01+
beNative/LogViewer
A multi-purpose logviewer
GerryYuan/giot
IoT Platform, Device management, data collection, processing and visualization, multi protocol, rule engine, netty mqtt client
cern-fts/fts3
Low level data movement service
cooldogepm/MultiProtocol
Allows players to play with different versions of the game
AdrianWahyu/Biconic-AI
Enterprise AI framework orchestrating AI agent swarms with reinforcement learning for scalable, autonomous business solutions.
alexbrjo/ChatBot
A chatroom bot that can preform a couple basic functions.
NETHICAI/NETHIC-AI
NETHIC is a decentralized AI platform on blockchain for secure on-chain training and NFT-based model ownership.
bmdbtech/mRemoteNG
mRemoteNG is the next generation of mRemote, open source, tabbed, multi-protocol, remote connections manager.
ghaith-jbali/Embedded-Multi-Protocol-Adapter-
Reconfigurable multi-protocol communication adapter for embedded systems, bridging UART, SPI, I²C, and CAN in real-time. Built on STM32F446RE with FreeRTOS and embedded Lua VM for scripting, ESP-01 web dashboard for configuration, and PC companion tool for debugging. Ideal for IoT prototyping and protocol conversion.
zahi1/multi-protocol-system-integration
Multi-protocol system integration of a gas‑pressure simulation with interoperable Container, Input, and Output components joined via adapters. Server uses SimpleRPC; Input client uses gRPC; Output client uses RESTful HTTP; adapters unify calls into a single RPC-style domain interface.