Joe E.

On the SLC 5/04, the 3-pin Phoenix connector and the round mini-DIN are both the DH+ channel. That means you'll need a DH+ adapter for your PC. The AB 1784-U2DHP adapter is very expensive and very fragile. And not repairable. I've seen them last a while or fail quickly. They just stop working. They'll power up, LEDs turn on, but RSLinx doesn't see any DH+ devices behind it. The failure is sudden and complete (it doesn't get flaky and then quit, it just works one day and doesn't the next). I've used a Prosoft EtherNet/IP to DH+ gateway module very successfully. Biggest downside (besides cost) is that it needs an external power supply. If I need to do it again, I'll probably try this: https://www.plccable.com/allen-bradley-1784-u2dhp-alternative-usb-to-data-highway-plus-dh-anc-120e/  

Ditto what Bob said and also verify your driver settings. The red "X" means RSLinx can't see it. The yellow question mark means RSLinx doesn't recognize it. Devices it's never connected to will always show both until the first time it connects, then it'll show the red "X" on top of the device's icon. Also...this seems weird....try a different network cable. I've seen almost that exact thing happen where I could ping but not connect. Jumped through all the hoops that could be jumped through and finally, after a couple of hours, swapped the cable and it just started working.

I finally got back to my desk where I have access to a spare CompactLogix. In V19, I created a new project. When you go to Communications -> Who Active, browse to the PLC and highlight it, and click "Go Online", what happens?

That's really weird....when you browse to it in RS Who from within RSLogix, does it show up?

I'm not 100% sure, but the "Set Path" may only be available while online. Try going to "Communications" -> "Who Active", and then browse to the PLC.

It's been a few years since I did much with ControlLogix (we're mostly CompactLogix and SLC500 here) and I don't have a test rig to confirm, but I'm 99% sure you can plug in the -EN2T, add it to the IO tree, and set up MSG instructions without disrupting operations.

The -EN2T is an Ethernet module and would be completely independent of the ControlNet system. ControlLogix (1756-*) supports "RIUP", Removal and Insertion Under Power, so you can pop the -EN2T into the chassis and add it to the IO configuration without stopping the PLC. What are you planning to do with the module? If it's just for PC, SCADA, or HMI access, it doesn't need to be in the IO tree at all.

Yes, you need to compile your new MER file to match (or be lower than) the ME version of the PV+. Also, pay attention when compiling the MER file. The utility has a check box that lets you allow/disallow decompiling. In some versions of View Studio, it was set by default to NOT allow decompiling. That changed in a newer version. I don't remember at which software version it changed, but you should verify that setting.

The PanelView Standard user manual refers to the installation manual for battery replacement instructions. See here for the PV600: https://literature.rockwellautomation.com/idc/groups/literature/documents/in/2711-in010_-en-p.pdf Battery replacement instructions start on page 15. the manual refers to a battery embedded in the RTC module but also refers to a battery that lets it retain some memory and presets. As far as I know, Mickey is correct that the application is stored in flash memory. If the battery dies, it just reverts to default values.

This. Use the USB stick to transfer the MER files. It's simpler and generally way faster than Ethernet. Here's a summary for how to get to the config mode: https://theautomationblog.com/how-do-i-access-the-panelview-plus-configuration-menu/ You'll want to go into Terminal Settings and find the startup options to see what runtime file is configured to run on startup of the HMI. If there is only one MER file on the HMI, no problem, but I've rarely encountered a PV+ in the wild that only had one MER on it and there's no way to tell what's actually running without going into the startup settings in the config mode. While there, also check the ME Runtime version. You'll need to know that when you compile a new runtime.

If you haven't already bought the 4M, take a look at the PF525. They have a 0.5HP 120VAC single phase model that's a little more expensive but includes the Ethernet/IP communications. To get Ethernet/IP on the 4M,  you'll also have to buy a 22-COMM-E adapter. List price on just the adapter is within $15 of a 0.5HP PF525. The 525 with its embedded Ethernet/IP and safe-torque-off is a really attractive option. It can drop into your CompactLogix project easily with no additional hardware.

