Logix L62 V13 - SEW MovfitFC (Tech)

0151paul

Member
Join Date
Dec 2017
Location
Liverpool
Posts
15
Hi all,

I've come across an issue when trying to integrating an MovifitFC drive onto a L62 processor using V13.

The system is one of the oldest we have in the factory other systems we have are running Logix V30 on the L72 using the Movifit without an issue.

In the past we have intergrated an MoviPro ADC unit onto the v13 processor without any issues.

As the V13 doesn't support EDS files I've used the Ethernet module to create my own connection to the drive but even using the structure specified by SEW cannot get the drive to communicate. It keeps giving me a comms timeout message.

Has anyone got any ideas on what the issue my be or successfully done this elsewhere?

I don't really fancy upgrading this PLC to a new revision to due other equipment installed on the line

Thanks in advance (y)
 
Thanks for taking the time to reply.

We run v20 (& v30) on a number of other areas within the factory and have movifit running via EDS there. This is where I have cross referenced the input/output array sizes against the documented information from SEW I don't really want to upgrade the PLC in the first instance but will if I have to
 
It's nothing more than a stab in the dark - but does your particular device have the option for Profinet and Ethernet/IP? A couple of years ago, I had an SEW device that I could not for the life of me get to talk. Turns out I'd forgotten to change a DIP switch that changed the port protocol from Profinet to Ethernet/IP. I finally worked it out after running a wireshark trace on the link, which showed the PLC sending out a connection request on the Ethernet/IP port, and the device rejecting it as the port wasn't open. A wireshark trace would likely be your next move also, if you can't find anything to "enable" Ethernet/IP.
 
Update.....

After setting up a test rig with a L62 v20 processor the issue was actually the ENBT card I was using to comunicate via to the movifit. When using an EN2T card there are no issues either via eds file or creation of a generic module. I checked the firmware revision levels against the card we used previously to communicate with the movipro on a different installation and they match. I have asked the question of SEW why there communication protocols are different between units, I'm waiting for a reply. As we have standard revision levels onsite for the ENBT I have not tried updating to the latest revision to see if I could establish communications that way.
 

Similar Topics

Hi everyone! Hope you all are doing great! We have a really strange issue with comms between Wonderware and a controllogix L62, we use an...
Replies
4
Views
1,674
One of the L62 faulted last week. First time I seen one of this in my many years of working with ControlLogix. Rockwell seems to take this...
Replies
1
Views
1,778
Good Morning , We had our 2nd episode in 4 weeks with a 1756-L62 processor causing a backplane communication issue , that caused us to...
Replies
7
Views
2,475
Hi All, Fairly new to PLCs and in particular communications between processors. I'll explain the problem best as I can. I have a new water...
Replies
7
Views
2,031
Good Morning , I received a used 1756-L62 / A CPU , from a vendor that was using it for a trainer. I tried to download a program that is...
Replies
4
Views
1,455
Back
Top Bottom