Advanced Search

hallo,

ich bewundere deine geduld... aber mit 78 jahren geht alles langsamer...bei mir..

die config gepackt, Halui=halui eingefügt, fehlermeldung neu zugefügt..



karlhe

I am probably barking up the wrong tree but could you try with the following lines disabled in their respective files:

I wanna ask a question. What are you using as controller?(SBC or normal computer). Since i didn't setup a machine with normal computer, i am wondering about this topic. I usually worked with SBCs, so i didn't use parallel port or that kind of stuff. Is it hard, what do you think?

To see hidden files in linux you usually have to type <ctrl>+h in the file manager

nicht den 'linuxcnc' ordner packen sondern deinen config ordner, so wie du es hier gemacht hast.
forum.linuxcnc.org/41-guis/53643-ease-pr...fuegt?start=0#308594

Aber wie gesagt erst die Zeile 'HALUI = halui' einfügen und nochmals probieren dann wären wir wieder einen Schritt weiter.

hallo,ich habe die config gepackt und versucht zu schicken,dass hat nicht geklappr.wahrscheinlich zu gross? karlhe

Nachtrag; ich habe den linuxcnc ordner kleiner gemacht, die config gepackt, läßt sich nicht einfügen

 

Na wenigstens der Fehler...

Hab ich doch schon geschrieben:
forum.linuxcnc.org/41-guis/53643-ease-pr...fuegt?start=0#308610

Du scheinst die Zeile aber nicht hinzugefügt zu haben.

Hallo,

hier die dateien...

karlhe

To set a parameter through the gui you can simply add a function to your handler.

1. add the function 'on_value_changed' to your panel handler script like this (you will need to change the parameter name form 'near_speed.difference' to whatever parameter you want to change):


 

2. Open your panel in glade and add 'on_value_changed' as handler for the 'value_changed'  signal to your widget:

 

The parameter value should now change with the value of the panel widget:
 
 

Hi all,

We have a plasma cutter running QtPlasmaC which behaves somewhat strange. I have attached a video of the plasma cutter doing a contour without the torch turned on. The G-code contains M67 code to reduce the feedrate in the fillets and 100% feedrate on the straight lines. Except, the machine doesn't do that, it is "stuck" on 60% feedrate but suddenly, on the last leg of the contour is runs at 100% feedrate (as it should).

This problem arises randomly on other parts, sometimes it runs at 60% feedrate for half of a long straight line and then all of a sudden it jumps to 100% feedrate, which causes all kinds of issues. But strangely the vast majority of programs do not see this problem.

Has anybody experienced this and is there a solution for it ? Any help is greatly appreciated, it has got us stumped.

Cheers, Peter

scotta wrote:

I've also had no luck with an out of the box STLinkV2. But ColdTurkey has got it to work

pyocd.io/docs/debug_probes.html

"Recent STLink firmware versions will only allow access to STM32 targets. If you are using a target from a silicon vendor other than ST Micro, please use a different debug probe."

If you have a couple of probes you can always flash one with the following firmware.

github.com/scottalford75/Remora-RT1052/tree/main/CMSIS-DAP

ok, so pyocd, CMSIS-DAP firmware, stlink
give me some more notes, im trying to do a docs thing
github.com/cakeslob/Remora-docs/blob/mas.../Ethernet/rt1052.rst

Hi Phil,

Thank you. I checked the HAL pins and it looks like the feed reduction pin is connected to the motion pin. I will bring it up in advanced configuration, hopefully that gives us some clarity.

Love your work !

Cheers, Peter

Hmmm, I don't understand what is going on. This is what you should see:


It may be worth asking in a different forum section as a M67 issue, either Basic Configuration or Advanced Configuration as more folk will probably notice it. I am fairly certain that there is nothing we do which would affect M67 operations. In the meantime I will keep experimenting but not being able to replicate the issue makes it difficult.

Hi Phil,

Same result on the motion.analog-out-03 pin.

Cheers, Peter

The feed-reduction pin should be directly connected to motion.analog-out-03 which should be switched by the M67 E3 Qn g-code commands.

Could you look at motion.analog-out-03 with HAL Meter and see what it does.

They do change state correctly here.