Error in tool_offsetview.py

More
23 May 2024 20:55 #301257 by MarkoPolo
Chris. If the 20mb limit should remain, could you add an option to the ini that would disable this limitation?
I don't want to modify glcanon.py after every system update.

Another topic.
I'm looking for a reason why the progress bar doesn't work when loading a gcode file. In qtdragon_hd the progress bar works and the code seems to be the same as in qtdragon.
Could you check it?

(I'm not sure but the "updateProgress" function is not used at all, qtdragon_hd does not have this function)
The following user(s) said Thank You: tommylight

Please Log in or Create an account to join the conversation.

More
24 May 2024 01:52 #301273 by cmorley
Replied by cmorley on topic Error in tool_offsetview.py
In case you are interested how this came along:
github.com/LinuxCNC/linuxcnc/pull/2896

In fact I said it should be set-able and then never followed up.
You must load very big files - do you see the bounding box show?

There is a signal missing from gcode_graphics to MainWindow - I'll add it back soon.
The following user(s) said Thank You: tommylight

Please Log in or Create an account to join the conversation.

More
24 May 2024 16:00 #301321 by cmorley
Replied by cmorley on topic Error in tool_offsetview.py
Dragon loading progressbar should be fixed now.

[DISPLAY]
GRAPHICAL_MAX_FILE_SIZE = -1

Should allow maximize usage of  the memory for graphical display.
or set it to any integer MB of system memory (default would be 20 MB)
Should work with Qtvcp/GMoccapy/AXIS

Pushed to master

Chris
The following user(s) said Thank You: tommylight, MarkoPolo

Please Log in or Create an account to join the conversation.

More
24 May 2024 16:43 #301330 by MarkoPolo
Great. I tested it and everything works fine. Thanks

One more thing needs to be fixed and qtdragon will be completely usable...
The following user(s) said Thank You: tommylight

Please Log in or Create an account to join the conversation.

More
25 May 2024 02:18 #301366 by cmorley
Replied by cmorley on topic Error in tool_offsetview.py
What is the last thing?

Please Log in or Create an account to join the conversation.

More
25 May 2024 22:10 #301446 by MarkoPolo
What I mean is the "start from line" function. It works very poorly for me, although apparently it works well for some users.
Depending on the position from which the spindle starts, the machine sometimes makes strange movements before it reaches the place from which it should start working. Sometimes the cutter will pass through the material before it sets itself to the starting point.
It works quite well if I first manually set the XY position.
3-axis XYZ machine

Please Log in or Create an account to join the conversation.

More
26 May 2024 03:08 #301458 by cmorley
Replied by cmorley on topic Error in tool_offsetview.py
Is this is different in AXIS?

Please Log in or Create an account to join the conversation.

More
26 May 2024 10:26 #301469 by MarkoPolo
In axis it's exactly the same.
If the spindle is somewhere in the lower position and I click "start from line" from there, the cutter usually passes straight through the material.
It should be the case that first the spindle raises to a safe height, sets the XY position and starts working.
Where can I find the code that does all this?

Please Log in or Create an account to join the conversation.

More
26 May 2024 21:22 #301527 by cmorley
Replied by cmorley on topic Error in tool_offsetview.py
from memory.. does start from line moves to the end of the specified line?
I can't remember if that linuxcnc or a machine I used once.
Looks like the end.

But if the start line doesn't specify all the axes, then it only moves the one(s) in the line.
This is a hard problem to fix satisfactorily in all situations.
Could add an entry line for adding a g1 line before the line to start.

dialog RunFromLineDialog would need to be modified in dialong_widget.py

Chris

Please Log in or Create an account to join the conversation.

More
30 May 2024 09:58 #301834 by MarkoPolo
Yes, the machine starts working from the next part of the code until it encounters all axis coordinates. It depends on how the code is generated. If all XYZ coordinates are in one line, then it starts working correctly, exactly from the indicated line. But even the code generated this way does not solve all the problems.
I think a small modification would improve it a lot. Now, when starting from a specific line, the spindle moves simultaneously in the XYZ axes, but if you raised the spindles to a safe height, made the XY movement and only then started executing the code, it would be much safer.

Please Log in or Create an account to join the conversation.

Moderators: cmorley
Time to create page: 0.236 seconds
Powered by Kunena Forum