logo elektroda
logo elektroda
X
logo elektroda

Best embedded development boards for HMI, analog input, touchscreen, AC motor control

27 13
ADVERTISEMENT
  • #1 21660123
    Peter Halick
    Anonymous  
  • ADVERTISEMENT
  • #2 21660124
    Joe Wolin
    Anonymous  
  • ADVERTISEMENT
  • #3 21660125
    Peter Halick
    Anonymous  
  • ADVERTISEMENT
  • #4 21660126
    Ralph Pruitt
    Anonymous  
  • #5 21660127
    Robin Moss
    Anonymous  
  • #6 21660128
    Peter Halick
    Anonymous  
  • #7 21660129
    Ralph Pruitt
    Anonymous  
  • #8 21660130
    Per Zackrisson
    Anonymous  
  • ADVERTISEMENT
  • #9 21660131
    Peter Halick
    Anonymous  
  • #10 21660132
    Peter Halick
    Anonymous  
  • #11 21660133
    Peter Halick
    Anonymous  
  • #12 21660134
    Robin Moss
    Anonymous  
  • #13 21660135
    Mark Harrington
    Anonymous  
  • #14 21660136
    Peter Halick
    Anonymous  

Topic summary

The discussion focuses on transitioning from off-the-shelf PLCs and programmable touchscreens to embedded development boards for a medical device HMI with analog inputs, touchscreen capability, and AC motor control. Recommended platforms include mainstream microcontrollers such as AVR and PIC for their extensive community support. Alternatives suggested are embedded Linux or Android-based solutions, notably the Freescale iMX53 with Android OS, which simplifies UI development via Java and XML. For easier microcontroller entry, boards like FEZ Cobra and Netduino Plus, both supporting analog inputs and .NET Microframework, were proposed, though with some latency considerations. The OLIMEXINO-STM32 MAPLE board, Arduino-compatible with an ARM processor, was also recommended for users familiar with Arduino. Analog input solutions for load cells and serial inclinometers were discussed, with suggestions to convert 4-20mA signals to 0-3.3V for compatibility. Development time estimates vary, with programming potentially requiring hundreds of hours depending on the chosen platform and developer expertise. Additional ideas include leveraging mobile phone platforms (e.g., BlackBerry) with touchscreen and Java-based development, and using wireless networking (WiFi, XBee) to interface embedded devices. Overall, the choice depends on real-time processing needs, programming skills, and budget constraints.
Summary generated by the language model.
ADVERTISEMENT