Advanced Search

It is not only a command.
I followed part of an "inspiring" doc and I typed other commands and edits on my own.
Actually, in my opinion, my installation is not completly correct, but it, after many experiments, works.

I have to create (and translate) a clean document with the procedure I followed to make NativeCAM run as a LinuxCNC tab.
When the doc will be ready I'll share it for sure.

Hi Rda,

The websocket server & client are now updated to exchange json data. This works fine.

For information a few pictures of the exhibition yesterday. So all these machines have a windows gui running.

Esab refused me to take a picture of their 5 axis cutting machine.
The swift-cut (now esab company) uses mach4 i guess, everyone knows how this looks like.

The kutavar is the next generation with my compliments to the software.
Kutavar is a english brand, located left to London on the map. The software they use is external made.
The software brand they use also delivers or advises the servo's for the Kutavar machine.
The kutavar uses software where you can do cad, cam and cnc in one program.
In England is easy'er to get hands on a Hypertherm high defenition as system integrator.

 
 

Then there are several tube cutters using laser, chinese brand, start price 75000 euro.
 
 
 

Tube cutter > 100.000 euro.
 
 



 

Hi again,sorry for my long absence, I moved and had to disassemble my machine for transport. I am reassembling it now and setting up linuxcnc again. I freshly installed LinuxCNC 2.9.3 Debian 12 Bookworm PREEMPT-RT and followed the steps for the Probe Basic APT Stable Install. I made a new machine config using Pncconf and the Axis GUI and only modified what I needed to get my machine running. When everything worked, I followed the steps to convert the config to ProbeBasic and that worked as well. All basic functionality seems to work in ProbeBasic, expect the tool changes. It is similar to the problem I had before.

All ProbeBasic files (Python and subroutines) are unodified. I only changed my .hal .ini and the probe_basic_postgui.hal file.

The machine is homed and Idle. Tool 1 is loaded in the spindle. 

I type "T1 M6" in the MDI window.
The log shows that the toolchange.ngc subroutine correctly notices that the requested tool is already in the spindle and exits.

 

But the machines doesn't stop the cycle and goes back to idle. The Cycle keeps running until I press the "Stop" button even though there is "M2" command right after the "<toolchange> endsub" line in the toolchange.ngc.
 

I don't understand why this happens since calling other ngc files like "clamptool" work fine and they set the machine back to idle after execution with the M2 command.

I attached my .hal and .ini files.
 

Updating. I have purchased and received the 3 drive control modules for the Siemens 611 drives to convert from the Heidenhain interface to one that can do Analog inputs. I am assuming velocity control is the preffered method?

I have also tracked down a company in the US that makes a 1Vpp to TTL signal converter that can handle the linear scales input and also the 2 rotary encoders used for the table pivot and tilt feedback. Cost more than I would have liked but is much cheaper than new encoders. Realistically I think I may have been able to just run with out them and used the encoder feed back via the drives / servos. But they are there and may as well be utilised. The supplier sent this when I enquired.

"=11.0ptThe HEIDENHAIN LS 486C has a 20µm resolution glass which, as you correctly calculated, will produce a 10Khz signal at 12m/min.  I have attached a data sheet showing the federate limits of each interpolation version for your reference.  You can choose any interpolation option from 0.5x to 5x.  The 5x interpolation model (SA 1872) will provide you with a 1µm TTL output signal.  "

So that is the drive and encoder interface issues solved (yet to be implemented )

With the increasing global madness ongoing I am escalating my MESA purchases and any other overseas needs so I don't end up missing out. With that in mind I am at a loss for where to start. I have been reading the manuals on the MESA boards but like most newbies I have researched, I am still confused. My machine needs 

• Analog servo control x5 .... for 3 axis, maybe a 4th down the track and spindle
• 9 TTL encoder inputs, maybe 10 if the 4th axis gets added.
• OEM inputs currently 28
• OEM outputs currently 22
• Automatic tool changer control
• MPG / keyboard control station.

My options I have configured so far

• 7I97T ethernet and motion control- 6 axis analog and encoders
• 7I85 serial interface x5 and encoder interface x 4
• 7I70, 7I71 input and output cards and a 7I73 pendant

I have looked at maybe using a

• 7I94T instead of the 7I97T
• 7I83 analog servo interface
• 7I53 12 channel encoder board
• 7I70, 7I71 input and output cards and a 7I73 pendant

Price difference is =11.0ptnegligible There are probably other combinations I haven't even considered. Any suggestions on the best configuration?
 

Hmm wouldn’t have been that recent.

I can take a look into it when I get some time. I remember back when there was a lot of trickery surrounding the timing between the component(s) (plasmac.comp, and in your case your capacitance comp) and the GUI’s timing. Perhaps there’s a better way to implement now.

