Search the Community

Showing results for tags 'status'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Found 5 results

  1. I'm looking for some general information about different types of vibration/temperature sensors. What type, brand, model number, etc. will best fit my application.  Scenario: I want to monitor the vibration and temperature of multiple motors and gearboxes for a large overhead conveyor system. If an oil leak occurs and temperature increases, I want to see a temp. alert via a HMI. If a something mechanical fails, I want to see a vibration alert via a HMI.  I've looked into sensors that stick to the outside housing of the motors or gearboxes via a magnet. My concern is justifying the temperature readings. How accurate would a sensor that reads an "ambient" temperature be (compared to a thermocouple on the motor coil itself or some sort of probe)? Also, would the location of the magnet  on the motor or gearbox drastically affect the temp. or vib. readings? Has anyone had success with a similar setup? If so, what devices did you utilize? Are these systems truly beneficial?  I'm currently considering Banner's wireless products...
  2. Hi, Iam new to schneider electric PLC drive programming and also to canOpen communication. I have an LMC058 PLC and there are three Lexium 32A drives connected via canOpen which inturn controls three servomotors. My question is how to find/ read hardware limit status of the axis in which limit is connected to a digital input pin of the drive. Even though the axis is properly working by configuring the digital input pins we are unable to get the digital input status of the drive. In the drive manual its given that the digital input status can be read from canOpen address 3008:F(hex) we dont know how to read the status during run time in the program . Can any one advise me how to read that address. I tried SDO_read function but its giving me error(canOpen network id Unknown). Thanks in advance.
  3. S7-300/400 Status to Wonderware

    I've been tasked with building several "maintenance" related HMI screens in our Wonderware application for systems running on S7-300 and S7-400 PLCs. I'd like to provide an overview of general PLC status for all PLCs, displaying this type of information: LED StatusStatus of Communication to WonderwareI/O FaultsModule faultsetcFirst on my list was LED Status. I found a Siemens tech document describing how to determine the status of each LED on the processor via PLC programming, but it occurs to me that it's pointless to do so for the Run or Stop LED's - if it's not in the Run state, then the code will not execute, therefor the HMI will always display a healthy status for those two LED's. I'm referring to a Siemens document entitled "Programming Example in Ladder Logic, Getting the Status for the CPU LED Indicators." It would be nice to be able to indicate if a PLC was faulted/stopped. Does anybody out there know of a way to do this with Wonderware? I'm fairly new to Siemens and Wonderware (mostly AB and iFix experience), so detailed answers will be much appreciated!
  4. I have had a GE 90-30 CPU331 in my house for 17 years with no trouble at all. I have a problem that I have never seen before. I was editing the program using LM90. I don't know what I could have done in the program to disable an output. Just 1. All the rest of the points in that group on that card still work. I swapped cards with no difference. All of the elements of the rung are true (highlighted). The output is not on or highlighted. The nickname over the output has ONE letter highlighted. The bit in the reference is "0" and is highlighted or "grayed out" (the cursor is not on it). I searched for coil conflicts. I am using this output contact lots of places but only one output. The logic is working correctly when I use another output or %M. This is an isolated output which needs to be in this group (moving it would be awkward). What does a "grayed out" reference bit mean?