Dave Williams
Member
Heres a teaser, maybe. I am just relocating to a new plant that has many new installs using AB DeviceNet. Today we had a conveyor, controlled by a AB 160 series VFD, just stop running, dont have the model of the DeviceNet interface, but I'm certain its probably the only one for this drive. After looking at this online, the enable bit was not present, which is supplied by the drive via the DeviceNet communications. Not being up to speed on DeviceNet myself, our electricain quickly diagnosed the issue as one that has occured before, that being that the message length instruction in the DeviceNet program in the interface, had apparently changed to a value that was to short to contain all the bits used in the message to the PLC. After changing the message length to what we believe are the max. values, life was good. My questions is has anyone experienced this issue. Again this is the second time this has occured according to our electrician, the last time the speed reference was effected, causing a conveyor to run at extremely high speed, a somewhat dangerous situation. One thing I did notice on the particular drive today was it was at the end of the DevideNet chain & had the terminating resistor on the cable, I will check with him tomorrow to see if that was the case on the last one that did the same thing, I was thinking perhaps the wrong resistor was used, but thats just speculation. Tomorrow I will also look into more detail the exact part of the program he changed, but I'm certain it was an output message length. Just curious if anyone has experienced anything like this. Thanks in advance for any responses.