I don't know if the AB website is the best resource or not. I started out in the AB world and Siemens world at the same time, working with the SLC 500 and S7-300/400. My PLC-5 experience came later. I never took a class, so my answers are just what I've learned working with them and  using their manuals. There are a few others on here who would be able to give you far more comprehensive answers. I'm not sure about tasks. As far as I know, it has a single task thread where it follows a "standard" PLC sequence: read field inputs into memory, execute code, write output memory to the field devices. The PLC-5s that I used lived in the same physical chassis and footprint as the older PLC-2, which was an octal system. That legacy carried over in some respects. I've never used debug files. I'll have to dig into them Another legacy of the older families, I think. That addressing system lets you pack 16-point I/O modules where the 8-point modules lived previously. Remember that memory used to be a lot harder to come by than it is now, so being efficient with it was a higher priority back then. Rack is more of a logical term than physical with these. I still think in my head about "chassis" instead of rack because of it. I have it broken down for myself like this: Group: 16 bits, in 2 octal words (00-07, 10-17) Rack: 8 groups (this is a logical rack) Not sure what you're asking here. When simulating code in the 5000 world, you can have the IO tree completely built but each device inhibited and the CPU will chug along just fine without faulting because the devices aren't there. In the 500 world, the configured IO has to be present or the CPU will fault. In the 5 world, the IO memory is all pre-allocated per processor, whether a device is in that location or not. In that sense, it's similar to a 5000 with its modules inhibited. You can read/write the IO while simulating without the IO being there. I've linked a few manuals that I've found useful in my journey Almost all of my work with PLC5s was in running systems, so I don't have any training resources. https://literature.rockwellautomation.com/idc/groups/literature/documents/qr/1785-qr001_-en-p.pdf https://literature.rockwellautomation.com/idc/groups/literature/documents/qs/1785-qs003_-en-p.pdf https://literature.rockwellautomation.com/idc/groups/literature/documents/gr/lg5-gr002_-en-p.pdf https://literature.rockwellautomation.com/idc/groups/literature/documents/rm/1785-rm003_-en-p.pdf https://literature.rockwellautomation.com/idc/groups/literature/documents/rm/1785-rm001_-en-p.pdf I have an installation manual (1785-6.6.1) and an addressing manual (5000-6.4.4) that I can't find on AB's site and attachments don't seem to be working right now. edit to add: Pturmel posted just as I did. I would also suggest not starting with a PLC-5, unless you're in a place where you need to support a bunch of them and you have access to someone else paying for the software license. Last quote I got for RSLogix 5 was around $10k about 9 years ago. It's likely gone up since then. My last location had a bunch of them and we actually bought some used PLC-5 CPUs to upgrade PLC-2s because we had the software and a base of spares and they dropped into the chassis. It was a fairly simple migration to get us away from DOS PCs, but is definitely not the ideal route or the path I would take for new builds or for learning.

The DN bit is indeed turning on...for  1 scan. When the TON finished, the DN bit turns on. On the very next rung, the DN bit being on turns on B3:57/1. On the next PLC scan, with the memory location B3:57/1 containing a "1", the XIO instruction becomes false, which drops the EN input of the TON instruction, which resets it. For a really good treatment of the PLC scan cycle and how to decipher what's going on, see these Youtube videos: https://www.youtube.com/playlist?app=desktop&list=PLGzS56y9k4eYr1uS3jPPxGunBTtPcS3Ez    

Sorry, I've never used Omron. I know that there are a bunch of folks on here with Omron experience, though. You could probably post in the Omron sub-forum and get some good guidance.

I'm also having trouble with the upload. Here's a link: https://www.dropbox.com/s/8mskxc5o0p9d3hi/Compression%20Bagger.pdf?dl=0  

I've never tried this, but Bob's reply sparked an idea.How about using a SCP instruction with a timer accumulator as its input and the analog output as its output? Interruptions might be tricky to handle, depending on what you wanted to happen if it's interrupted. Just a thought....

Have you verified the mA signal matches the display? Also, verify the scaling in the Module Properties hasn't been messed with.

Have you seen this? https://www.plctalk.net/qanda/showthread.php?t=134779 I'm not an Arduino guy, but there is a PLC IDE for it.

I tend to call this "Magic Math", where there's a mysterious, unexplained scale factor. I really don't care for it, but I've seen it a lot. When I do scaling, I tend to show each step of the calculation so it's clear what's going on in the future. Also, if someone changes a sprocket or sheave or motor or something, it's easy to see which number to change and what to change it to. So...that 1.38 value could have been calculated based on the engineering parameters of the system, or it could have been empirically figured out to be the magic number that gets  the desired result. If anything in the system ever changes later, you'll have to figure out how to change the number to make everything right again.

Try this. TELE QEQ.pdf

I'm not sure, but I think there's an ME Station program that lets you run ME files on a PC. But I could be totally off on that. I remember running across something back in the dark ages when cobwebs were new...

Here's a thread where a member created a tool that extracts the version information: https://www.plctalk.net/qanda/showthread.php?t=90986 Can you post your MER file here? edit: I missed where you said it was ME Station. That may not help...

I found a KB article (Access level: TechConnect) that *almost* talks about this: https://rockwellautomation.custhelp.com/app/answers/answer_view/a_id/19576/loc/en_US#__highlight It refers specifically to the -IF4 and -OF2 modules, but it may apply here too. In essence, there's a switch on the side of the module for bus or external power. If the module is set for external power and it and the base lose power at the same time, then the module will report that error to the PLC as it powers down, which causes the PLC to fault. It will still show that fault when it powers back up. That article refers to another one (Access Level: TechConnect): https://rockwellautomation.custhelp.com/app/answers/answer_view/a_id/17966 The second article refers to noise as the most likely cause, but starts out talking about 0xx79h but ends up talking about 0x300. Not sure what's going on with that...

Studio 5000 doesn't have DBs per se. You have controller-scoped (global) and program-scoped (local) tags that you can use to store data. It's a different structure than Siemens uses. Logix class processors are entirely tag-based while the Siemens PLCs are address-based, more like the Logix 5/500 processors in the AB world. If you want to organize your tags, you can create UDTs (can't be edited online, though), array tags if you need to store a lot of the same datatype, or use naming conventions that help them sort together in the tag databases.

My C++ is a little rusty, but a struct isn't itself a datatype but consists of a collection of variables that can be different datatypes themselves. Basically a function-less class. In that sense, a UDT is a struct. It can also contain other embedded UDTs.