LinuxCNC + Orange Pi (allwincnc)

X 209,715mm is way outside your work volume. Are you saying that the part starts out at ~40x40mm and then the display suddenly shows a X position of 209715mm?

Please post more info about what exactly is happening. Even in your own language. I am still not sure what you are asking.

@Andy  He only mentions an open loop stepper system, but I also await further clarification.

It is a open loop system.

Hi Bari,
I manually setting zero point when I starting every milling.
So I took semi-finished product and fastened it on my CNC machine.
Then I manually set zero point of X, Y, Z axis. (the dimensions of the part I milled were about 40x40mm and and my working place is 400x500mm)
Then I run the program / Gcode. Program ran, machine milled the part. ... then like I said .. without doing anything or some kind of machine collision happened machine suddenly stopped during the milling process (for example somewhere in the middle of Gcode) and one of my X or Y or Z coordinates change in LinuxCNC from Gcode value to (for example '' 209715mm ''). 
When this happened, machine was stopped and didn't allow me to move with that axis. I must re-home the axis to ''zero''.

I don't understand why the position suddenly jump from value about 40mm to 200000mm. 

But like I wrote... I was mill another part (different Gcode) and then the machine was working fine.

M.

Yeah, that is odd. Has it only happened with that program? Does it happen every time you run the same program? Same line in the program causes the error or at random points?

Hi Bari, It happened only with that one program. The error cause not on samé line of Gcode but on different.

Hi MLc,

Good to see still has some people get interest with this project. By the way, your expansion board looks great!
Would you like to upload you gcode here, I can put it to my Pi and get it try, see the same thing happen to me.

Hi envyvan, sorry for my inactivity, i forgot to send it. 

Hi Mlc,

I don't have ATC on my machine so I have to remove some gcode, then I try it several times.
It works with no issue, I don't have the your position jumping problem.
Which os you are currently using? May be you will need to do some system optimize if you have come up with this issue all the time.
 

Hi envyvan,
Today I was milling and I again got the same error two times. I thought it was caused by adaptive cleaning G code algorithm from HSMWorks, but then I was manually moving (by keypad) with axis and I got the same error
I have only passive heatsink on CPU so I am going to try add a fan.

I am using debian - buster, release 10. Maybe I need some system optimize.
Servo-thread.tmax I had about 1000000 during the milling process.

Can you tell me what to change in ''settings'' ?

M.

Hi Mlc,

I don't have any luck to make the mesa driver installed on debian buster.
I did some research before, you can see link below for reference:
www.forum.linuxcnc.org/18-computer/39037...cnc?start=310#217178

I think I also upload my SDcard image somewhere. it was base on ubuntu.
If you get interest, you can give some try on it.

I think Servo-thread.tmax above 1000000 might cause some issue. You should keep your Servo-thread.tmax number below 1000000.
Try to disconnect you cable network and wifi.
Backup, your sdcard.
Then check your system"Session and startup", make sure no any unnecessary program there. I think we don't need any of auto update stuff.