Advanced Search

Chris, a little something here, regarding the variation of the circle diameter

mouse scroll only - scroll circle diameter 

may now work a little slower than in previous versions

It would perhaps be practical if the currently set value according to the

middle mouse single click - cycle through rotation increments 

would also be used to adjust the diameter?

Chris,
I'm not sure that the calculation is is correct. I see the tool table file being written to but, the offset is incorrect.

For example, take this line:
T42  P42  D+12.700000 Z+290.403761 ;SpeTool Spiral .5" Shank .5" Dia 2" CL

I first zero'ed the above line, measured spindle with 3d probe. Then the "Z" probe fails multiple times before the gcode starts correctly. The above line was after the multiple probes and the gcode started running.
My "Z" can only travel somewhere around 120mm based on it's current configuration.

Here's another tool table entry:
T28  P28  D+3.175000 Z+12.349993 ;Whiteside 1/8" RD1600
This is what I would expect to see(Z+12.349993).
However I probed multiple times on that one also.

I did look at the code and there is an os.fsync on line 335 of qt_tstat.py which is located in def _save()
There's also comments to this perhaps causing "odd errors".

I'm thinking that maybe the FLUSH before the FSYNC might be causing this?

 

All qtdragon versions have that button now. I'd you have an MPG you might like it to scroll the gcode, mdi or graphics view. There is no option to remove it currently.

scotta wrote:

Remora does not use the Base Thread.
Whether you run Remora or MESA the latency will be the same.
 

Hi Scott

Ok, then i have maybe some weird misconfiguration on my side. Today i switched the mill to a 7i96S today and the servo thread on the same laptop with same kernel params and network card is about 700k-750k instead 1,5m-6,0m with the remora config. Any idea what iam doing wrong ? Shall i upload my remora config ?

-
schnellmued