R
Ron Gage
Ralph Mackiewicz wrote:
>The more interesting issue here is WHY do the machines require so
>much rebooting?
>Besides specing Nematron for the project, all non-I/O communications
>were required to be DCOM based using the OPC API. What happens when
>you loose a DCOM connection? How do you reestablish the
>communications channel? Answer: you reboot the machines. Is this the
>reason for the rebooting? If yes, that has nothing to do with
>Nematron. There were other communications solutions being considered
>that had a long track history of reliable operation in GM plants that
>were discarded in favor of the "safer" DCOM route. Maybe that was the
>key mistake? Lumping Nematron into this might not be fair.
Actually, I wasn't referring to the DCOM stuff as the machines I was dealing with didn't have the ethernet drops ran yet. The only things we had for network was Profibus and an occasional RS-232/422/485 connection. There were (and from what I understand from the plant folk I keep in touch with) and still are times when the whole machine would just stop responding. No reason, no notice, no activity. Couldn't even move the mouse pointer. Power down/power up, let chkdsk do it's thing and then wait a few more minutes while Open Control opened up everything it needed
to. That is *IF* there wasn't any real hard drive damage caused by the lockup and/or subsequent "improper" shutdown...
Ahhh, the progress of moving forward... What is it, one step forward, twelve steps back?
Ron Gage - Saginaw, Michigan
([email protected])
Visit the Gastracker website: http://gastracker.rongage.org
>The more interesting issue here is WHY do the machines require so
>much rebooting?
>Besides specing Nematron for the project, all non-I/O communications
>were required to be DCOM based using the OPC API. What happens when
>you loose a DCOM connection? How do you reestablish the
>communications channel? Answer: you reboot the machines. Is this the
>reason for the rebooting? If yes, that has nothing to do with
>Nematron. There were other communications solutions being considered
>that had a long track history of reliable operation in GM plants that
>were discarded in favor of the "safer" DCOM route. Maybe that was the
>key mistake? Lumping Nematron into this might not be fair.
Actually, I wasn't referring to the DCOM stuff as the machines I was dealing with didn't have the ethernet drops ran yet. The only things we had for network was Profibus and an occasional RS-232/422/485 connection. There were (and from what I understand from the plant folk I keep in touch with) and still are times when the whole machine would just stop responding. No reason, no notice, no activity. Couldn't even move the mouse pointer. Power down/power up, let chkdsk do it's thing and then wait a few more minutes while Open Control opened up everything it needed
to. That is *IF* there wasn't any real hard drive damage caused by the lockup and/or subsequent "improper" shutdown...
Ahhh, the progress of moving forward... What is it, one step forward, twelve steps back?
Ron Gage - Saginaw, Michigan
([email protected])
Visit the Gastracker website: http://gastracker.rongage.org