Migrate Studio 5000 project to earlier processor?

Hello everybody!

I have a Studio 5000 project which uses a ControlLogix 5580 (1756-L82e), but do not have that exact PLC model available to test on.

The most recent ControlLogix I could find is a ControlLogix 5570 (1756-L73) which is very similar, at least enough for my testing.

My question is: My project is already developed and ready to test on the ControlLogix 5580 processor, but I don't have one available for testing. When I go into Controller Properties to try to switch processors, Studio only gives me processors from the same family / generation as the original processor in the project (5580), so there is no option to select the 5570 processor. I do not see a way to test my current project on the 5570 processor without exporting it, and developing a sort of one-off application specifically for testing, which is less than optimal. Does anybody know of a way to revert a project for an 5580 / 1756-L82 processor to an earlier family, like the 5570 / 1756-L73 processor?

Ideally I would like to test on the actual processor (CLx 5580), but if that is not possible then I would like to test the actual program on the best processor I have available (CLx 5570). The only solution I see is to build a side project as mentioned, which is less than optimal as it may introduce irregularities / anomalies into the process during migration/development, and as a general rule I always try to test as close to actual real world / typical expected conditions as possible.

Thanks!

.L5K/.L5x and hand-edit?


Obviously this will have problems if the program uses capabilities of the 5x80 series that the 5x70 series does not possess (e.g. LREALs).

drbitboy said:

.L5K/.L5x and hand-edit?


Obviously this will have problems if the program uses capabilities of the 5x80 series that the 5x70 series does not possess (e.g. LREALs).

Click to expand...

What he said, or create a new program and export/import/copy/paste. All options are dumb. If I can edit the L5X/L5K to do this, the software should do this for me. If you used unsupported types, the software should warn you and pick the correct type (UDINT > DINT).

Thanks for your replies. I agree, it seems like the easiest / most straightforward option is to export my routines / programs, and then create a separate PLC project file just for testing. Seems like a lot of work to get to a suboptimal solution, but such seems to be our industry

I did find a PLC from the 558x series to test with, so I can avoid this issue for now. I hope to find a workaround in the future as I have ran into this issue a few times and have been able to avoid it up until now!

Thanks again