FuLcRuM

MrPLC Member
  • Content count

    6
  • Joined

  • Last visited

Community Reputation

0 Neutral

About FuLcRuM

  • Rank
    Newbie

Profile Information

  • Country United States
  1. 90-30 change analog signal to actual values

    Didn't think about converting it to internal on the PV, that may work. The PV is new, only reason it was chosen is because we want a spare for another piece of equipment that has a similar setup. This new system is designed to run without the screen if needed, the other machine requires it to run so we wanted a backup.
  2. Hey guy's got another question for you. This is on the same system as my last question (331 CPU). We have 5 PH meters that we are sending a 4-20 milli amp signal to an analog card in the PLC, it's reading an INT number between 0 and 33,000 for a PH reading between 0.00 and 14.00. Using the Panelview I'm able to convert that signal to the actual value that the meter is displaying (divide by 2300). The problem I ran into is that for logging on the PV It won't let me modify or convert the data so I just get the raw numbers (0-33,000), which is not very helpful. I tried adding some logic in the PLC to do the conversion but ran into some problems, I took the analog input, did a MOV_INT to get into a %R then did a DIV_INT (2300) to another %R that I then read with the PV, problem is it won't display anything after the decimal, so instead of getting a PH of 6.44 I just get 6. Closest I could get is to divide by 23 to get 644 and log that, but id really like to get the correct output. I suspect this is another issue with using an old CPU (331) vs a newer one. I see some other options in Proficy (DIV_REAL) that generate errors that my CPU doesn't support them that are probably the fix for this. Any suggestions or other work arounds to get a good PH signal?
  3. 90-30 not accepting inputs from Panelview

    I'm pretty sure we have 8.40 on the "new" 331 we just used and it's having the same issues as all our others, so personally I don't see any benefit in buying the PROM's. If a whole new CPU fixes it id rather go that route, but unless it's free it's not likely I can get management to go for it, as long as stuff is actually still working they don't want to spend money on it.
  4. 90-30 not accepting inputs from Panelview

    Thanks for your help. I have contacted the local rep and was told I needed a support contract to get any updates/upgrades. I guess they just don't want to bother with us or don't know any better. As far as my buttons I guess I'll just parallel the Panelview buttons in the logic and do it that way since it works. I'll keep working on getting some upgrades in here, I'll have to look more into the trade-in idea.
  5. 90-30 not accepting inputs from Panelview

    The buttons I'm trying to copy are Momentary Push Buttons, since they should be "Normally Open" I figure the HMI could send a closed signal and it would not be overwritten since the button itself is not sending any sort of signal while at rest. When I did this on my test PLC in my office it did work like this. Obviously I can't change a switch since it will be sending a signal in position 1 and in position 2, I am however monitoring all the switches and the HMI displays their current status. I have basically done as you suggested and paralleled the logic with my "Virtual" buttons, but like I said I didn't want to go through the whole program and do that if I didn't have too.
  6. Hey all, I've found some good info on these forums before and was hoping I could get a couple specific questions answered. Not sure if I should just put them all in one thread or start multiple. What I have: 90-30 331 cpu ver.8 firmware I believe AB Panelview Plus 1250 CMM321 ethernet card Kepserver Enterprise V4.170 Proficy ME V5.50 Build 3655 A little background on me: I am entirely self taught, I started messing around with Proficy and the logic of one of our machines after doing a kiazen event on it and determining there was room for improvement in the programming. We had the Proficy software but none of our maintenance guy's knew how to use it, they were all still using the old Logicmaster DOS software. I am the I.T. person here at my facility so I'm very familiar with computers and can usually figure out most software pretty easily, I have reprogrammed the original machine extensively and made it run a bit faster. Since then I have trained all the maintenance guy's on Proficy and helped work on several other pieces of equipment. We are mainly a GE shop but do have a couple AB Micrologix, Omron and other PLC's around. Since I have had no formal training my terms may be a bit off, I've tried to pick up as much as I could from the maintenance guy's and help files so hopefully it's at least understandable. First, I have noticed that if you are in programmer mode in Proficy and change the logic, say add a rung or delete an input or something that sometimes the whole rung will not work. The rest of the logic is fine and it will show equal in the PLC and PC but it just ignores that whole rung. The only way to fix it is to put the logic back how it was then it starts working again. I've seen this happen on several different PLC's and have just got in the habit of editing the logic offline then downloading my change to the PLC. Is this some sort of bug that is common? I've tried searching online and here on the forums but haven't found anyone with a similar problem. Is it something I'm doing wrong or a configuration I have on my PC or in Proficy maybe? Second, we have recently setup a new PLC with the hardware I listed above and are still trying to work out a couple of the bugs. The last problem we have is actually getting buttons pressed on the touch screen to work in the PLC. I initially set the touch buttons to the same Input address as a real PB that is on remote panel. The purpose here is to be able to control everything from inside an office on the Panelview but also be able to go down to the floor and manually start/stop equipment as well. If the PLC is in RUN mode pressing the touchscreen does nothing, however if I stop the PLC pressing the touchscreen does seem to work (shows up in proficy as a button press). To get around this I have made "virtual" buttons with Inputs that are not in the used range and added them to the logic, now when I press a button everything works as expected. I only setup 3 buttons this way and would prefer not to have to do them all like this. I also have a test PLC in my office that I used to get the communication between the Panelview and GE to work, in that program I did the same thing (used real Inputs from real buttons) and it worked fine, so why did it not work in the real project? On a somewhat related note, I've found that if I try and change the address of the ethernet card the "Virtual" buttons stop working, I can still read everything fine but pressing a button does nothing. I am wondering if that is why the "Real" buttons don't work in the first place. We did move some of the cards around while wiring everything up so maybe the address got changed then. I wasn't present for the wiring up of everything I only started helping once the PLC was online so I can't say for sure what happened. If this is the case is there any way to fix it other then putting it "back how it was"? Assuming it's similar or related to the first issue above. If so, I have no idea "how it was" so I can't go back anyway, unless there is some sort of history log that I'm not aware of. I realize that I've got both GE and AB hardware and software running here and that maybe the AB forums could provide some input, but I believe all my issues are related to the GE PLC and/or software and not the AB stuff, so I figured id at least try here first. oh and before it's mentioned, we have no support from GE or AB and my company is to cheap to pay for it so I can't upgrade any software or get official support from either company.