It is tough because I’ve not run into this when cutting or simulating. Not saying it doesn’t exist, but it just makes it infinitely harder to fix when the issue is inconsistent or varies between computers.

Hopefully at least the reverse run stuff is easy to duplicate …

For me adding self.makeCurrent() to gcode_graphics.py solves the problem. it works

In gcode_graphics.py, yet another self.makeCurrent()Does that work?

Hallo Fritz,

cool danke.

mit F5 (MDI) meinst du oben links im Bild?
linuxcnc.org/docs/devel/html/de/gui/imag...mple-panel-small.png

Das bedeutet, dass ich dort alle Codes testen kann. Kann ich sie dann exportieren, wenn ich fertig bin? damit ich sie dann in eine Datei schreiben kann?
Wie kann man das MDI wieer löschen? bereinigen?


Ok, wenn ich das richtig verstanden habe.
G0 => Volle Geschwindigkeit in der Bewegung
G1 => Hier muss ich die Geschwindigkeit der Bewegung angeben, sonst bewegt sich nichts.
M0 => Pause (ich muss lesen wie lang die Pause ist)

Nach G0 / G1 kommt der Achsenbuchstabe mit der Angabe zu welcher Koordinate die Achse fahren soll. und dann kommt F für die Geschwindigkeit.

Und wenn ich zwei Achsen gleichzeitig fahren lassen will, dann muss ich nach dem G0 / G1 die beiden Achsenbuchstaben mit der entsprechenden Koordinate schreiben.
(Hier muss ich noch nachlesen, wie ich die beiden mit unterschiedlichen Geschwindigkeiten laufen lassen kann.

Ok, Du hast mir schon mal geholfen. DANKE!!!

VG Mücke

In glcanon.py we are nit getting a buffer for some reason:

Right, my bad. I'm on QtPlasmaC v2.10-008.046

Might be this:
(from the 7I92 manual)

The configuration utilities expect standard FPGA bitfiles without any multiboot features
enabled. If multiboot FPGA files are loaded they will likely cause a configuration failure.

Might also be an issue with the flash chip size detection.
 

Well, Linux backstage nonsense strikes again.

It appears that flippantly ignoring a GPG key thingie error during installation caused LCNC not to update/install properly.  LCNC was starting and running, so why worry?

sudo apt update revealed a GPG error.

Once I fixed that by editing the repository to buildbot2, adding the GPG key file, and doing another update/upgrade, both the timer hal pins and the display were magically fixed.

Hi all.

i have problem.

error mesaflash
linux reports an error: 
Checking file ... OK
   File type: BIT file
Error: BootSector is invalid


I have two files. 
1. tuxcnc-mod.bit
forum.linuxcnc.org/27-driver-boards/4773...901t?start=80#274777

2. my.bit 
I make the file myself using VM from IlyaKw

I load the first file using jtag.
After which I can write --write tuxcnc-mod.bit
I can --fix-boot-block
I can --fallback
mesaflash --device 7I92 --addr 192.168.1.121 --fix-boot-block --fallback --write tuxcnc-mod.bit
mesaflash --device 7I92 --addr 192.168.1.121 --write tuxcnc-mod.bit
Everything is fine and there are no errors.

I can even load my second file mesaflash --device 7I92 --addr 192.168.1.121 --write my.bit
The program is loading successfully
But after rebooting I can't load any firmware and I get the message
Checking file ... OK
   File type: BIT file
Error: BootSector is invalid

These commands do not work.
--write tuxcnc-mod.bit I --fix-boot-block --fallback

Me and I have to use jtag again

The problem is not very serious.

But I want to understand the fallback mechanism
Why do different files behave differently.

Apparently I am making a bad file that works via jtag but does not work with mesaflash.

Please tell me more about fallback

Something appears to be hosed up in my PB or QtPyVCP installation.

I found the file which creates the timer hal pins - probe_basic_ui.py - and that file is supposed to create u32 pins, not floats.

And same-same for timerminutes & timerseconds.  But... when I start either my config or the sim configs QtPyVCP creates float pins.

My PB sim timer on a Windows VM is working, but not the live machine.  And the VM sim's timer is displayed correctly.

I made a couple minor edits to the probe_basic.ui file, but that was just changing the ATC button M-code numbers.  Certainly didn't touch the py file or anything but the ui file.  And switching back to the 'stock' ui file results in the same behavior for both my config and the sim.

I don't think I did something dumb and install PB twice and my config is looking in an odd place with an edited ui.py file.  Probe_basic_ui.py has the same modified date as all the rest of the files in /lib/python3/dist-packages/probe_basic/

What would cause LCNC to ignore the QtPyVCP/Probe Basic python instruction? 

thanks it runs fine it does freeze and i have to reboot it and it is a little clunky on my other machine i run fluid nc . i know my verion of linuxcnc is about 10 years old a newer version would be a little more user friendly and smoother with a cleaner interface