ge 90-30

[rswolff]

Attention all you GE Gurus and Masters, Here's my problem. Got a GE 90-30. Its got a Horner Electrics Ascii Basic Module. Couldn't get into the program. RUN indicator would go out when I typed a Cntl-C but it wouldn't respond to any commands (?) Turned out to be a communication setting problem (i was configured as 4800,7,e,1 and port was 4800 8,n,1). Now it worked fine. Made my mod's and turned it back to run w/o any problem. Now I can't get the Basic module out of run. A Cntl-C Stops the program, but now it starts right back up. Tried setting Byte 2 in the configuration to 0,1,2 and nearly anything else. Doesn't do any good. Just so I come clean, while I was originally attempting to communicate, I tried setting all the other bytes (3-25) in the module configuration to a 1. I have since changed them back. Byte 2 is a zero but the Basic module still goes into run on powerup. So these are my questions. Is there something I'm doing wrong when I set byte 2 to 0 or 1 (either should allow the module to stop on powerup). Be nice, but expect that I don't know a blasted thing about anything GE except my toaster. If I'm not doing anything wrong, is there another method I can use to stop the thing? If no, is it possible that one of those other configuration bytes is a GE special mystery undocumented function that restarts the Basic program on any stop? Just to weed out the people who like to answer and believe they read better then I, its not a BREAK0 problem, does not appear to be an AUTORUN problem (can't determine because the damned program won't stop). Any help greatly appreciated. I have a HE693ASC940F module. Thanks, Bob

[Steve Bailey]

Sorry, but I don't have any hands-on experience with the Horner Basic module. I've only ever used the GE Fanuc PCM when I had an application that needed that capability. Have you tried contacting Horner tech support? I've found them to be very helpful. Their website is Heapg.com On the chance that you've set a bit that refuses to clear, you could try clearing memory and reloading. Make sure you have made backups before doing any of the following! In the PLC, you can restore the CPU to its out-of-the-box condition by removing the module from the baseplate and letting it sit for a few hours without being connected to a battery. If you don't want to wait that long, you can remove the circuit board from the plastic case, locate the capacitor that retains RAM memory during short-term power interruptions, and discharge it. This all assumes that you're not configured to load the program and configuration from flash memory on power-up. In that case, I would clear the flash memory, configure it to ignore flash on power-up and follow the procedure to clear RAM. You'll know you have successfully cleared the memory when the name of the program stored in the PLC reverts to "HHP". I'm not sure if there is a similar procedure to return the Horner module to its default state. That's another thing to take up with Horner tech support. Edited November 3, 2007 by Steve Bailey

[rswolff]

i've tried most of that. One question. The information on the module indicates that BYTE 2, located on the configuration screen when you select the module, controls the Startup feature. Every time I've changed this value, I've reloaded the configuration into the processor. However, the module has not responded to this (I should be able to set this to not run the Basic program on powerup). Am I setting this value correctly? (or is this something specific to the module) The module is configured as a Third Party and has that form of configuration setup. I'll also try Horner Tech Support. I've never dealt with them. I'll withhold my opinion until contact is made. in the past with most tech support, they are not particularly interested in this type of problem. It's usually, 'works for us....sorry can't help'. its esspecially true if this is a not very well documented feature and they don't sell much of this. I'm actually pretty sure this may be an undocumented method of preventing the program from stopping. There probably is a method to turn this off, the tech personnel may not have it readily available. Thanks, bob

[Steve Bailey]

Are you cycling power to the PLC or just putting it back into run mode following the configuration change? I seem to remember that for some 90-30 modules, some configuration changes require a power cycle before they take effect. What is the part number of the module? I'll download the manual and take a look. Maybe a second pair of eyes will be able to spot something you missed. Edited November 3, 2007 by Steve Bailey

[rswolff]

cycling power. Old habits are hard to break. p/n is HE693ASC940F. It appears to indicate that Byte 2 controls the Startup Mode. A zero (0) or one (1) should keep the module from startup the program (doesn't as far as I can determine). A two (2) allows the module to start the program on powerup or a reset. The strange thing is this. I did not have the program in the module (nor did the customer). It was a running system until about one week ago, when it stopped receiving data from two devices. I setup my pc with what I expected should be the port parameters. When I entered a CNTRL-C the module run light went off, however the module did not respond to any commands. Since I was not familiar with the module, I expected that there must be some sort of protection, or that editing or actually being in command mode was being inhibited. I tried all the different settings for BYTE 2 with no success. I then entered a one (1) into each and every one of the other BYTE registers. This also had no discernable effect on the module and I set them back to zero. I attempted several other port settings and then discoved that the port parameters were different then what I expected (this is stuff for another story). I then was able to list the program (and save it of course). The module was set to program 1, and I issued an EDIT 0 command. Modified the program and issued a RUN command. Reconnected the devices and everything worked. Just to make sure everything was okey-dokey, I powered down and then up. Everything still worked, however now when I enter a CNTRL-C, the module answers back 'STOP in line (number). It then sends 'READY' and then restarts the program. I can now no longer stop the program. It may be because of the EDIT 0, or something else, or a combination. For the life of me, I can't fathom why anyone would make a module that effectively can't be stopped. I'm going to try Horner by email and phone. I like to resolve this so I can support the system properly. And by the way, I've also got a 90-30 with a COPRO module so I'll most likely have some questions on that too. Thanks, bob

[Steve Bailey]

After looking at the manual, I agree with you that entering a value of zero or one into byte 2 of the PLC hardware configuration should keep the module from running its program following a reset (power cycle). I would expect that if you put a zero into byte 2, the module should be waiting for you to enter a <SPACE> following reset. If you put a 1 into byte 2, the module should power up in command mode, ready for you to edit or whatever. If the program that the module is executing contains a BREAK 0 command, changing the value in byte 2 would appear to be the only way to stop program execution. It has also been my experience that Horner manuals are not paragons of clarity, nor are they free from errors. All the more reason to take it up with their tech support. For your GE Fanuc PCM module, I own one and have a 90-30 to install it in, so I can probably be more helpful with your questions on that.

[rswolff]

many thanks, I feel that way about most tech manuals. I'll probably go slowly on the PCM. The problem is my client has no records or printouts of the code inside. I don't want to do something incorrectly and then disable a running system. I normally have a free hand once the system crashes. That being said, I normally press them to allow me to start backing up not only the plc code, but device configurations, basic code (they have not only the horner as well as a pcm, but several basic modules in a series 6) A great deal of their equipment and interfaces are so old there is no direct replacement. Its particularly difficult when I don't have the original application, or in one case, the actual hmi development software no longer exists in order to view the source code. again, many thanks for the help bob