Re: [Emc-developers] Error channel missing errors

2017-04-27 Thread Chris Morley
I removed error message polling from gstat. I also added the math import (Thanks Norrbert) Chris M From: Chris Morley <chrisinnana...@hotmail.com> Sent: April 27, 2017 6:42 PM To: EMC developers Subject: Re: [Emc-developers] Error channel missing errors

Re: [Emc-developers] Error channel missing errors

2017-04-27 Thread Chris Morley
:33 PM To: EMC developers Subject: Re: [Emc-developers] Error channel missing errors On 27 April 2017 at 17:09, Chris Morley <chrisinnana...@hotmail.com> wrote: > The more I explain this the more I realize I think I need to remove error > polling. Could there be two (duplicated) error

Re: [Emc-developers] Error channel missing errors

2017-04-27 Thread Kurt Jacobson
Norbert, thank you for confirming that the problem is not specific to my GUI. I don't know what the best solution is, but I would vote for changing the error channel behavior so that it is analogous to the stat channel. This would mean that the most recent error is returned when polling for

Re: [Emc-developers] Error channel missing errors

2017-04-27 Thread Niemand Sonst
Hallo Chris, I just tested also with a simulated limit switch and as reported previously not all errors are reported. After I commented out GStat lines for error polling, I got the errors reported correctly. So in deed it is caused by double polling errors. So we have to discus, if the error

Re: [Emc-developers] Error channel missing errors

2017-04-27 Thread Kurt Jacobson
On Thu, Apr 27, 2017 at 1:33 PM, andy pugh wrote: > On 27 April 2017 at 17:09, Chris Morley > wrote: > > The more I explain this the more I realize I think I need to remove > error polling. > > Could there be two (duplicated) error channels? >

Re: [Emc-developers] Error channel missing errors

2017-04-27 Thread Niemand Sonst
Am 27.04.2017 um 05:11 schrieb Kurt Jacobson: > Hello all, > > I am using the Python interface and have noticed recently that the error > channel appears to catch errors only about 50% of the time. The errors get > printed to the terminal but don't show up when polling the error channel. I > did

Re: [Emc-developers] Error channel missing errors

2017-04-27 Thread andy pugh
On 27 April 2017 at 17:09, Chris Morley wrote: > The more I explain this the more I realize I think I need to remove error > polling. Could there be two (duplicated) error channels? -- atp "A motorcycle is a bicycle with a pandemonium attachment and is designed for

Re: [Emc-developers] Error channel missing errors

2017-04-27 Thread Kurt Jacobson
lution would be for my to stop using the HAL_ > > On Thu, Apr 27, 2017 at 12:09 PM, Chris Morley <chrisinnana...@hotmail.com > > wrote: > >> >> >> >> >> From: Kurt Jacobson <kurtcjacob...@gmail.com> >> Sent: A

Re: [Emc-developers] Error channel missing errors

2017-04-27 Thread Kurt Jacobson
<chrisinnana...@hotmail.com> wrote: > > > > > From: Kurt Jacobson <kurtcjacob...@gmail.com> > Sent: April 27, 2017 3:22 PM > To: EMC developers > Subject: Re: [Emc-developers] Error channel missing errors > > > > > A

Re: [Emc-developers] Error channel missing errors

2017-04-27 Thread Chris Morley
From: Kurt Jacobson <kurtcjacob...@gmail.com> Sent: April 27, 2017 3:22 PM To: EMC developers Subject: Re: [Emc-developers] Error channel missing errors > > A change recently in master has Gstat poll for errors. Does it poll even if I am not

Re: [Emc-developers] Error channel missing errors

2017-04-26 Thread Chris Morley
From: Kurt Jacobson <kurtcjacob...@gmail.com> Sent: April 27, 2017 3:11 AM To: EMC developers Subject: [Emc-developers] Error channel missing errors Hello all, I am using the Python interface and have noticed recently that the error channel appears to catch

[Emc-developers] Error channel missing errors

2017-04-26 Thread Kurt Jacobson
Hello all, I am using the Python interface and have noticed recently that the error channel appears to catch errors only about 50% of the time. The errors get printed to the terminal but don't show up when polling the error channel. I did not have this problem when using 2.7, only since switching