bwhinch

MrPLC Member
  • Content count

    18
  • Joined

  • Last visited

Community Reputation

1 Neutral

About bwhinch

  • Rank
    Sparky

Profile Information

  • Country Canada
  1. Unclear on OTE OTU instructions used together

    It's been running for 16 years, however I don't think it uses that logic. According to the people who use the equipment regularly that belt always runs, only the main disconnect stops it. If I'm understanding everything, rung 68 doesn't have a purpose? Maybe it is an unfinished feature. The reason I am worried about it is because I'm tasked with adding a condition that would stop the belt.. So the OTU not really doing anything would make my life easier. The N15:101 integer of 3 is some sort of recipe value, it doesn't change for our usage.
  2. Unclear on OTE OTU instructions used together

    Yea Michael, the OTU and OTE are both enabled by the same N file. If I can import this picture correctly. Joe, in the image there is only two references to the output bit. My confusion is why the OTU instruction is even necessary, if there is no OTL instruction to latch in the first place. My understanding is if the value in the N file isn't equal to 3/4 it would disable the bit?  
  3. RSLogix 500/ SLC-500 I have this program where an OTU instruction unlatches a bit that's addressed to a VFD's emergency shutdown over devicenet. The next rung uses a OTE instruction to energize that same bit. I'm having trouble understanding if those are suppose to work together, and I can't seem to Google the right words. My background is DeltaV, I'm new to PLCs. Unfortunately I'm not able to test the program, I just expected to see a latching and unlatching pair.
  4. Thanks for the added tips Joe.
  5. I'm not clear on this step, I don't see those options in FTView or RSLogix 500. This sounds like my issue then... edit: Oh, I see my mistake now. Thank you so much for both your help. The device shortcut had to be named cpu4 because the diagnostics/error log at the bottom of FTView was spitting out some message about not being able to find [cpu4]::N7. This is all new to me, I won't be forgetting this!
  6. Does the device shortcut name matter, I'm not clear its purpose? I have right-clicked on the Ethernet driver and added a device with IP in both the local and runtime tabs. And clicked apply to the previously mentioned device shortcut. I just noticed that if I make a 2nd Ethernet driver, it auto-populates with a lot of our equipment IPs. Except for the SLC that I am looking for, which I have verified again is active. As a side note, what version of windows is your virtual machine with FT View Studio. I have a laptop running Windows 7 64-bit which only lets me import a PanelBuilder 32 into FT View if I remote desktop into the W7 64-bit machine via my main W10 machine. I think it is because FT View maybe running in 32-bit mode over a remote desktop connection...
  7. SLC 5/05 CPU 1747-l552 32k
  8. Is there anything that I need to configure seperately in RSLinx Classic then? I have added the ethernet drive with the correct IP address to the PLC but I am still not able to connect when testing the converted HMI. I don't have something configured properly, but I can't figure out what. I can ping the IP, it is valid. I have RSLinx Enterprise drivers setup in both the Design (Local) and Runtime (Target) tabs.
  9. Ok thanks, I had seen configurations for equipment 1 and 2 and thought it auto-sensed it.
  10. The issue is I can not see the plc or hmi in RSLinx Enterprise, however I can see them in RSLinx Classic. 
  11. So I am following this procedure,  https://literature.rockwellautomation.com/idc/groups/literature/documents/ap/2711p-ap001_-en-p.pdf and I am stuck on page 53 of 102. Step 3/4, I can't see my controller under the ethernet driver. If I close FactoryTalk View Studio, and open RSLinx I can see the controller and existing field HMI fine. It seems like I am missing a step that I can't find in the guide. We have 4 pieces of equipment with their own controller and HMI. I am able to see the controllers for equipment 1 and 2, but not 3 or 4. And 4 is what I am trying to connect to, in order to test out the converted hmi program.
  12. Ok, so the newer software does a better job at creating a small save file. Thanks,
  13. Data file word count is still the same. It's not a big deal, more of a curiosity. Thanks.
  14. I've done a cursory glance, it is a fairly large program. Same number of LAD files and approximate length as far as I can tell.
  15. I'm attempting to make a backup of a program, complete with comments. I go connect to the PLC over Ethernet, and select Use Upload File to merge the comments from an original copy of the program. After that, I go file-saveas to backup the program. However the new saved file, complete with comments is only 134 KB, and the very original copy of the program is 230 KB, from 2003. Is there a reason for this, the program hasn't shrunk in size, only minor tweaking of some span calibration numbers.