On Mon, 2017-04-10 at 10:05 -0600, Sebastian Kuzminsky wrote:
> On 04/10/2017 09:45 AM, Valerio Bellizzomi wrote:
> > On Mon, 2017-04-10 at 16:30 +0100, andy pugh wrote:
> >> On 10 April 2017 at 15:52, Valerio Bellizzomi wrote:
> >>> Running the servo jitter test program shows a value of around 60
On 04/10/2017 09:45 AM, Valerio Bellizzomi wrote:
> On Mon, 2017-04-10 at 16:30 +0100, andy pugh wrote:
>> On 10 April 2017 at 15:52, Valerio Bellizzomi wrote:
>>> Running the servo jitter test program shows a value of around 6000-7000,
>>> but the default is 100 !
>>
>> That's because a 1mS s
On Mon, 2017-04-10 at 16:30 +0100, andy pugh wrote:
> On 10 April 2017 at 15:52, Valerio Bellizzomi wrote:
> > Running the servo jitter test program shows a value of around 6000-7000,
> > but the default is 100 !
>
> That's because a 1mS servo thread is about right for most machines.
> Just a
On 10 April 2017 at 15:52, Valerio Bellizzomi wrote:
> Running the servo jitter test program shows a value of around 6000-7000,
> but the default is 100 !
That's because a 1mS servo thread is about right for most machines.
Just about the only time that you would need to go faster in the base
On Monday 10 April 2017 10:52:29 Valerio Bellizzomi wrote:
> On Mon, 2017-04-10 at 15:46 +0200, Valerio Bellizzomi wrote:
> > Followup: the issue was in the servo jitter value. Looking at dmesg
> > there are a consistent number of messages indicating that one cpu
> > was stuck, and other messages
On Mon, 2017-04-10 at 15:46 +0200, Valerio Bellizzomi wrote:
> Followup: the issue was in the servo jitter value. Looking at dmesg
> there are a consistent number of messages indicating that one cpu was
> stuck, and other messages about hm2. Now I have left the default
> untouched and Axis starts.
Followup: the issue was in the servo jitter value. Looking at dmesg
there are a consistent number of messages indicating that one cpu was
stuck, and other messages about hm2. Now I have left the default
untouched and Axis starts.
On Mon, 2017-04-10 at 14:50 +0200, Valerio Bellizzomi wrote:
> Ok
Ok then it should be some config issue, I will investigate further.
On Mon, 2017-04-10 at 05:01 -0700, andypugh wrote:
> The Mesa drivers are built-in to LinuxCNC, no extra config should be needed.
> Can we move this to the forum?
>
> --
> You are receiving this because you authored the t
