Advanced Search

I have also speed mode servos tuned
with p and ff1 so cruise ferror is 0
but at the start - stop i have ferror spikes.
How to guess initial ff2 value?
What else can i do for start-stop ferror?

Problem: "looks 50% too large" seems to get bigger over time (with every project), but the rule still seems to hold water at the end.

I love the temp wiring stand. I will definitely use it going forward.

What io's do you think you are missing?

I notice that your digital in and digital out are empty. I had to use this to control my tool changer, pnumatic gripper, and to read spindle & tool changer sensors. It is how the O-code program can control the outputs and check the inputs.

I linked my door lock to some classic ladder pins.
Ex: "net door-open classicladder.0.in-01 => hm2_7i97.0.7i84.0.0.input-00"

The sserial seems like it might be right. Check to see if you can see the 7i84 pins in halshow. I had to expand pins > 7i97 > 0 > then I could seen the 7i84. If it doesn't work try replacing the XXXXX with zeros to become "sserial_port_0=00000000" It is what works for my 7i97T + 7i84 setup.

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.