VFD Guy

MrPLC Member
  • Content count

    125
  • Joined

  • Last visited

Posts posted by VFD Guy


  1. Copying a real to a dint isn’t gibberish. It’s an IEEE 754 conversion. I agree with you on the rounding error from float to dint when you mix data types. However a copy will convert the data type. I’ve had to do this for drives on devicenet. Get the reference I want as a real, copy to a DINT, send the DINT to the drive, the drive (750 in this case) would convert back to a real. You can look on knowledgebase. Many technotes on it. Or just look up the IEEE conversion. I probably went on a tangent from your question but just wanted to say I’ve had to convert before. In your specific case, if you put a DINT tag into a tag looking for a real, I believe it just adds .00 to it. Devicelogix does that. And vice versa, I believe logix would truncate a real if put directly into a dint 


  2. @ElectronGuru  you’re correct that the speed reference the drive is pointing to probably can’t be changed while the drive is running but by understanding the io image, you can ‘change’ the speed ref on the fly by writing to the logic command to point to a new reference. 
     

    I agree that ample testing should be done before changing a live system. Sounds risky in any manner


  3. If you have some free outputs on the drive, you can make a clever speed select with parameter control on a DO wired to a DI to choose a speed select of parameter 38. I’m not completely understanding what needs to be done. An MSG is pretty simple if you’re sending a new reference 


  4. F12 on a 755 is caused by 2x drive rated current outputted for longer than 8 us. It is important to know when this occurs. On start or while running. If there's and encoder installed, try running open loop. A failing encoder may cause this. Also, starting into a rotating load without flying start on. This is also caused by motor winding shorts, but probably not your case if you have many drives doing this. 


  5. CCW also has data logging to record data over time or trending which is in graph form and much faster sample. Or saving a techsupport wizard will also show you fault and alarm history. If the event occurs and there is no fault, it's likely the run or stop command was removed