Advanced Search

Thanks you All!!! I am not familiar with Python. I am starting to learn it.
In the meanwhile,
If I only want to add an image in the AXIS GUI, that will show a Camera view near the tool, and 3 label boxes.

What do you think it will be the easier way to have it done quickly?

Is this source code correct to add in the INI file to see the image

[DISPLAY]
PYVCP = image.xml

<?xml version="1.0" encoding="UTF-8"?>
<pyvcp>
<image name='fwd' file='fwd.gif'/>
</pyvcp>


This source code would be correct to add for the labels?

<pyvcp>
<label>
<text>"AXIS X"</text>
</label>
<label>
<text>"AXIS Y"</text>
</label>
<label>
<text>"AXIS Z"</text>
</label>
</pyvcp>

Or should I use something like:

Et1 = tk.Label(WINDOW, text="AXIS X", font=("Arial", 24), fg="blue", bg="yellow")
etiqueta.pack(padx=20, pady=20)
Et2 = tk.Label(WINDOW, text="AXIS Y", font=("Arial", 24), fg="blue", bg="yellow")
etiqueta.pack(padx=20, pady=20)
Et3 = tk.Label(WINDOW, text="AXIS Z", font=("Arial", 24), fg="blue", bg="yellow")
etiqueta.pack(padx=20, pady=20)




Thanks a lot.

There are some variables at the top of the shetcam post processor that allow you to prevent generation of the hole data if you don't want to use it.

Thank you very much! I will do that tomorrow (german time) and report the result!
Have a nice day!
Sincerely,
Hanno

Ok

issue of not being able to cut arcs due to radius error is sorted. User error as normal. For some reason I had it in my head that the statements in the gcode regarding the hole processing were commented out with a #. When I did actually comment them out with a ; the code loaded and ran with no issue.

the realtime error is possibly resolved but will know for sure when I do some more cutting tomorrow. I changed the Ethernet cable and also removed the WiFi nic. Will do more testing tomorrow and update the post if I can confirm which cured the issue, if it is cured that is.

Doesn't even look like the current hal file would run
as there are two different signals connected to
hm2_7i76e.0.7i76.0.0.spinout:

net pdnt.spindle-speed-abs => hm2_7i76e.0.7i76.0.0.spinout
#net spindle-vel-cmd-rps-abs => hm2_7i76e.0.7i76.0.0.spinout
net pdnt.spindle.is-on => hm2_7i76e.0.7i76.0.0.spinena
net spindle-cw => hm2_7i76e.0.7i76.0.0.spindir
net spindle-vel-cmd-rpm-abs <= spindle.0.speed-out-abs => hm2_7i76e.0.7i76.0.0.spinout

I would first get things running in the usual way by adding

net spindle.0.on => hm2_7i76e.0.7i76.0.0.spinena

commenting out

net pdnt.spindle.is-on => hm2_7i76e.0.7i76.0.0.spinena

and uncommenting:

#net spindle-enable             <=  spindle.0.on

When this is working I would look into the pendant spindle control options

thanks, yes i saw it, i will give it a try as soon as i learn this UI principles of linuxcnc..

as in everything the hard part is the beginning part i suppose..

this happens mostly because of i am new in linux environment and there is no step by step instructions for anything in linux.

i will write everything i learn step by step under this topic about the UI designing and editing for linuxcnc with qt designer so that newbies may save some time

Just a guess........
If your touch screen comes up as HID (assuming USB) you may be able to modify the mouse properties in "control center" . Sorry I can't be of more help, as I haven't got access to my setup.

Currently pocket one on the carousel is called no matter what I do. If I have tool #4 in the spindle but call the #<_current_pocket> the carousel rotates until the index and stops ending up on pocket #1. The code also fails to abort. If I re-run the code the carousel does not rotate, nor does it abort.

The sample of code I am running is as follows.

M68 E0 Q#<_current_pocket> ;set the carousel to move to the right pocket
M64 P0 ; start carousel
G4 P2
M66 P0 L3 Q60 ; wait and check for carousel finish
M65 P0; stop carousel
O040 if [#5399 LT 0]
    (abort, failed to align carousel)
O040 endif   
M2

M64 P0 is "net atc-enable motion.digital-out-00 => carousel.0.enable"
M66 P0 is "net atc-rdy carousel.0.ready => motion.digital-in-00"

I think I copied the "M68 E0 Q#<_current_pocket>" from a video or other forum post.
Is this the correct way to call a pocket when interacting with the carousel component?

My carousel setup is in the main.hal as follows:
# --- setup carousel ---
loadrt carousel pockets=21 encoding=index num_sense=2 dir=2
addf carousel.0 servo-thread

It has an index and a proximity sensor for pocket alignment.

Hi,

I have uploaded a first development version of my module on github.

It has not been deeply tested and will probably have some bugs. But it connects to drivers on RPi4 and RPi5 and moves motors. I wrote a very short how-to, but feel free to ask questions about how to use it.

Thank you RotarySMP. You certainly are an inspiration!

That's really interesting. I had no idea hal "scripts" are actually Tcl. Thank you for the neta function. I did just quickly test it out and indeed it appears to work.

Why do you say that debugging hal files would be difficult? From where I'm standing, debugging usually starts by checking why one input (or output) is not what its expected to be. The following step is to check what is connected to that input. To do that we can use the "show sig" command, which will then display all pins connected together. So I already see which (other) pin is driving that signal, and the name of the signal has little significance.

Is there some normal use case I'm not thinking about? I'm not saying that named nets are bad, I'm just questioning why there is no inbuilt automatic naming of nets. Is it just that nobody has done it, or is there some more fundamental argument against (supporting) automatic naming of nets?

You might try setting the Z axis velocity the same as the joint 2 velocity (125):

[AXIS_Z]
#MAX_VELOCITY = 25.0
MAX_VELOCITY = 50.0
#MAX_ACCELERATION = 750.0
MAX_ACCELERATION = 1000.0
#MIN_LIMIT = -100.0
#MAX_LIMIT = 0.01
MIN_LIMIT = -100.0
MAX_LIMIT = 100.0

[JOINT_2]
TYPE = LINEAR
HOME = 0.0
FERROR = 50
MIN_FERROR = 50
#MAX_VELOCITY = 25.0
MAX_VELOCITY = 125.0
#MAX_ACCELERATION = 750.0
MAX_ACCELERATION = 1750.0
P = 50.0
I = 0.0
D = 0.0

Is the Y properly calibrated?

What hole processing does Pronest have?
What diameter hole are you cutting?
What material and thickness?

Its suggested to slow cut velocity to about 60% for holes.

Ok, I didnt realize this, because the Probe Basic GUI and the VFD switched the ENA/FWD Output if I give some MDI S command. I can see that in the GUi, my relai clicks, the VFD switches to Run. But the Pin says the truth...

I don't fully understand why this Enable command should come only from the XHC-WHB-04 pendant (set pdnt....) and not from the PB Gui - I would like to enable the spindle over the pendant but more in an OR funktion not only with the pendant.
I have to say that all these spindle commands weren't made by myself but from someone else who wanted to help me out in the past. And I couldn't test it in real life, because my VFD wasn't connected until now.

How should I change the settings so that it works with GUI and pendant? can you give me some hints, please?
Thanks for your support!
Hanno

Looks like someone has started one...
forum.linuxcnc.org/qtvcp/53092-qtdragon-...ortrait-mode-monitor