Is Micropython ready for industry?
Posted: Fri Jan 12, 2018 5:34 pm
I am planning on making a pitch to my partners that we should move controller development to Micropython over the next two years. Does anyone have experience in using Micropython in industrial situations where you replace a PLC with it?
A little background... I develop controls for environmental/water technologies. I can't believe that PLCs are still the industry standard. I've tried for 3 years to get traction with Atmel chips so that engineers could use Arduino to adjust code onsite, but I don't think the Arduino wrapper/C++ brings much of a development benefit for people to change. In essence, it kills the value proposition.
I see the power of Micropython in that I think it is much easier to code, uses less time, and interfaces with the internet much easier than C/C++, so I can make the case that we can safe lots of time on development.
The question is whether things like garbage collection or something else that I'm not aware of pose a problem with using Micropython in embedded solutions. There are very few resources for Micropython out there, so I was hoping to have a discussion here to give me an outlook on what I can reasonably expect if we do switch over.
My goal is to build a few products internally, then use that knowledge to take PLCs so that Micropython developers have access to a UL-Listed device for their code, which would lower the barrier between prototype and sellable unit.
Also, I am considering one of these books:
https://www.amazon.com/dp/1484231228/_e ... 5OHV&psc=0
https://www.amazon.com/dp/B075X49VVH/_e ... 5OHV&psc=0
Any suggestions?
TIA
A little background... I develop controls for environmental/water technologies. I can't believe that PLCs are still the industry standard. I've tried for 3 years to get traction with Atmel chips so that engineers could use Arduino to adjust code onsite, but I don't think the Arduino wrapper/C++ brings much of a development benefit for people to change. In essence, it kills the value proposition.
I see the power of Micropython in that I think it is much easier to code, uses less time, and interfaces with the internet much easier than C/C++, so I can make the case that we can safe lots of time on development.
The question is whether things like garbage collection or something else that I'm not aware of pose a problem with using Micropython in embedded solutions. There are very few resources for Micropython out there, so I was hoping to have a discussion here to give me an outlook on what I can reasonably expect if we do switch over.
My goal is to build a few products internally, then use that knowledge to take PLCs so that Micropython developers have access to a UL-Listed device for their code, which would lower the barrier between prototype and sellable unit.
Also, I am considering one of these books:
https://www.amazon.com/dp/1484231228/_e ... 5OHV&psc=0
https://www.amazon.com/dp/B075X49VVH/_e ... 5OHV&psc=0
Any suggestions?
TIA