Hello all, first post here, sorry if it's a bit long...
I'm brand new to the Teensy ecosystem, the product just wasn't on my radar. I just stumbled into it and like what I see. I just ordered a 4.1 and Ethernet kit to try out.
I have an industrial project that is required to communicate as a Modbus TCP slave. It seems the world has moved on from "legacy" protocols, and there is not a lot of interest / support as Wireless is the new hotness. Industrial controls have not moved on, at least in my world. Modbus, 4-20ma sensors, etc. are not going away anytime soon. I've done some embedded RS-485 & CANbus projects in the past, but have not dealt with Ethernet.
I started out this project ESP32 (using the official ethernet dev kit) and tried various Ethernet and Modbus library combinations. The Modbus portion is proving more difficult than I expected. The ESP32 official Modbus TCP stack is rock solid, and blazing fast... as long as you don't try to connect a second client, then it crashes. It's a known issue on the Expressif GitHub repo, and they are actively working on the problem. Even when they get it sorted, I'm not sure I want to go that route. There is just such low adoption that other bugs may be lurking, and I just don't have the bandwidth to deal with that.
This brings me to Teensy. What libraries would you recommend? ArduinoModbus? something else? I'm hoping to hear from anyone that has deployed to real world Modbus applications based on Teensy.
My project is pretty simple; continuously poll up to 64 I2C sensors (using I2C multiplexers as the sensors are all fixed address), and publish the readings to Modbus registers read by two masters, one is an industrial HMI, the other is an Ignition SCADA server. What is critical is that it's rock solid. Once the system is put into production, it's a huge disruption to shut down.
Thank you.
I'm brand new to the Teensy ecosystem, the product just wasn't on my radar. I just stumbled into it and like what I see. I just ordered a 4.1 and Ethernet kit to try out.
I have an industrial project that is required to communicate as a Modbus TCP slave. It seems the world has moved on from "legacy" protocols, and there is not a lot of interest / support as Wireless is the new hotness. Industrial controls have not moved on, at least in my world. Modbus, 4-20ma sensors, etc. are not going away anytime soon. I've done some embedded RS-485 & CANbus projects in the past, but have not dealt with Ethernet.
I started out this project ESP32 (using the official ethernet dev kit) and tried various Ethernet and Modbus library combinations. The Modbus portion is proving more difficult than I expected. The ESP32 official Modbus TCP stack is rock solid, and blazing fast... as long as you don't try to connect a second client, then it crashes. It's a known issue on the Expressif GitHub repo, and they are actively working on the problem. Even when they get it sorted, I'm not sure I want to go that route. There is just such low adoption that other bugs may be lurking, and I just don't have the bandwidth to deal with that.
This brings me to Teensy. What libraries would you recommend? ArduinoModbus? something else? I'm hoping to hear from anyone that has deployed to real world Modbus applications based on Teensy.
My project is pretty simple; continuously poll up to 64 I2C sensors (using I2C multiplexers as the sensors are all fixed address), and publish the readings to Modbus registers read by two masters, one is an industrial HMI, the other is an Ignition SCADA server. What is critical is that it's rock solid. Once the system is put into production, it's a huge disruption to shut down.
Thank you.