From: andy pugh [mailto:[email protected]] > On 1 January 2016 at 23:21, Bertho Stultiens <[email protected]> wrote: >>> I'm assuming using a scope is the right way to do it? >> Yes and no. It depends on what you are tracking and how it is induced. >Also, there is no way to detect an occasional microsecond spike without recording and analysing unfeasible quantities of data. >I tried looking for noise on my system with a scope, but soon gave up.
On the other hand, some types of failure are super obvious with a scope. On the level of 'Aieeeeee! My resolvers look like that! Aieeeee!' obvious. Which, to continue a theme, turned out to be due to wiring. (in particular, no problems when moving over =/- 1mm, spiky noise when moving over +/- 10mm) It's a useful tool - which often can't help diagnose subtle and intermittent errors. Well, not without a crazy amount of logging as per atp's post. As daft as it sounds - nearly every significant problem I've had to date on both my hobby level systems (gecko or clone) or my industrial systems (up to a 30 kw servo) has been traced to a poorly specified cable. Shielding is awesome... >atp Ben ------------------------------------------------------------------------------ _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
