bgtorque

MrPLC Member
  • Content count

    34
  • Joined

  • Last visited

Everything posted by bgtorque

  1. Hi all. I have an analogue level sensor (0-10V) that I am bringing into a CompactLogix L32E controller. We are using PanelView plus 600 HMI screens to view the channels. I would like to show a rectangular gauge with a few marks on for alarm, trip, nominal fill levels etc and have a a different colour rectangle (representing the fluid) scale with the sensor output to show a visual of where the oil level is. I am scaling the output in the PLC to give me a percentage percentage fill, so I know if the fill level is at 53% for example. Can anyone help to point me in the right direct to achieve this in FactoryTalk? Thanks for your assistance.
  2. Thanks for your help on this. It seems that this will only represent the fill at two given threshold values (ie if 25% and 50% fill) My output is scaled at 0-100% at would like to show anywhere on the scale as being filled, like 53% for example?
  3. I have a HMI display that gives the channel name (It's simply a text box) and then reports back the value, such as the oil temp as a tag from the PLC. What i'd like to do is have the channel name displayed as default, and then be able to press it and have further text display (the wiring diagram page, location) over the top of the channel name for maybe 5-10 secs and then go back to the channel name. How would be the most efficient way to achieve this? Two GoTo buttons? How would I achieve the timeout and back to the channel name? Thanks for any thoughts.
  4. Is there anybody that can give me a bit more guidance on setting up parameter files that will use logic to determine which tag is used?
  5. I am brand new to PLC / HMI programming and have inherited a system by the previous engineer. I think I pretty much get the gist of the system as it is but am taking the opportunity to try and refine the HMI as I learn (things like getting consistent fonts and alignments between screens). My question really is that we are monitoring various hardware channels from a test rig (pressures, temperatures, vibrations, etc) and this are grouped in their various components on individual screens (motor, gearbox, lube system, etc). Each channel is monitored by the PLC and we alarm and trip with high and low limits. We have all of the individual hardware status screens accessible by a status index (menu) screen, this top level menu screen and all of the individual status screens have an alarm lamp and a trip lamp at the top of the screen that lights up and flashes if we alarm and trip on any single channel, regardless of which screen we are in. We can then press the lamp and it will take us to the channel that has tripped. Of cause, going into an alarm or trip condition can then lead to other channels following suit. To aid diagnosis of any problems, pressing the alarm lamp will take you to the latest channel that has gone into alarm. In the event of a trip, pressing the trip lamp will take you to the first channel that tripped. Thus you know the last channel that went into alarm before you tripped and the first channel the tripped. Currently it is configured such that in reality there are multiple lamps that sit one on top of the other (looking like just one lamp) and each one is mapped to an individual channel (thus as many lamps as there are channels!). When configuring this in FactoryTalk you have to drag out each lamp to change or modify behaviors or tags. To make a long story short, is there are way to map multiple tags to a single lamp and keep the first out/last out logic as i've crudely described? Also, when I say lamp, I mean a button that say's "ALARM" or "TRIP" and blinks orange or red if channels go above or below high limits and are then pressed to take you to the hardware status screen that shows that individual channel. Thanks in advance.
  6. I've been having a bit of a look at parameter files and must admit i'm still unsure as how to perform this alarm and trip functionality as described above? Also, I cannot seem to locate ViewMe-UM04F-EN chapter 25? Can anyone kindly walk me through the first few steps? Thanks, Ben
  7. This looks interesting. I will have a read around this subject to see if I can understand how to implement it. I'm completely green on this software (with no training as of yet!) and may be trying to run before I can walk. These alarm and trips are pretty much visible on every screen (bar the home screen), so i'm keen to button down how they will operate. Thanks again!!!
  8. Also, looking in my library I can see two History screens (640x480 and 800x600), I am using a PanelView Plus 600, so I think the screen resolution is 320x240? This might be useful additional screen to incorporate, but I do need to keep with the system as I have tried to describe above. Thanks
  9. Wow, thanks for the speedy responses from you both. What's nice about the current system is that when you press on the alarm or trip button, it takes you to the status screen that shows that sensor that has tripped first or alarmed last, depending on whether you pressed the alarm or trip button. With he history screen, the first channel to trip will cause many more channels to go into alarm and probably trip, and thus the first out could well be buried under any number of subsequent trips. Also, by going to the status screen you see all of the relevant channels to that device, diagnostically this helps immensely.