Switching brands

V0N_hydro

Member
Join Date
Sep 2010
Location
lower mainland
Posts
560
We're considering switching PLC brands. We are considering Omron, Siemens, Allen Bradley and Automation Direct. We have virtually no experience with any of the above brands, and have only heard that Siemens are good but the software can be confusing, and that allen bradley is easier than siemens but the most expensive.

As long as the programming software is nice, I don't mind confusing at first. I probably heard that from someone who wasn't a programmer.

We have to bid to get our projects and nobody else is using allen bradley, so they're probably to expensive for us.

Projects generally have 500-1000 IO, of which 80% is 'in the field' so comes in to the PLC with modbus over ethernet on fiber.

Also have heard good things about codesys but am not sure what PLCs and remote IO solution to use that with yet.

Anyone have any platforms they recommend or ones to avoid!

The only requirements we really have is that on-line changes are a must, and so is a simulator so systems can be fully tested before they go out the door.
 
Alaric's suggestion is an important factor. But if you have a good support I suggest Allen Bradley.
 
...................Projects generally have 500-1000 IO, of which 80% is 'in the field' so comes in to the PLC with modbus over ethernet on fiber.............

If that's the case I would seriously consider PLC's that supported Modbus "out of the box". From memory Seimens & Rockwell do not they require additional software/hardware. have a look at which PLC's use modbus as a "native" language.
 
Why Modbus TCP ?

I strongly recommend that you chose the field bus that is native to the PLC brand.
That would be Profibus or Profinet for Siemens, Devicenet or Ethernet/IP for AB, and I dont know about Omron.
For a project with up to 1000 i/o and many in the field, I dont think that AD is a contender. AD also do not have a real online change as far as I know.
 
Hi.
500-1000 IO is not a small project. The cost of the PLC in something like that should be a small component of the life cycle of the project.
Support during development and for the next 30 years should be what the client is looking at, not wether he can save $5K at the start.

Hi Jesper. Unless AD changed their theory of how they do things then they don't have real online editing. They just freeze the outputs at the current state while the logix is being swapped around. Can make it very interesting in a factory when this happens.

Regards Alan
 
Last edited:
Why Modbus TCP ?

I strongly recommend that you chose the field bus that is native to the PLC brand.
That would be Profibus or Profinet for Siemens, Devicenet or Ethernet/IP for AB, and I dont know about Omron.
For a project with up to 1000 i/o and many in the field, I dont think that AD is a contender. AD also do not have a real online change as far as I know.

FYI:- Omron supports Devicenet, Profinet, Ethernet/IP as well as their own Compobus and Componet protocols.
 
You write Modbus over ethernet. Yet Schneider is not in your list of brands. And that is strange since it is one of the large brands.

Is Schneider the brand you are using today? Otherwise have a look at it's Premium and Quantum family. The Unity software is good.
 
You write Modbus over ethernet. Yet Schneider is not in your list of brands. And that is strange since it is one of the large brands.

Is Schneider the brand you are using today? Otherwise have a look at it's Premium and Quantum family. The Unity software is good.

I have never seen a schneider plc in 20+ years. I guess it depend on what part of the world and what part of that country your in...
 
If that's the case I would seriously consider PLC's that supported Modbus "out of the box". From memory Seimens & Rockwell do not they require additional software/hardware. have a look at which PLC's use modbus as a "native" language.

for a project that size I would just go with native protocol. with that many points I would prefer to not have to worry about doing any translation.

if you use AB you would have to buy a prosoft card then do all of the logic to support the conversion. thats gonna cost alot more than just buying a native driver... which may even be free depending on the scada package.
 
Why Modbus TCP ?

I strongly recommend that you chose the field bus that is native to the PLC brand.
That would be Profibus or Profinet for Siemens, Devicenet or Ethernet/IP for AB, and I dont know about Omron.

Thanks for ruling out AD for us, that is good to know.

We aren't married to modbus TCP, it is just what we use now and what we are familiar with.

I agree with your recommendation to use the native field bus for the PLC brand.

Thanks for your thoughts
 

Similar Topics

Hello guys, please let me ask if you have experience the same situation like this. Inputs are steady but the outputs OTE are switching off and on...
Replies
5
Views
334
is this possible? i have a customer has has a large factory, he has 2 x 800amp supplies coming into the site and would like to switch between...
Replies
8
Views
920
Does anyone have any experience with working on piezoelectric motor control? I want to use off the shelf components to hopefully change the...
Replies
5
Views
737
Hello, I have a Ge Fanuc 90-30 system with a Cutler Hammer PM 3000 Power series HMI. Besides the HMI, the customer is happy with the controls side...
Replies
9
Views
1,004
I'm working with a ROC800 program offline right now. Normally, you can switch your TLP view between text and numbers by making your choice under...
Replies
2
Views
849
Back
Top Bottom