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

123 13

#1 21660123 16 Nov 2011 20:38

Peter Halick Peter Halick

Anonymous

Post #1
21660123 16 Nov 2011 20:38

I am developing a human machine interface and controls for a medical device. What is the most efficient way to move from off the shelf products, PLCs and purchased programmable touch screens, to embedded stuff. I need analog inputs and a touchscreen with the ability to control an AC motor. Any suggestions on specific development boards. Is this months of programming or weeks?
ADVERTISEMENT
#2 21660124 17 Nov 2011 03:16

Joe Wolin Joe Wolin

Anonymous

Post #2
21660124 17 Nov 2011 03:16

Peter,

Are you planning on doing this work yourself for the first time or hiring it out to a senior embedded developer?

If you're looking for a development platform, I'd go for one of the mainstream micros such as a AVR or PIC as there are large online communities that you can tap into for help.

Let us know if you have more specific question about doing an embedded project.
#3 21660125 17 Nov 2011 09:38

Peter Halick Peter Halick

Anonymous

Post #3
21660125 17 Nov 2011 09:38

If this project could be done within a reasonable budget I would gladly find a programmer/designer. However I have not been able to find a company or person with these skills. I am a licensed mechanical engineer with many years of experience with machine control and a decent background with PLC and CNC and hobby controllers like arduino. I would be willing to personally devote about 200 hours to programming. Otherwise its a purchase.

How can I find skills. I have spoken with microchip corporation with only one referal which didn't pan out.
ADVERTISEMENT
#4 21660126 17 Nov 2011 18:15

Ralph Pruitt Ralph Pruitt

Anonymous

Post #4
21660126 17 Nov 2011 18:15

Hey Peter,

Have you thought of doing a paradigm shift and go to an Embedded Linux or Android solution. These are almost off the shelf and require programming apps in Java. I am looking at solutions for my company right now based on the Freescale iMX53 solution and using a version of Android as the underlying OS solution.
#5 21660127 18 Nov 2011 17:14

Robin Moss Robin Moss

Anonymous

Post #5
21660127 18 Nov 2011 17:14

Hi Peter,
I don't know your requirements, but an easy step into micro controllers I found was through these 2 processors.
They both have active and helpful forums.

FEZ Cobra
http://www.ghielectronics.com/catalog/product/131

Netduino Plus
http://www.netduino.com/netduinoplus/specs.htm

Both are incredibly easy to develop, one of the draw backs depending on your requirements, may be that your solution requires real-time processing. There is about a 20ms delay on these boards, due to the .NET Microframework. However, the FEZ processor does allow you to run realtime routines via their RPL. ( Realtime Processing something ).
#6 21660128 18 Nov 2011 19:32

Peter Halick Peter Halick

Anonymous

Post #6
21660128 18 Nov 2011 19:32

This board looks interesting. I need to get an idea of the amount of programming involved. I assume I'm looking at hundreds of hours of programming as well as costs to create a final electronics package ready for production.
ADVERTISEMENT
#7 21660129 19 Nov 2011 10:29

Ralph Pruitt Ralph Pruitt

Anonymous

Post #7
21660129 19 Nov 2011 10:29

It depends on how you want to deploy a solution through Android or Linux. Android takes care of much of the work of the OS and you only need to write the HID in believe or not...XML..and even that can be done in a graphical way.....The app and underlying code is Jave written in a windowing method. There are many tutorials for Android and good books for the development....I can't see how a good app could take 200 hours. The trick is learning the coding methods within the Android OS.
ADVERTISEMENT
#8 21660130 19 Nov 2011 16:00

Per Zackrisson Per Zackrisson

Anonymous

Post #8
21660130 19 Nov 2011 16:00

