BobLfoot

MrPLC Admin
 View profile  See their activity

  • Content count

    4131

  • Joined

  • Last visited

Posts posted by BobLfoot

  2. Posted

    I did see some recent FANUC Robots which had 4-D Displays on both the pendant and a remote webpage served from in the Robot Controller.  I don't recall the model and version at this time however.

  5. Posted

    1. DETERMINE WHAT DATA TYPE HISTORIAN USES FOR COMMUNICATION STATUS.

    2. CREATE A TAG OF READ/WRITE CAPACITY IN THE PLC OF SAME DATA TYPE.

    3. MAP THE TAG TO THE HISTORIAN.

    4. USING THE HISTORIAN SMC/MMC WRITE AN EVENT SCRIPT TO COPY THE STATUS INTO THE TAG AT THE HISTORIAN.

     

    OF COURSE IF THE HISTORIAN STATUS IS "i CAN'T COMMUNICATE TO PLC" THE PLC WILL NEVER GET THE CHANGE IN STATUS.

     

    1 person likes this

  12. Posted

    You will only need a single ethernet port on the Panelview if you're using a STAR or LINEAR Network topology. 

    The two ports come into play when you use DEVICE LEVEL RING {DLR}.

    If I am reading your post correctly you have three devices to convert.

    Device 1 - SLC50* to 5069-L310ER

    Device 2 - SLC50* to 5069-L310ER

    Device 3 - Panelview with DH-485 Communications to Panelview with Ethernet Communications.

    AS I think about this I might do the panelview first and use the Prosoft DH485 Ethernet Gateway.

    Then with each PLC converted you'd reprogram the Panelview tags to point at the new ethernet PLC rather than the old DH-485 SLC.

    Just my two cents.

  14. Posted

    Another "trick" I've used it to set the device dial switches to a known number 123 for example. 

    Set the IP of your laptop to 192.168.1.1.

    Use a local connection {patch cables and hub or cross over cable} and RSlinx Browse the new device.

    Using Module properties in RSLinx set the device to the IP address, Mask and Gateway you desire as the final address. And turn off DHCP/BootP.

    Power down device, reset switched to 256 and power up.

    Device should be at the final working address.

    1 person likes this

  16. Posted

    RSLOGIX 500 is last century programming and for the most part doesn't use tags.  IT uses Data Table Addresses.  You'll find booleans like B3/10 or B3:0/5 ; Integers like N7:1 or N77:17 ; Timers like T4:0 and Counters Like C5:1.  Also Floats like F8;5 and Control Registers for special instructions like R6:7.

    Professional Programmers usually applied Symbols limited to 8 characters to help identify Data Table addresses.  And also Comments limited as they were.

    Hope this helps.  If you're familiar with only with Connected Compinents Workbench or Studio 5000 stepping back to Logix 500  will be a "culture shock".

    1 person likes this

  19. Posted

    Before I post about the logic you're seeking, I want to elaborate on the pros and cons of your approach.  

    A. In your approach the operating time of all pumps is kept close to uniform, meaning they'll all need their 500 hour rebuild at the same time, they'll all fail at the same relative time.  If you have scheduled down periods and can perform all maintenance at once and tolerate the purchase of 6 replacement pump/motor units when they do start to fail.  This is an ok approach.

    B. If you use the approach where pump 1 is run more often and so forth and pump 6 is kept in reserve, being run only one time a week to ensure it's ready to go.  Then when pump 1 fails or needs it's 500 hour maintenance you cycle in pump 6 and declare pump 1 to be the spare.  This spreads your maintenance and replacement costs out over time and leaves you an always running system.

    Now on to one possible logical solution:

    1. Assuming your Ladder Logic supports FIFO Array build an array and load locations 1-6 with the numbers 1-6.

    2. When water level enters zone 1 pull array item 1 and whatever it's value {1-6} start that pump.

    3. When water level is below zone 1 {off region} Unload the FIFO of one number and reload that into the FIFO.

    SO IT LOOKS LIKE THIS TO BEGIN

    ARRAY[1] =  1

    ARRAY[2] = 2

    ARRAY[3] = 3

    ARRAY[4] = 4

    ARRAY[5] = 5

    ARRAY[6] = 6

    Then when water enters zone 1 we start pump ARRAY[1] or pump 1

    Water keeps climbing and enters zone 2 so we start ARRAY[2] or pump 2

    Water then drops down and all pumps are off.

    We FIFO UNLOAD and ten FIFO LOAD so now the array looks like

    ARRAY[1] =  2

    ARRAY[2] = 3

    ARRAY[3] = 4

    ARRAY[4] = 5

    ARRAY[5] = 6

    ARRAY[6] = 1

    Then when water enters zone 1 we start pump ARRAY[1] or pump 2

    Water keeps climbing and enters zone 2 so we start ARRAY[2] or pump 3

    Water keeps climbing and enters zone 3 so we start ARRAY[3] or pump 4

    Water then drops down and all pumps are off.

    Repeat the FIFO UNLOAD and LOAD.  

    This won't be perfectly equal but will come close to what you're looking for.

  20. Posted

    IT will be making more and more news that the Apache Logging Unit - LogShell ot Log4J2 has a major remote access vulnerability.  This is a widely used subsystem and so I am posting what I've been able to garner about affected automation products here and hope others post factual not anecdotal evidence here as well.

    Aveva Wonderware - https://wonderwarenorth.com/tech-alerts/Tech%20Alert%20-%20Apache%20Log4j.pdf

    Rockwell Automation - https://rockwellautomation.custhelp.com/app/answers/answer_view/a_id/1133605/loc/en_US#__highlight

    GE Proficy - https://digitalsupport.ge.com/communities/servlet/fileField?retURL=%2Fcommunities%2Fapex%2FKnowledgeDetail%3Fid%3DkA28a000000bzlgCAA%26lang%3Den_US%26Type%3DArticle__kav&entityId=ka28a000000c3DPAAY&field=File_1__Body__s

  25. Posted

    Just to clarify and recap.  During a download there was an interruption and this faulted the PLC.  You've done the standard troubleshooting and reset the  memory and now while RSLINX will see the device you cannot get RSLOGIX to acknowledge it as an SLC 5/03 and accept the program?

    I only worked with 5/04 and 5/05 back twenty years ago, but I seem to recall the manual calling out a procedure for RSLogix to reset a fault similiar to this.  Hopefully one of the more active SI members can help you.