Advanced Search

NTULINUX wrote:

 if anything it should be better and not worse, and this is a run-on-sentence.

Hi NTULINUX. I have no doubt in that statement, doubting my knowledge/skillset is in upgrading linux systems rather. Mind you I was able to use the 5.4.279 release full featured. Only bug was a new timeout error on starting, and ofc not being able to restart lcnc if closed - a full system reboot was required. 

To begin with I have no idea how to clean a previous RTAI installation (if required?), or whether it's okay to simply "upgrade over" which is what I've done.

Additionally (less inspiring!). I've completed a clean Debian 12 install on my newly acquired Dell Optiplex. All updated, all drivers functional, no errors, everything's happy. Then proceeded to installing the RTAI 5.4.279 debs (module, headers, image, then lcnc), to have nothing showing up when starting linuxcnc. It reports that module is not loaded, although re-installed the deb twice now

Not entirely sure what I've done to RTAI to deserve all that, we used to be good friends!!

Have you set the files permission to 'Allow executing file as program'?

Here is the part of the doc refering to custom M-codes:"The external program named M100 through M199 (no extension, a capital M, found in directory pointed by [DISPLAY] PROGRAM_PREFIX parameter of the INI file) is executed with the optional P and Q values as its two arguments."I followed this and the lcnc did not find the macro.

the txt must added to post to forum, but not used in lcnc. 

alwinjohn wrote:

Bad character '\357' used.
 

File -> Utilities -> Customer Defaults -> Manufacturing -> Simulation & Visualization
Under the tab "NC Program Manager", select UTF-8 without BOM as your output encoding.
Hope this helps. 

I just pushed a fix for getting the LinuxCNC version so download and reinstall the deb.

JT

sprintertrd wrote:

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.


 

What does apt-cache policy linuxcnc-uspace in a terminal return?

Yes, the "default" buttons will create a new blank configuration and then populate some units and a few variables, mostly I used them for testing. Perhaps a different function would be better. If you have any ideas let me know.
JT

Where are Lcnc M-codes are stored? 

I having hard time to run a custom macro in qtdragon_hd since the ini pah of subroutines not working. The macro itself is working. I also read and followed the docs on how to add multiple path to subroutines in the ini. 

So this is what I've discovered. And exactly what I expected to happen.

Using NFS
mount the nfs share via the mount command.
Tried this with both axis & qtdragon, using the file browser of each. Red is what I did on the linuxcnc machine, blue is what I did another remote machine. Server runs ubuntu, RPI5 is debian & Linuxcnc machine is running Mint.
Open a file in a sub dir of nfs share. create a file either locally on the server or via another pc (RPi5) that has the share mounted, go up one level, then back into the dir and I have no issues seeing the newly created files.
 

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