M
Michael Griffin
On April 8, 2003 12:54, Alex Pavloff wrote: <clip>
> Michael Griffin wrote:
> > I suppose what we should be asking is what segments of the
> > automation software market look like they could become commoditised? Low
> > end MMI systems perhaps?
Alex Pavloff replied:
> I doubt it. Low end (sub $500 dollar range is my thinking) HMI hardware is
> about driving hardware costs down by picking low-end parts and driving up
> volume. When you pick low end hardware, you limit your programming
> choices. When you increase volume, you can afford to go with a custom
> solution.
I wasn't referring to "MMI Panels". I see that as a different market segment with a lot of differences between them and PCs besides just price. They are designed to be something any competent industrial electrician can troubleshoot and replace (just like a PLC). That's more of a "system" feature rather than something software alone can give you.
I was however referring to the segment at the bottom end of the market where an actual PC is required for some reason. You will notice that there is very regular discussion here on how to use VB (or Delphi), or even (shudder) Excel as an MMI development system. The usual reasons given are the need for a programmable system that has low capital costs for the development software and (often) royalty free run times.
There does seem to be a demand which isn't being met by existing systems for some reason and which an open source solution may fit. This isn't something I would have a need for myself, but I can't but help noticing people asking for something like it.
> Besides, the main hurdle to open source in automation is that there isn't
> any large body of open source automation code out that people want to use.
> Sure, there are dribs and drabs here and there, but not enough to make
> anyone go "Ooo! If I use this code it'll save me lots of time!"
<clip>
However, that isn't the only way for something to arise. I see a more likely origin to be where someone finds a software development system which was intended for another application but is fairly close to what is needed for a useful MMI development package. All that may be needed is to add on a few GUI widgets and other minor bits (strip chart, etc.) to get something that is good enough for a lot of purposes (or at least better than VB).
I can't give you an detailed example of how to do this, as I haven't been doing any research on something I don't need. However, building user interfaces quickly and easily is a fairly common software development task, so we shouldn't be surprised to find something that fits the bill.
************************
Michael Griffin
London, Ont. Canada
************************
> Michael Griffin wrote:
> > I suppose what we should be asking is what segments of the
> > automation software market look like they could become commoditised? Low
> > end MMI systems perhaps?
Alex Pavloff replied:
> I doubt it. Low end (sub $500 dollar range is my thinking) HMI hardware is
> about driving hardware costs down by picking low-end parts and driving up
> volume. When you pick low end hardware, you limit your programming
> choices. When you increase volume, you can afford to go with a custom
> solution.
I wasn't referring to "MMI Panels". I see that as a different market segment with a lot of differences between them and PCs besides just price. They are designed to be something any competent industrial electrician can troubleshoot and replace (just like a PLC). That's more of a "system" feature rather than something software alone can give you.
I was however referring to the segment at the bottom end of the market where an actual PC is required for some reason. You will notice that there is very regular discussion here on how to use VB (or Delphi), or even (shudder) Excel as an MMI development system. The usual reasons given are the need for a programmable system that has low capital costs for the development software and (often) royalty free run times.
There does seem to be a demand which isn't being met by existing systems for some reason and which an open source solution may fit. This isn't something I would have a need for myself, but I can't but help noticing people asking for something like it.
> Besides, the main hurdle to open source in automation is that there isn't
> any large body of open source automation code out that people want to use.
> Sure, there are dribs and drabs here and there, but not enough to make
> anyone go "Ooo! If I use this code it'll save me lots of time!"
<clip>
However, that isn't the only way for something to arise. I see a more likely origin to be where someone finds a software development system which was intended for another application but is fairly close to what is needed for a useful MMI development package. All that may be needed is to add on a few GUI widgets and other minor bits (strip chart, etc.) to get something that is good enough for a lot of purposes (or at least better than VB).
I can't give you an detailed example of how to do this, as I haven't been doing any research on something I don't need. However, building user interfaces quickly and easily is a fairly common software development task, so we shouldn't be surprised to find something that fits the bill.
************************
Michael Griffin
London, Ont. Canada
************************