neilr216

MrPLC Member
 View profile  See their activity

  • Content count

    69

  • Joined

  • Last visited

Posts posted by neilr216

  8. Posted

    Normally, I don't like to post information like this because it shows how stupid someone can be even after years of experience programming. However, if I can save anyone else from wasting time on a project like we did, then I don't mind. To make a long story short, we were programming alarm banners for a SLC500 system (which I hadn't done for years) and couldn't get them to work at all. The fact that they didn't display in any way should have been a clue, but no. After hours of changing the alarm setup and trying this and that, I accidentally stumbled upon a section in the help file under startup that explains that you must tick the alarms tick box so that on startup the HMI will display alarms. After doing this, they worked beautifully ! - duhhhhhhhhhhhh!

  9. Posted

    File Name: Pinstamp File Submitter: neilr216 File Submitted: 29 May 2009 File Category: PLC Sample Code TASK: Do more with less. Write PLC code for an ancient Telesis pinstamp printer from the early 1990's, replacing a flaky ink jet printer that never worked properly Existing control system is an AB SLC500 PLC controlling a sixteen station assembly line. An AB basic module was used to communicate to the ink jet. Our options were: 1) Modify basic module code to suit ancient pinstamp 2) Find another way of doing it since we were in a hurry and didn't have enough experience with the AB system to do it in time. We opted to take an existing OMRON CQM1 PLC that we had gathering dust in the corner, and write code for the pinstamp Our part model and reject codes would be sent from the AB discretely as binary inputs to the CQM1 Using the CQM1 RS-232 port, the Telesis functions strictly as a printer with no confirmation signals sent back to the CQM1 Having installed a clock module in the CQM1 we were able to extract the Julian day and year and print it along with the model # and reject code . Not exactly the finest example of modern technology, but it works. Who said that OMRON and AB can't get along! P.S. - DM memory saved in project! Click here to download this file

  11. Posted

    Thanks for your quick response, Question #1] Sorry for not providing all the necessary information. The program that I downloaded to the SLC504 is an existing program that has been running for a few years. When converted,(for the SLC504) I ran the program verification to ensure that it is OK. So I don't believe it's the code. I'm not at work right now, so I guessed at the the SLC504 OS number, but regardless, it is a SLC504 with a DH+ port. (I can verify the OS # on Monday) What really get's me is that is that I can be online with a comparing program on the 504 in run mode and no faults but coils that should be energized are not energized. Could this be some incompatability with the backplane? (Guessing) Question #2] From memory I believe that the Panelview is a 2711-K5A8. It has an RS232 port and a DH+ port. I set the panelview as Node 2 57.6kb and the PLC channel 1 for DH+ 57.6kb node 1 What I need to know is whether I require the 150 ohm resistor at both ends or just one end? Thanks, neilr216

  12. Posted

    Limited experience with SLC/Panelview and have been unable to retrieve support information from Rockwell. 1] Adding a PV500 Panelview with DH+ to an existing control system. Original PLC processor was a SLC503 OS302C and substituted a SLC504 OS402C with DH+ port Installed processor on backplane, downloaded program - no faults indicated - in run mode - but no coil on any rung is energizing - this includes module outputs. Does anyone know what the problem(s) could be? 2] Assuming that the above problem can be solved and the processor starts working, I want to know if I need a 150 ohm terminating resistor on both the PLC DH+ end and the Panelview DH+ end? I have terminated the correct shielded cable to the correct terminals at both ends. Thanks, neilr216

  14. Posted

    I am providing this download for anyone interested in the JOKAB (Swedish) Safety PLC system which we have used extensively in the last two years. This particular application is a press with a Pressotechnik air-over-oil press cylinder and a Sitema safety catcher (catches the die shoe if it breaks from the cylinder) Light curtain inputs are dual channel category 4 & Emergency Stop & Press Ram Block in series are single channel using the Jokab Category 4 pulsed output/input system. The pulsed system will detect electrical shorts in connected safety components. Handshaking to a non-safety OMRON PLC is through discrete I/O. Safety PLC errors are configured in the software and displayed on the LED Alpha/numeric display on the front of the safety PLC. I have included the safety PLC program as well as the I/O configuration in PDF format. For further information regarding Jokab - http://www.jokabsafetyna.com/products/safetyplc/index.html Safety_PLC.zip

  17. Posted

    File Name: Omron CS1 Sequencer File Submitter: neilr216 File Submitted: 3 Jul 2008 File Category: PLC Sample Code OMRON CS1 This is an example of a sequencer using a reversible shift register instruction Easy to troubleshoot because you can see what step it is on when the sequence stops for whatever reason. Easy to add steps and not too bad to insert steps. This program example shows the ease with which you can move to a specific step in the sequence after an alarm or stoppage. Click here to download this file

  19. Posted

    I agree with you regarding your use of (your example) "Y1 connects to OSSD1 I have considered Y1/OSSD" I do precisely this when wiring safety circuits e.g Sta30 OSSD1 or Sta30 X1 or Sta30 FGR1 etc. It makes it a lot easier to troubleshoot safety circuits when you can read what the wire is and where it is going , as apposed to a number like 3328 or 1004 etc.