2016-07-19 13:40 GMT-03:00 John Kasunich <[email protected]>: > If set to auto-trigger, neither scope is likely to detect an index pulse. > > In that situation, a digital with deep memory, slow sweep speed (or roll > mode) and a glitch capture mode would do better than the analog. > > But the real answer is to switch from auto-trigger to normal trigger and > set the trigger source and level appropriately so the scope will trigger > ONLY when the pulse arrives. > > With the trigger properly configured, either analog or digital would > be able to detect the index pulse, but the digital would give you a > better look at it because of its effectively infinite persistence. > > Halscope cannot reliably detect ANY pulse shorter than its sample time. > If sampling in the servo thread that is usually 1mS, index pulses are > often much shorter than 1mS (depending on how fast the encoder > shaft is turning). > If you are using a hardware based encoder counter (Mesa or PPMC or > other), the actual index pulse probably doesn't appear in HAL at all. > > What Halscope CAN do is look at index-enable which is driven high > by motion during the homing sequence (or can be disconnected and > manually driven high by a "setp") and goes low when the encoder > driver detects an index pulse. >
Thank you John for the specific details about how this works. I tend to use the machines only for production and I don't have a lot of time for experimentation with all the features LCNC has. The only time I can improve my knowledge about how all these things work is when we put another machine to work with some new feature. For example now my concern about encoders is because I intend to replace the resolvers on the Mazak since, as I mentioned on another discusion they are wired backwards (the excitation is on the SIN and COS windings) and I couldn't measure them properly to see if they are gonna work with a resolver to quadrature converter. -- *Leonardo Marsaglia*. ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
