G
As rule all drives have ability to create simulated encoder output from a main motor feedback. Drive producers are doing the feature in different ways which are depended from a type of a main encoder. One way does a hardware simulation output of a main motor encoder only if this encoder is incremental. Another one does a software simulation when a encoder is sin/cos, Hiperface or EnDat.
The case of hardware simulation is clear for me due to a small delay time about nanoseconds. The case of software simulation is complicated due a big delay time for the process about 250 us or 125 um which is depended from a drive maker.It seems to be large value when a position loop of an upper controller works on 2.25 kHz isn'it?
How do you do your applications with upper motion controller and drives in this case? Do you use a feedback signal with software simulation and don't notice a delay time or perhaps you use encoder signal splitter for drive and conroller or instead of you mount second encoder in a motor?
Thank you for your help
The case of hardware simulation is clear for me due to a small delay time about nanoseconds. The case of software simulation is complicated due a big delay time for the process about 250 us or 125 um which is depended from a drive maker.It seems to be large value when a position loop of an upper controller works on 2.25 kHz isn'it?
How do you do your applications with upper motion controller and drives in this case? Do you use a feedback signal with software simulation and don't notice a delay time or perhaps you use encoder signal splitter for drive and conroller or instead of you mount second encoder in a motor?
Thank you for your help