Advanced Search

i have seen in other thread, that you are from Slovakia. Me too, PM me

now I have these error ... somethings in git??

 

Buyurun Bizler Türkiye 'den Nokta CNC

Thanks for the messages. 
It seems to be a Linux file explorer problem indeed. 
I have been able replicate the same issue on another device (a PI5), also doesn't refresh automatically. It is the same issue with a NFS share as well.

Going up and down a folder works in certain conditions, but the up folder GUI button freezes (both on the file explorer and in Probebasic) once inside the shared folder (as if it doesn't know if UP is up on the server or locally.

I have tried adding all the options I found for no-caching, both on the server SMB config and on the client (when mounting), but nothing does.

The only thing which allows the folder to be updated on linux seems to be when the machine is hosting the folder itself (as changes are actually written on the machine itself). But that would require the machine to stay on at all times, which I don't want.

Any other ideas or ressources?
Though, I'm now pretty it is Linux specific and not Linuxcnc...

Aciera wrote:

Yea, my memory is certainly not what it once was and I cannot blame the heat. The only excuse I have is that I almost exclusively use rip installs.

Regarding the error you may want to try:

sudo apt install asciidoc

 

I know but it is €400 euro for hardware... I want to know if it is possible to run ... .xml file if there are starup setup in the twincat XAE should be no pain...
If anybody has experiences Have you any please?

regards..

"qtplasmac" "plasmac" are the 2 components that would need to be added i believe those get loaded with the ui their pins arent visible in the config hal file.
i think the options needed would be to add qtplasmac in gui dropdown then there is a gui options tab ,and user buttons
for the inputs pnconf has plasma in the first layer of the dropdown menu then
Arc Ok / plasmac:arc-ok-in
==> db_arc-ok.in
<== hm2_7i96.0.gpio.001.in
Ohmic contact / plasmac:ohmic-sense-in
==> plasmac.ohmic-sense-in
Float switch / plasmac:float-switch
==> db_float.in
plasmac:float-switch-out
<== db_float.out
==> plasmac.float-switch
==> qtplasmac.led_float_switch
Break away / plasmac:breakaway-switch-out
<== db_breakaway.out
==> plasmac.breakaway
==> qtplasmac.led_breakaway_switch
Move up / plasmac:move-up
==> plasmac.move-up
Move down / plasmac:move-down
==> plasmac.move-down
for the outputs
ohmic enable / plasmac:ohmic-enable
==> ohmicsense.is-probing
<== plasmac.ohmic-enable
scribe arm / plasmac:scribe-arm-delay
==> plasmac.scribe-arm-delay
<== qtplasmac.scribe_arm_delay-f
scribe on / plasmac:scribe-start
==> plasmac.scribe-start
<== spindle.1.on
torch on / plasmac:torch-on
==> hm2_7i96.0.ssr.00.out-00
<== plasmac.torch-on
==> qtplasmac.led_torch_on
laser on /plasmac:laser-on
==> hm2_7i96.0.ssr.00.out-01
<== qtplasmac.laser_on
in an encoder option
Arc voltage / plasmac:arc-voltage-in
<== hm2_7i96.0.encoder.00.velocity
==> plasmac.arc-voltage-in
those are the main connections made in pnconf

i wish i could be more help with this since im asking

what kind of hardware are you trying to hook up?
First thing would be make it work in TwinCAT, so that you are sure your wiring is correct and everything works.
Next step would be transfer of settings over to linuxcnc.

Hi sir, I have done it but is showing
" Near line 2 of //
Bad character '\357' used.
for a cavity milling operation.
I am using NX 11.0 and Linux CNC 2.8

Yea, my memory is certainly not what it once was and I cannot blame the heat. The only excuse I have is that I almost exclusively use rip installs.

Regarding the error you may want to try:

If you have a simple network and don't have any proxy details you can skip that part.

Mirror lets you choose a repo geographically close to you, unless you are installing a large number of packages and the server your are using is slowwwwwwww don't worry about it.

You need a user name & password. Like many concepts of Quantum Physics just accept it for what it is.

Since the installer is just a plain Debian installer many answers can be found here, the only difference being Linuxcnc packages are installed and a realtime kernel is install as well:
www.debian.org/releases/bookworm/amd64/

Hi JT,
I just did a fresh install of linuxCNC 2.9.3 and MesaCT 2.1.4.

Things that I notice & happen-
When I run the software the info panel reports LinuxCNC version 2.9.0 not 2.9.3

1. I enter the machine name and check load this config & backup config.
2. When I press default Metric for the linear units, the info in 1. above disappears. In fact if I enter the Mesa setup, verify the board then press Default metric all that information disappears as well. Is this normal behavior for the software?

Also noticed step 3 in your help "Select Max Linear Velocity" does not exist on the Machine tab but it does on the Settings tab.

 

Aciera wrote:

OOps, my appologies.
I just realized that I also have a 2.10 rip installation on that machine. So you are probably right and the deb installation does not come with the c source files. Kind of makes sense I guess.
 

you made me feel shocked... I'm not 30 anymore but I didn't remember about the /linuxcnc folder... I thought I had problems with my memory and the scorching heat that is here these days.

at the end I compile a rip with these:

but have these error too ...


 

Maybe this comment in the source code of the trajectory planner from 'src/emc/tp/tc.c' can give a bit of an idea: