lostcontrol

Hi Bob, check out the System Bit area SB12/13/15 you can map it to plc area & then drive directly from your program.   System Setting/Initial tab. There is a button called System Memory List that gives the allocations 

@pturmel, the functions used are PLC config, not the drive. These applications need to be connected exactly as per the manual to work. It is possible that this is not the case for the OP.   If it were me, I’d be rolling my own code based on what is actually installed. All that is needed is a home sensor .

Change the source unit in the G3 to be 0. Try that, it it doesn’t work you will most likely need a routing table in the PLC  

Add a P_On first, then it will be possible

They are the UNIT NO switchs bob, not the NODE NO

Unit No OR Node No.? Unit No can be derived from the IO table & usually Node No is the last octet of IP address

Is your intent to control these drives or just monitor? IMHO, I don’t believe the CP series were designed with this intent (although I could be wrong..) Even monitoring more than 1x device is pushing the boundaries (I think)

Why not just download the settings via CX-P in the tree? by doing this, you are checking the settings are what you want/expect also.

What do you mean by pointers.?  

As there are now multiple drivers, you have to select the relevant one for your device. You should be able to locate the driver manually.   I have had this issue when using a brick PLC, NS & NB screens where have had to manually change the driver for the USB connection

Sounds like baldor/ABB drive upgrade? As IO_Rack has said, what modules are on the PLC rack.? you shouldn’t need to access the PLC if just doing a drive upgrade, as long as you can get the config/setup from the current flex drive. From there, it should be just autotune & go.  

This sounds like a bug in sysmac somewhere, as I recently had something similar. Opening a project that was all ok & had the EIP mappings are broke. I need to check if this was from an import or version upgrade tho.

Can the 'mode of operation' be exposed via the PDO mapping? 

Is this a working system or new.? ive had an L16 embedded IO go bad before, fortunately not much was used so could easily move to the expansion modules. 

This is where I would be focusing. Depending on the size of the servo, I would expect it to react back (as you would ) Do you have the manual that breaks down the control word? Perhaps that a single bit that is not being set correctly via the MC instructions? I am thinking that you should be able to do everything without the SYSMAC motion instructions to confirm the PLC-Drive functionality & that there is something missing in the actual motions maybe. (you will probably have to un-allocated the control word though.?) This is just an assumption though, but maybe something I would be trying if it were me.