3 ms·
I think this is one of the few RFS that I would drop everything for. The factory environment has to be one of the most frustrating as a software developer. So
by karmicthreat 10y ago
I think this is one of the few RFS that I would drop everything for.
The factory environment has to be one of the most frustrating as a software developer. So much low hanging fruit that you really have to develop too much if you are not following the typical industrial idioms. (Throw ladder logic at it, keep at it till it barely works, then run it till the wheels fall off.)
Even just something as simple as reporting on a 30K$ PLC driven machine is painful. You can't buy a 10K HMI with Wonderware (a still painful piece of software) so you just ignore it. In my particular case I developed a simple reporting system on a RPI.
These industrial systems are usually not capable of even SQL or MQTT. You have to strap on an extra piece of hardware and a ton more money for licensing.
Even deployment is painful. You can't just push new code because you have no way to mock your industrial systems. Even if you could you will need to live edit your code into the PLC or you will wipe its current state of recipes and other user data. Because your PLC wasn't able to use standard SWE tools to get that data. God help you if you need to roll back.
So I am applying to this. Everything is broken. Where do you even start? Fix the platform, fix the robots, fix the job setup, fix the people.
- aryamaan 10y agoWhat?
- karmicthreat 10y agoExactly. These systems are pretty foreign to most people. It has completely different vernacular, idioms and tradition. It is very different than say backend development.
- aapusaam 10y agoIndustrial IoT modules are solving these problems. I have been developing/deploying these modules for the past two years that interface to the controllers and send MQTT messages OTA to the cloud for analytics. Ofcourse, it is a bit of a challenge to interface to these legacy industrial systems, but not impossible.