Announcement

Collapse
No announcement yet.

P1000 "cpu" that allows it to act as remote IO for Productivity PLCs

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts


  • P1000 "cpu" that allows it to act as remote IO for Productivity PLCs

    I think it would be really great if we could use a P1000 based system as a remote IO base for the larger systems. The size of these P1000 units make them perfect for using as remote/field IO, but as of now we cannot mismatch base types in Productivity. Instead of using a normal CPU for the P1k, we should be able to use something like the remote slave units in the higher end series. Then the hardware would integrate seamlessly into Productivity software and we could create tags for the hardware in the same way the current remote bases work. It would also connect over the Remote IO port rather than the external port using ENet/IP. That way we dont have to futz with any client setup, or assembly instances or any of that. Just let the hardware be discovered like a normal rack, only these little P1k based systems would allow discovery when they are connected to the larger P2000 and P3000 systems. Doing this and using P1000 systems as remote for the larger systems would let us save a ton of space and would promote their use in more systems rather than needing to go the ProtosX or Terminator route.

    I mean, just look at the size difference we could have of a P1k based IO compared to adding a P2k based remote rack:
    Click image for larger version

Name:	Productivity.jpg
Views:	137
Size:	122.6 KB
ID:	119182


  • #2
    You could use a p1k and either modbus, ethernet ip,or pronet to easily communicate with another pseries cpu

    Comment



    • #3
      Originally posted by g.mccormick View Post
      You could use a p1k and either modbus, ethernet ip,or pronet to easily communicate with another pseries cpu
      I've experimented using Modbus commands over Ethernet IP with a P2K being the master and a P1K and an Ethernet Click were both setup as remote I/O. It worked great.
      Why worry? If you've done the best you can, worrying won't make it any better

      - Walt Disney

      Comment



      • #4
        While you could use them via modbus, etc, doing so means you have to use actual modbus write or similar instructions which take a lot more work and much longer to execute. If it behaved like the remote slaves do when you plug in a slave CPU then you can make tags like it is normal local IO, and address the remote IO with all the same instructions like it is local to the main base. It is quite different an experience than addressing everything you want to do from network read/write commands. Sure it works, but it isnt the perfect, seemless integration of remote IO I would love to be able to use.
        Last edited by MikeN; 11-27-2018, 09:45 AM.

        Comment



        • #5
          I can see where you are coming from and it is an interesting idea especially for keeping all your machine control on one network. Ethernet IP implicit would be your closest bet currently but the set up wouldn't be as simple and you would still have two programs to edit when you add IO on the P1 side.

          Comment



          • #6
            i like this idea MikeN, but it would be more likely they made a dedicated piece of hardware for the task. a remote io cpu for the click and for the p1000 would come in quite handy

            Comment



            • #7
              Thanks for the posts. We are in the process of adding more capabilities and remote I/O options to our Productivity PLC line so stay tuned.
              If you have an urgent issue, please contact AutomationDirect's Technical Support team at 1(800) 633-0405 or (770) 844-4200. Thank you

              Comment



              • #8
                awesome i cant wait to see what you have coming.

                Comment

                Working...
                X