>>> hm2/hm2_5i23.0: encoder.00 dT <= 0, how can this be? >> >> This is a known bug in the HostMot2 encoder velocity calculation. >> >> Maybe someone more knowlegable can point to a workaround >> so these error messages dont clog up the queue. > > The hm2 message listed above does not go over NML, it goes directly from > the kernel to the system log files (via klogd). It indicates a problem, > but not the problem that's causing Donnie's machine to not work.
Depends how you printed the error. (From memory: if you use rtapi_print then they end up in dmesg, if you use report_error they surely end up at the HMI). The problem with the Error NML channel, is that it can only hold so many errors, if they come in a burst and the GUI doesn't read them all out, the queue will overfill. I think that will happen independently of how large the queue is. Donnie: maybe try really increasing the queue lenght in the emc.nml file in your config dir. (like 20-30 times as big, maybe even more). Regards, Alex ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
