machinebuilder

Up date. I have it working. Ken, I took your advice and actually eliminated the reset on error. An error did show up. It said bad address. After converting numbers and finally trying them all. It turned out I have to add 1. I was looking to write to address 6000. I had to use 6001. Funny thing, I tried that at first signs of trouble and it did not work. Not sure if I changed something other then adding the 1 before this. Also it was a series B PLC. I left the unit number at "0". The biggest help was not resetting on an error bit. Sometimes it just helps to hear others give their suggestions no matter how small it may sound. It get you thinking. This forum is awesome.

First, I do not need to do the mapping. That is only required if I was doing Allen Bradley Ethernet/Ip. Since I am doing Modbus, that is not needed. I checked with the manufacture of the servo drive, and i would have needed to specify I wanted to do Ethernet/Ip. that is an add on. But the drive will do Modbus Ehernet/IP.   Second, I will check the Unit Identifier. I tried 0 and 1 but was thinking of trying the 255. I will try that tomorrow. Third. I had someone check the label on the PLC for me to see if it was a version A or B. I was told it was B. Funny thing when i hooked up for 1st time and sucked out the plc info. it came up as A. It was hard to see in the cabinet, being the label is on the side of the PLC. I will personally check tomorrow, and if it is A, I am going to be pissed. For those who work a lot more with AB then I do, when you hook up to the plc and auto config, is it by default it says series A? Maybe that is a default thing. Well anyhow I created a new project and selected 1400 Ser B. When I downloaded for the first time. it warmed me the versions did not match. Is the software smart enough to compare? How  accurate is the software reading the PLC info?  

Thanks for the info. Yes, that rung is running continuously. The modbus address supplied are in decimal. Just for kicks, I converted them anyhow and it still does not work. I connected an Automation Direct PLC and within 5 minutes I had it working. So I would say the servo drive is configured correctly and capable of modbus tcp/ip. I hate to pull the AB plc out and have to re-wire for a different plc. Any other thoughts to as why the AB 1400 does not work over the modbus tcp/ip?   Oh tried the add 1 to the address. still did not work. Will give it a couple more trys tomorrow, then out it comes!

I need to have a 1400 series B to do Modbus. I have a series  A. Is there a way to upgrade the plc I have to series B?  So does AB only sell the latest series or my distributor sells what he has on the shelf? I hope I do not have to rip out the plc. It is wired in and in the cabinet. I went to program the machine and found out I had the wrong series.

I took a micro 800 and threw it against the wall, ridiculous how complicated they make things. Also by the time you buy the usb port, yes you have to but a port, and any add on cards you mind as well just buy a micrologix 1000 or 1100.

BITS N BYTES, this is a little off the subject but do you use the updater program that goes with that program. It downloads the updates but does not tell me where the updates are so I can run them! The update program actually checks all AB programs for updates.

I have the AB Program Updater that up dates my programs. That is fine, but where are the updates stored so I can run them? There are no settings to set where i what them stored. Would be nice you could run the updates after they are down loaded. If i can, how do I do that? So every time I start a program it pops up saying there is an update. I say okay, but then can not run the update. Irritating it keeps wanting to down load the same updates!

yea, hahaha, you better believe I am going to file this!

I can not figure out how to fill out the setup screen for modbus/tcp/ip. I am using a 1100. the device I want to connect to is a protos valve bank. It has 8 inputs and 8 outputs. It states it is 40001:0-40000:7 for the inputs and 40270:0 -40270:7 for outputs. for my logix setup top section I used B3:0 in the top section. i put the address of the device in the Multihop. I do not know what to put in the other blanks. I chose channel 2, but that channel does not say modbus tcp/ip. Am I using the wrong PLC model? In the bottom portion of setup i tried to use the 40001:0 and it would not accept that. I am at not atwork to get more info. I just found this website.

I finally got it to work. I ended up starting over then making 2 MSG blocks, one to receive the inputs and one to turn on the outputs. That was a challenge in itself to get the numbers right. attachment=14087:Send to Protos Outputs.png]

I never did get the communications to work properly. there is not much of a program at this point, just the rungs for the MSG. If you do get the Protos to work, let me know. I am not on planning to use it unless someone can get it to work. Looks similar to the wago system. Actually, the cards work with the Wago Ethernet System. The cards are less expensive then getting them from Wago. I was hoping I could use the Protos Ethernet module as we, but that is not the case. A lot disappointed the protos is not working out.

Okay I put those numbers in the MSG setup, but when on line it shows ER for the msg block, there is no communication between the plc and Protus. Wonder if something with the I/O. I use C-More panels with the 1400 and I do not even have to select enable modbus to make it work, it just works. I also am using the same version of RS500. Now that I think about it, when I use a C-More, I do nothing. That is because there are tags to be made. How do I relate the Protus I/O to the plc? There are no tags so how would I map the I/O to the plc? I went and changed the setup file to Channel 1 integral. but but b3:0.0 in both addresses, which I think are wrong and now I see commications between the two. Not sure this I/O is going to work.

I can not figure what to put in the This Controler-Communication Command I have 500CPU Selected and in Target device, data table Address I just threw in B:3.0 and I see the two device talking, but the addrerss is wrong. I can not work the Protus I/O. Channel - 1(Intergel) Communication Command - 500 CPU Read Data Table Address - N7.0. Size in Elements - 1 Target Device Message Timeout - 33 Data Table Address - ? Local/Remote - Local Routing - RI20:0 Mulithop, the address of the Protos I tried Channel 1- Modbus TCP/IP and get no where, have no idea what to put in the fields. If it is going to be this difficult, and can not be figured out, I won't use AB for this type of application. I never had such a hard time trying to use modbus with other brands. wow Would not be so bad if they had help files that really did explain these things.

I did change to a 1400. Are you saying I do not use or fill out the boxes under Chan1-Modbus? Do I select Chan1 under Channel Configurations?

wow there is more to setup as well. Typical Allen Bradley. I never had to go through so much to use modbus/tcp on other brands. there is another window chan-1-modbus to fill out too. wow

Thank you guys, That would explain why there is not a Modbus Tcp Enable choice under Channel 1. Since I have you guys here, Can you help me fill out the setup file? I am using a Protus I/O unit. It is showing me 8 inputs 400001:0 - 400001:7 8 outputs - 402049:0 - 402049:7 In my setup I have Channel as 1. I did the setup in the channel config and selected Modbus Tcp blanks are: Modbus Command Data Table Address, I have B3:0 there Size In Elements For Target Device Message Timeout is 2 MB Data Address (1-65536) 1 is in there Unit Identifier has 255 in there Modbus Address has 1 in there Routing Information I have RI20:0 Ethernet Address. has client in there. should i put the address of the Protis in there? This is my first time doing modbus tcp with Allen Bradley.

thank you. I will