Joe E.

MrPLC Member
  • Content count

    1495
  • Joined

  • Last visited

Community Reputation

232 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

10515 profile views
  1. 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.
  2. 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.
  3. Base 36

    My first thought is "Why?", but that's just out of curiosity. I've never encountered a need for that. What are you doing that requires that conversion? If you can write a routine to convert between binary and decimal, it should scale up to base x once you get the pattern figured out. If you need a tool to use manually, try this: http://www.unitconversion.org/numbers/base-10-to-base-36-conversion.html I remember doing manual base conversions a LONG time ago. There was a process where you'd calculate each digit by dividing or multiplying and carrying over the remainder. It was a little painful to do by hand but wouldn't be too awful to implement. I'd have to get my head back in that space to figure it out again, but that will have to wait.
  4. L18ERM 16#0203

    Their compatibility page says that it will go all the way up to v34.012. Series A and B start at 20.011,while series C starts at 30.016. I would probably skip ahead to v24 or 30 if it were me. Unless you have a compelling need to stay at v20. What error do you get when you try to flash it?
  5. Does the duplicate system you built have the same power supply and chassis size? If so, swap them one at a time to see if the problem stays or moves. If you swap both and the problem stays, then go through your power supply and chassis grounds. And the grounding of the analog signal shields. It's not unusual for noise to cause random weirdness.
  6. Siemens hmi

    There is an option when downloading to an HMI to allow back transfer but it requires more memory in the panel than they come with. You have to buy a larger SD card (and they're special and very expensive). None of the HMIs I ever worked with had a large enough memory card to store the project for back transfer. You can try to extract the project from within WinCC Flexible, but I'd be surprised if it's possible.  
  7. L18ERM 16#0203

    It looks like that's the embedded I/O that's built into the processor, but it can still be affected by the end cap or bad connections on the Compact Bus. Try pturmel's suggestion and disconnect/re-connect all of the modules and the end cap. With power off, of course... Here's a tech note (access level: TechConnect): https://rockwellautomation.custhelp.com/app/answers/answer_view/a_id/466339/loc/en_US When you downloaded the new program, did you keep the same firmware version? I saw a Tech Note about an anomaly in v20.11-20.12 with these processors and their embedded I/O acting funny with firmware change (access level: Everyone): https://rockwellautomation.custhelp.com/app/answers/answer_view/a_id/498109/loc/en_US There's another anomaly caused by sending a "reset" command via the AOP or MSG instruction in v20.13 and earlier (access level : everyone): https://rockwellautomation.custhelp.com/app/answers/answer_view/a_id/519749/loc/en_US  
  8. It may not apply to you guys, but there's a tech note (access level: TechConnect) about "1756-IB16ISOE Modules Randomly get 16#0204 on Power up and Download": https://rockwellautomation.custhelp.com/app/answers/answer_view/a_id/602867/loc/en_US#__highlight It's not a very well-edited tech note with some run-ons and incomplete sentences, but the gist is to flash the firmware of the modules to a different version. I'd check the release notes for the different FW versions of your modules to see if this issue is mentioned and which FW version it starts with. Then choose an older version (or a newer one if it's been fixed...).
  9. Board Mount Safety Relays

    I'm not aware of any such products. I know they go through a lot of testing and certification to be allowed for safety applications. For what you're doing, you might reach out to the safety relay's manufacturer representative to see if they could work out something like an open frame model that could attach to your board, but I would be really surprised if they did that unless your volume is really high.
  10. Since you have to replace the CPU anyway, consider the 1747-AENTR. That would turn the SLC chassis into an EtherNet/IP node that the CLX can reach pretty easily. I've never used it in the real world, but when you put the 1747-AENTR into the ControlLogix project, you can set the chassis size up to 31, which is what the extended SLC chassis maxes out at. You can then populate the SLC chassis with its modules. Not sure how well that would work out, but see if you can configure it offline. You may need to search the "secondary market" for modules, though, especially for the -ASB which was discontinued back in 2013. The -AENTR is still made, but it's "Active Mature" and list price is VERY high. What SLC PLCs are in the racks? If they're 5/05s, you could turn them into IO processors of sorts and have the CLX use MSG instructions to read/write IO with the code running in the CLX. That's far less ideal a solution, but could work without having to buy expensive hardware that you're going to replace anyway. I did a migration from PLC-5 to ControlLogix and we ended up just replacing all the IO in one fell swoop since the changes to the system were so extensive already. I'd seriously consider that option as well if it's at all possible. It may be that you can get your hands on the COMMS modules easier than the new IO modules, especially analog ones. Those things are really hard to get over here.
  11. s7-300 ethernet connection

    I've used the IBH gateway before and it worked reasonably well but initial setup was a bit involved and it was expensive. I don't know how the price compares to an in-chassis module, but it does simplify things in that it isn't added to the PLC's hardware configuration.
  12. Hmmmm....that's interesting. I've done serial to a PLC5 but not what you're proposing. I wouldn't have even thought it possible if you hadn't found the tech note. Have you been able to ask Red Lion support directly? If there's an HMI out there that could do that, Red Lion is probably it.
  13. Read rs485 data

    Hehe, wedding of the rabbit and the carp. I'm going to have to remember that one! I'm pretty sure that there are Modbus examples available for the S7, but I've never used them. I looked into them a little when I was testing Advanced HMI. As I recall, though, those examples were Modbus over Ethernet, not RS485. It's been a few years, though, so my memory may be faulty. Does the manufacturer of the power meter have any documentation or support for connecting to an S7?
  14. One thing I've learned with FT View Studio is to reboot the PC. That sorts out a lot of bugs. It's not directly related to your issue, but I took a working project and made a change to it, recompiled and downloaded the runtime, and communications didn't work. I banged on it for an hour before rebooting and recompiling the mer. That's all I did: reboot and recompile. Then it worked fine. I'm sure you've done that by now, but reboot the PC and see if anything is different. Another thing to double check is your tag syntax in the display objects. To do that, create a blank display and add just a single indicator light or numeric display. While connected to the PLC, go to the connections tab of the object properties. Click the "..." button under "Tag" next to the "Value" field. The Tag Browser will open. Expand the PLC shortcut name and then "Online". Click "Refresh All Folders". If you don't have stuff there, then there's an issue. If you do...pick an appropriate tag and "OK". Then test the display with just that object. If that works, then you can double check the syntax of the other objects and verify they're correct. Edited to add: I should have asked earlier. Is this a new project or an existing one that you're editing?
  15. When simulating/testing from  your PC, it uses the "Design (Local)" shortcut path. Have you set that?