Joe E.

MrPLC Member
  • Content count

    1081
  • Joined

  • Last visited

Community Reputation

145 Excellent

3 Followers

About Joe E.

  • Rank
    Propeller Head

Contact Methods

  • Website URL http://

Profile Information

  • Gender Male
  • Location Harrisonburg, VA
  • Country United States

Recent Profile Visitors

7149 profile views
  1. I can simulate timer

    Good catch. One comment says "50msec" while the other says "100msec". Either way, it'll be too fast to see with the software. I would still expect to see the value of bit Q100.00 displayed the same throughout, though. Weird...
  2. Factorytalk password

    Hmmm... The simplest thing may be to just use Excel's RAND function to generate a series of random numbers to populate a look-up table in the PLC. Here's one idea, inspired by your desire for it to be random digits: https://www.geeksforgeeks.org/pseudo-random-number-generator-prng/ It was fairly straightforward to implement in Excel but I don't have a PLC on my desk any more to make sure it yields the exact same numbers. You'll have to do some manipulation (other than rounding/truncating) to make it always be 4 digits without leading zeros if that's important to you. You would also not be able to use the user administration that's built into the HMI. Do you have the source code for the Siemens HMI to take a look at how they did it? If you're using the runtime security functionality built into HMI, I don't know of a way to automatically change the password every day...but that doesn't mean it can't be done.
  3. I can simulate timer

    Not sure what platform it's emulating, but the NC of T0000 may be a problem, depending on what status of the timer it indicates (done, enabled, timing, etc.). If it means the timer is done timing, that looks like an off delay time function. The fact that Q100.00 looks like it's on in the output instruction of the first rung and off in input instructions is suspicious, like the simulation isn't properly running. Or the output is forced. Or something else...
  4. Factorytalk password

    At a previous employer, the password was the Julian date (day of the year) of the preceding Sunday. One of the 3rd shift maintenance guys would go around every Sunday morning and change the passwords. It wasn't reliable because sometimes he'd be too busy or he was out. I ended up automating it. Are you looking for an algorithm that you can implement in the PLC and in Excel so someone with access to the spreadsheet can look up the password? Or do you want the PLC to calculate the password and have it show up automatically in Excel? The first option won't be difficult if you keep the date & time updated in the PLCs. The second one will require a data connection to the PLC which won't be nearly as straightforward if you don't already have something like that in place.  
  5. BOOTP/DHCP

    I didn't save the bookmark, but I downloaded a similar tool from Phoenix Contact that seemed to work better and more reliably than AB's BOOT/P. I used on Windows 7, though, not Win10. It's not at all unusual to have issues with BOOT/P. I usually use it in a virtual machine with a USB network adapter connected directly to the VM and all of the VM's other network adapters disabled and disconnected. That sometimes works...
  6. Connect to an AB Logix5555 via 1756-ENBT?

    As a client to do what? What exactly are you trying to accomplish?
  7. TCP connection

    If you're trying to roll your own from scratch without using their native protocols, you're way beyond anything I can suggest. I know the Ethernet/IP and CIP standards are handled by ODVA, but they're not free and they're going to be a big deal to implement properly. I *think* both AB and Siemens PLCs can be Modbus masters and the Modbus TCP standard is a lot more open (and less rigidly defined) than E/IP and Profinet. And that arrangement may not work for what you're doing (I've only been peripherally involved with a Modbus system and it didn't use Modbus to talk to the PLCs but to other auxiliary devices, so definitely don't take that to the bank).  
  8. TCP connection

    I don't know the protocol, but I know you can read/write any tags in the PLC. Are you wanting a PC to be able to control physical I/O directly? If so, this is likely not the most cost-efficient way to get I/O onto a PC.
  9. TCP connection

    If all you want to do is display the current status of the I/O, I would seriously consider using AdvancedHMI. It's a plug-in into Visual Studio. It's written in Visual Basic, but the library may work with C/C++ too. The software to create a PC-based HMI is free. I tested it once with a CompactLogix and it worked well. I installed the free version of Visual Studio and imported the AdvancedHMI solution per the instructions. After that, it took me less than 5 minutes to have a tag displayed on the PC.
  10. Connect to an AB Logix5555 via 1756-ENBT?

    At my previous location, I did the same thing...until IT updated our network and group policy settings. At each update, the Ethernet/IP driver was less and less likely to see the devices until it finally stopped finding anything, even if we were plugged directly into the device. At that point, I just stopped using it altogether and always use the Ethernet Devices driver. It's a bit of a pain to type in the addresses manually, and you have to know the addresses ahead of time, but that's what we have to do here.
  11. RS LOGIX 5000 V15

    To view routines in FBD, SFC, or ST, you will need a higher license of Logix 5000 or a language pack add-on. With the add-ons, you can buy them individually or as a multi-pack. The multi-pack is more expensive than each individual language but far cheaper than buying all of them individually. You only need the language license to look at the code. You can upload/download without it. It's possible you have a language pack license already. Were you able to open them before? If so, try to find the activation certificate for your language pack. If you can't find it, reach out to Rockwell and ask them what to do to re-send the certificate so you can re-host it.
  12. Without knowing the IP address, it's going to be tricky. In this case, the serial port is probably going to be simplest method. If the 5/05 is at factory default settings (DHCP enabled), you can use Rockwell's BOOT/P utility, or one from another vendor (I like the one from Phoenix Contact better) to set an IP address. If it doesn't have DHCP enabled, you can try to use a program like Zenmap to run a ping scan but that gets really cumbersome if you don't know the subnet range it could be.
  13. Connect to an AB Logix5555 via 1756-ENBT?

    Ok. What driver in RSLinx are you using? When you open RSLinx, there will be a driver called "Linx gateways, Ethernet". Don't try that. Instead, add a driver. Either use the blue "configure drivers" button in the toolbar or go to Communications -> Configure Drivers in the menu. Under "Available Driver Types", select "Ethernet devices" and click "Add New...". Name it something (or keep the default name) and click OK. In the dialog box that pops up, there's a place to map stations. Enter the IP address of the PLC and click OK. Select the new driver in the left panel of RSWho and the PLC's IP address should show up to the right. It may take a few moments for it to make a connection, but that *should* work. I've seldom seen it not work. If it doesn't, try another Ethernet patch cable. Believe it or not, I've had a bad cable allow me to ping but not communicate. I banged my head against a machine for a LONG time once trying to get it to talk and finally replaced the cable out of desperation and it immediately started working. I then cut the ends off of the Ethernet cable...
  14. Connect to an AB Logix5555 via 1756-ENBT?

    So: PLC: 192.168.1.100 PC: 192.168.1.99 Computer: 192.168.1.105 That should work. Can you ping the PLC from your computer? Exactly what trouble are you having connecting to the PLC?
  15. Connect to an AB Logix5555 via 1756-ENBT?

    In general terms, your PC and the PLC have to be routable to each other. At its simplest, they should be connected to the same physical network with unique addresses on the same subnet. See this link for information about subnetting: https://www.lifewire.com/internet-protocol-tutorial-subnets-818378 In most settings I've worked with, we used a subnet mask of 255.255.255.0, meaning that the first 3 octets of the IP addresses had to be identical. We did have a situation once where we used 255.255.254.0, allowing devices with addresses in the 10.130.32.* range communicate with devices in the 10.130.33.* range. That was ultimately eliminated via the use of VLANs in the managed switches (all done by our IT group, not us). So... If your PLC is at 192.168.1.50, your PC will need to be set to 192.168.1.x, where "x" is an unused address on that physical network. Set the subnet mask to 255.255.255.0. Set the default gateway to 192.168.1.1 or leave it blank. Our standard practice was to allocate the higher values of the last octet (like 240 and above) for static assignment to laptops and virtual machines. Those addresses were reserved in all subnets (it was a messy disaster in that plant, so we had several subnets in use).