flyboy013
RVF VIP
- Joined
- Jul 24, 2020
- Messages
- 386
- Location
- Naples, Florida
- RV Year
- 2018
- RV Make
- Newmar
- RV Model
- Mountain Aire 4531
- RV Length
- 45
- Chassis
- Spartan K3
- Engine
- Cummins ISX12 (500HP)
- TOW/TOAD
- 2023 Jeep GC Summit Reserve
- Fulltimer
- Yes
The system is being design too be locked down such that only the required network ports are exposed and that those ports are as secure as possible. I’ve developed quite a bit of software for the DoD and fully understand the need to and value of properly securing systems. That’s not to say that access to the MQTT server cannot be made available, it’s just not there now as has been no need."The solution does utilize MQTT, but it is not designed to be an interface to external systems. The MQTT server is currently userid/password protected. The goal is to secure it further with SSL, limiting access to LAN, and restricting accounts to reading/writing only a portion of the data in the database. I worked developing DoD systems for quite some time and understand the need for securing the system."
Are you saying that with proper credentials, that a third party system couldn't use the MQTT to bidirectionally control KIB / RV-C devices using your solution?
Not really. I 3D printed some support brackets to mount the required components, but there are still some jumper wires.I would rather leverage your solution (including pointing people to buy yours or resell yours) than spend the effort to reverse the KIB protocol for the small number of expected people that would want to use it (relatively speaking). The two systems would be on same LAN. The user IDs would belong to the owner of the RV. Certainly we would need to know how to pass and accept the authentication method you use.
So hardware wise, on your RV - is your hardware on a breadboard?
I am currently using KiCad for my design work. FYI - The RPi itself is designed with KiCad.And your talented kids are helping you get it onto a PCB?
FYI, there are lots of free PCB design software (Kicad is one).
Once you have your circuit in the software, you just email the resultant file to one of thousands of inexpensive PCB manufacturers that support that output format. Then a week later, you will get the PCB populated or not (depending on what you choose). Easy peasy.
KIB is not CAN based.Would be nice if the PCB was designed as a Raspberry Pi4 Hat.
Another thing to consider is I assume KIB is just a CAN based protocol. There are lots of PCB / Hats for CAN readily available. Just write your software for it.