I’m having an error resulting in missing steps so the layers I’m printing
shift. The file I print is pretty big (17MB). But the error does not happen at
the same hight. How can i find what’s happening? Do i need to switch off the
screensaver for example? or is there something else i can check?
On 1/14/14 11:07 , Bas de Bruijn wrote:
I’m having an error resulting in missing steps so the layers I’m printing
shift. The file I print is pretty big (17MB). But the error does not happen
at the same hight. How can i find what’s happening? Do i need to switch off
the screensaver for
Yes, the BeagleBone Black,
the PRU is hat 10us step length and 1us step time.
The servo task period, in nano sec is 100.
When i run a latency test i get a jitter of approximately 56000 to 6 ns max
Jitter
I’ll disable the screensaver to check.
On 14 Jan 2014, at 19:13, Sebastian
On 1/14/2014 12:21 PM, Bas de Bruijn wrote:
Yes, the BeagleBone Black,
the PRU is hat 10us step length and 1us step time.
The servo task period, in nano sec is 100.
When i run a latency test i get a jitter of approximately 56000 to 6 ns
max Jitter
I’ll disable the screensaver to
Maybe the error generated has nothing to do with the missing steps per se, it
just got me triggered. I have acceleration about 2000 and I’ll turn it down
some more. Other parts got printed without problems. I’ll review the tension on
my belts.
On the arduino clone I have approx 1000 mm/s^2
Am 14.01.2014 um 19:33 schrieb Charles Steinkuehler char...@steinkuehler.net:
On 1/14/2014 12:21 PM, Bas de Bruijn wrote:
Yes, the BeagleBone Black,
the PRU is hat 10us step length and 1us step time.
The PRU code cannot cause an unexpected realtime delay, since this is a
message generated
I’ll start looking.
Thanks for the pointer
On 14 Jan 2014, at 19:57, Michael Haberler mai...@mah.priv.at wrote:
Am 14.01.2014 um 19:33 schrieb Charles Steinkuehler
char...@steinkuehler.net:
On 1/14/2014 12:21 PM, Bas de Bruijn wrote:
Yes, the BeagleBone Black,
the PRU is hat 10us step