Since you are experienced with arduino why not try
OLIMEXINO-STM32 MAPLE / ARDUINO (http://olimex.com)! Its is a arduino compatible board but with a arm processor. And as userinterface I would consider writing an app for andoid or iphone, either bluetooth or usb.
#9 21660131 21 Nov 2011 14:57

Peter Halick Peter Halick

Anonymous

Post #9
21660131 21 Nov 2011 14:57

What you recommend for analog inputs. I'm reading two load cells and a serial inclonometer.
#10 21660132 21 Nov 2011 15:02

Peter Halick Peter Halick

Anonymous

Post #10
21660132 21 Nov 2011 15:02

What products would you recommend for reading an analog signal from a load cell? The analog signal is currently fed through a very expensive signal conditioner and phoenix contact analog module.
#11 21660133 21 Nov 2011 15:08

Peter Halick Peter Halick

Anonymous

Post #11
21660133 21 Nov 2011 15:08

Thanks I looked up these boards. But I'm trying to define "incredibly easy to develop". Pay a pro X dollars or spend X hours using my rudimentary but expanding programming skills.Any thoughts.
#12 21660134 21 Nov 2011 15:15

Robin Moss Robin Moss

Anonymous

Post #12
21660134 21 Nov 2011 15:15

Hi Peter,both boards and the Aurduino have Analog inputs... 0 - 3.3V, 0-1023 ( 0 = 0V and 1023 = 3.3V ), it is easy to convert 4-20mA to the required 0-3.3V. Serial data is no problem either, FYI, I have connected this 485 level to the Cobra.I'm happy to look over what you have and want to achieve. I will PM you my contact details.
#13 21660135 26 Nov 2011 20:18

Mark Harrington Mark Harrington

Anonymous

Post #13
21660135 26 Nov 2011 20:18

Have you ever considered using possibly something along the lines of mobile phones such as may be blackberry which incorporates touch screens and for which the software and development tools are already free and available for download , Java based languages , There is of course ANSI C compilers , also available for download for use with devices such as Atmel

Using wifi networked technology such that you can develop user interfaces to send packet packet messages to embedded technology

It might be worth looking into other devices possibly the PIC RF range would could offer what you need Short of this you might be considering PC based servers linked to wifi networks and then onto embedded devices via RS 232 ports or Ethernet interfaces with PIC or Atmel devices

Development boards can be obtained from sources such as www.ladyada.net/make/xbee/

Sounds as though its quite project and would needs considerable research before deciding what path to take Certainly you would require a sound knowledge of networked techniques together with networking software languages Maybe even blue tooth stack as well not to mention a good knowledge of the type of embedded micro that you would be using with PWM techniques to control the motor Lots of self study and self learning combined with C , C++ , ARTOS 200 hours plus I would estimate 600 Plus myself
#14 21660136 28 Nov 2011 11:45

Peter Halick Peter Halick

Anonymous

Post #14
21660136 28 Nov 2011 11:45

Great. Thanks for your info I figured 600 was possible. Apreciate the reality check.
Create an account, log in here. You will receive points by participating in discussions.
Join this discussion.

Install Elektroda application

Didn't find an answer? Ask Artificial Intelligence

*I agree to send the question to OpenAI, Anthropic PBC, Perplexity AI, Inc., Kagi Inc., Google LLC - owners of language models in order to prepare the best response. The companies may monitor and log information entered into the form.

*I agree to publicly display my question and answer. The question and answer will be publicly available to everyone. The process may take a few minutes. Upon completion, you will be redirected to the page with the answer.

Wait...(2min)

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.
Generated by the language model.

FAQ

TL;DR: Expect 200–600+ hours for an HMI with analog I/O, touchscreen, and AC motor control; “it’s quite [a] project.” [Elektroda, Mark Harrington, post #21660135] Why it matters: This FAQ helps PLC-to-embedded movers pick boards, plan effort, and avoid real-time and analog pitfalls for medical HMI builds.

Quick Facts

Typical analog input on suggested boards: 0–3.3 V, 10‑bit (0–1023), with simple 4–20 mA conversion. [Elektroda, Robin Moss, post #21660134]
.NET Micro Framework boards can add ~20 ms latency; FEZ offers realtime via RLP. [Elektroda, Robin Moss, post #21660127]
Effort planning: prototype-to-product often spans 200–600+ developer hours. [Elektroda, Mark Harrington, post #21660135]
Android/Linux path: Java app with XML UI; OS handles much device plumbing. [Elektroda, Ralph Pruitt, post #21660129]
Starter HMI boards discussed: FEZ Cobra and Netduino Plus, both with active communities. [Elektroda, Robin Moss, post #21660127]

What’s a practical starter board for HMI with a touchscreen?

FEZ Cobra and Netduino Plus are entry-friendly and community-backed. They support touch UIs and peripherals. Note that .NET Micro Framework adds latency, so evaluate response time. FEZ’s RLP lets you offload time‑critical routines. Start with dev kits, then migrate to custom PCBs. [Elektroda, Robin Moss, post #21660127]

Can these boards read my analog sensors directly?

Yes, their ADCs accept 0–3.3 V with 10‑bit resolution (0–1023). For 4–20 mA loops, use a shunt and scale to 0–3.3 V. Serial sensors like RS‑485 inclinometers also connect with proper transceivers. “Serial data is no problem either.” Validate noise and grounding early. [Elektroda, Robin Moss, post #21660134]

How many hours should I budget to move from PLCs to embedded?

Plan for 200–600+ hours depending on features, safety, documentation, and validation. Networking, motor control, and HMI polish expand scope. One contributor estimated “600 Plus” for a robust solution. Timebox learning spikes and keep noncritical features for phase two. [Elektroda, Mark Harrington, post #21660135]

Should I choose Android or Embedded Linux for the HMI?

Android offers fast UI development in Java with declarative XML layouts. Many tasks are off‑the‑shelf, reducing OS plumbing. Boards like Freescale i.MX53 run Android for rich touch interfaces. Validate real‑time needs and use external controllers for tight loops. [Elektroda, Ralph Pruitt, post #21660126]

Is Android UI coding heavy for this use case?

UI scaffolding is quick since Android handles views and events, and XML defines layouts. “The app and underlying code is Java.” The main learning curve is Android’s component model. Prototype screens first, then integrate hardware services. [Elektroda, Ralph Pruitt, post #21660129]

Do I need a real-time OS for motor control?

If your control loop needs sub‑millisecond timing, avoid pure .NET MF loops. Expect ~20 ms framework overhead. Offload timing‑critical PWM or FOC to native code or a dedicated MCU while the HMI runs managed code. [Elektroda, Robin Moss, post #21660127]

What about the load cells—can I skip the expensive conditioner?

Your current design uses a signal conditioner and a Phoenix analog module. Maintain equivalent conditioning or replace with a suitable front‑end before the MCU’s ADC. Budget time to validate accuracy and drift across temperature. [Elektroda, Peter Halick, post #21660132]

How do I connect an RS‑485 inclinometer to an HMI board?

Use an RS‑485 transceiver and match baud, polarity, and termination. Cobra‑class boards can handle serial framing in software. Keep cable shielding and biasing correct to avoid intermittent data dropouts. [Elektroda, Robin Moss, post #21660134]

Which microcontroller families are safest bets for community help?

Pick mainstream lines like AVR or PIC to tap large communities and examples. This reduces bring‑up risk and accelerates debugging. Decide based on available libraries, tools, and your team’s skills. [Elektroda, Joe Wolin, post #21660124]

What skills or components inflate project time the most?

Networking stacks (Wi‑Fi/Bluetooth), secure comms, motor PWM control, and multi‑device integration add effort. Server links, RS‑232/Ethernet bridges, and radio modules like XBee expand scope. Expect research and validation cycles. [Elektroda, Mark Harrington, post #21660135]

What is the .NET Micro Framework, and when is it OK?

.NET MF lets you write embedded apps in C# on boards like FEZ and Netduino. It simplifies UI and logic but adds ~20 ms latency. Use it for HMI and supervisory tasks; push tight control to native layers. [Elektroda, Robin Moss, post #21660127]

I’m an Arduino‑savvy mechanical engineer—can I self‑deliver?

Yes, with scope control. Boards discussed expose analog inputs and serial easily, easing transition from PLCs. Aim for a working HMI first, then add motor control. Timebox to 200 hours for MVP, expand afterward. [Elektroda, Robin Moss, post #21660134]

How do I quickly prototype an Android‑based HMI?

Choose an i.MX53‑class board that runs Android.
Build the UI in XML and app logic in Java.
Bridge hardware via serial, USB, or Ethernet and test end‑to‑end. “Android takes care of much of the work of the OS.” [Elektroda, Ralph Pruitt, post #21660126]

What’s a reasonable definition of “incredibly easy to develop” here?

In this context, it means rapid HMI iteration, built‑in analog and serial I/O, and active forums for answers. FEZ and Netduino fit this, with the caveat of real‑time latency. RLP provides a path for time‑critical routines. [Elektroda, Robin Moss, post #21660127]

Any edge cases I should plan for before committing?

Plan for failure modes: serial framing errors, ADC saturation beyond 3.3 V, and motor stalls during latency spikes. Add hardware protection and watchdogs. Validate the 20 ms managed overhead against your control loop budget. [Elektroda, Robin Moss, post #21660127]

How can I find the right embedded talent if I don’t DIY?

Target developers experienced with AVR or PIC, as suggested, and review community contributions. Share a lean spec and ask for a fixed‑scope prototype quote. Prioritize candidates with HMI and motor‑control portfolios. [Elektroda, Joe Wolin, post #21660124]

Generated by the language model.