For those who have looked on before, this is a continuation.
A process tool that sat for some time in storage.
A GE 90/30 311 to control the pumps, valves, and process sequence.
A KEP MMI-200 24 key operator. (NO Display! Only key pads and LEDs)
On first power up while in a recommission process, the operator panel displays all the signs of a lost memory. That is, no connection with the plc and no project to be retrieved from the unit. (programming software from KEP)
"Factory suggested" Diagnostics indicatet a bad MMI-200 unit. Ahh the ravages of time.
'Sent the unit of to KEP for a once over. Returned with a new memory chip.
Refitted the unit to the tool....Exactly the same results as at first. No connectivity with the plc. Indicator lights consistent with not communication with plc
In the mean time, I have become more familiar with the 90/30 and the LM90 application. The machine works fine!, The logic/project for the 90/30 preserved in EEPROM.
But,....I have NO record of the MMI-200 project. It should not be too complicated as the interface is ONLY buttons, momentary too, if I read the logic correctly. (set bit on)
I have fitted a second serial port module (Horner XXX,,,,900) and that works fine. ( Thanks to contributions from forum members!) With that added card, I can monitor any changes that a key entry from the panel might make. There are none ;-(.
I must be missing something basic.
I have made a MMI project and loaded it into the unit. Verification returns positive. I even pulled the project from the unit into a new project to confirm that everything proceeded as intended. A- OK.
Please be advised, I have no clue about what is right, Nothing to compare to and no examples to look at. I'm only going on my "reading" of the ladder logic and trying to get the operator to do what is readily accomplished in the LM90 program. That is, perform all the programmed functions! ;-)
I've assigned the keys to the %Mxxxx references as displayed in the ladder logic. I'm not sure if this is correct. Perhaps I should be writing the keyboard presses to internal memory (%Rxxxx)
Since the %M references are not working with the MMI-220 even though toggling them in the LM90 program works a charm, It makes me look elsewhere.
What caught my eye was the final instruction in the "MANUAL MODE" block. It is a "MOVE WORD" instruction (len 2) that takes its input from LED1 (%M0505) and outputs to %R0001. The location of all the LED status bits. And registers that are set to zero on "FRST_SCAN"
32 bits being more than enough to accommodate the 24 keys available.
Looking at the MMI-200 programming software, when "write to " is selected for the key stroke operation the value entry window prompts with four zeros. IS this a suggestion to enter the entire LED status word in Hex?
AM I way off base?
You might know, bits, bytes. words, dwords arrays and strings might as well be so much babble. I read and re read, but it goes in and out untouched. I'm good at a few other things however ;-)
Examples and guidance welcome!
Cheers
Cal
A process tool that sat for some time in storage.
A GE 90/30 311 to control the pumps, valves, and process sequence.
A KEP MMI-200 24 key operator. (NO Display! Only key pads and LEDs)
On first power up while in a recommission process, the operator panel displays all the signs of a lost memory. That is, no connection with the plc and no project to be retrieved from the unit. (programming software from KEP)
"Factory suggested" Diagnostics indicatet a bad MMI-200 unit. Ahh the ravages of time.
'Sent the unit of to KEP for a once over. Returned with a new memory chip.
Refitted the unit to the tool....Exactly the same results as at first. No connectivity with the plc. Indicator lights consistent with not communication with plc
In the mean time, I have become more familiar with the 90/30 and the LM90 application. The machine works fine!, The logic/project for the 90/30 preserved in EEPROM.
But,....I have NO record of the MMI-200 project. It should not be too complicated as the interface is ONLY buttons, momentary too, if I read the logic correctly. (set bit on)
I have fitted a second serial port module (Horner XXX,,,,900) and that works fine. ( Thanks to contributions from forum members!) With that added card, I can monitor any changes that a key entry from the panel might make. There are none ;-(.
I must be missing something basic.
I have made a MMI project and loaded it into the unit. Verification returns positive. I even pulled the project from the unit into a new project to confirm that everything proceeded as intended. A- OK.
Please be advised, I have no clue about what is right, Nothing to compare to and no examples to look at. I'm only going on my "reading" of the ladder logic and trying to get the operator to do what is readily accomplished in the LM90 program. That is, perform all the programmed functions! ;-)
I've assigned the keys to the %Mxxxx references as displayed in the ladder logic. I'm not sure if this is correct. Perhaps I should be writing the keyboard presses to internal memory (%Rxxxx)
Since the %M references are not working with the MMI-220 even though toggling them in the LM90 program works a charm, It makes me look elsewhere.
What caught my eye was the final instruction in the "MANUAL MODE" block. It is a "MOVE WORD" instruction (len 2) that takes its input from LED1 (%M0505) and outputs to %R0001. The location of all the LED status bits. And registers that are set to zero on "FRST_SCAN"
32 bits being more than enough to accommodate the 24 keys available.
Looking at the MMI-200 programming software, when "write to " is selected for the key stroke operation the value entry window prompts with four zeros. IS this a suggestion to enter the entire LED status word in Hex?
AM I way off base?
You might know, bits, bytes. words, dwords arrays and strings might as well be so much babble. I read and re read, but it goes in and out untouched. I'm good at a few other things however ;-)
Examples and guidance welcome!
Cheers
Cal