Advanced Search

Hallo liebe Linux cnc Gemeinde
Ich habe es doch nicht aufgegeben und weitergemacht. Alle Achsen Bewegen sich, aber das hat Zeit gebraucht. Jetzt muss ich noch den Not-Aus machen, da habe ich ja schon Informationen. Das mit den Endschalter hat sich auch erledigt. Ich wußte nicht das man den Weg vorgeben kann somit Stopt die Achse ja nach erreichten Weg. Vorige Woche habe ich den Bildschirm montiert eine Schnurlose Tatatur und Maus Installiert damit nicht soviel Kabel sind.
Ich möchte die Grafig ändernund zwar die Jog - Tasten X - Achse ist Horizetal angeordnet un Y - Achse Vertikal die möchte ich tauschen wenn das nicht all zu schwierig ist. So das war es wieder mal.
Gruß Hans

Most probably missing G64 P0.1 or whatever the tolerance should be, notice the white line still visible in the preview.
G64 Pnn should be in the gcode file.

What type of motion hardware do you have?

if you using the makefile, all should work with the gowin enviroment (WLED/1.8V).

pin 10 in one of the LED's on the Tangnano9k and the blink plugin is only to show that the gateware is flashed and running

Hi Rob,

looks like you have been bussy Grotius
Yeahh...

ill try and find the page in one of my manuals for lathe and share will give you some ideas i think
Perfect.

The super imposed interpreter itself does not track the axis positions as it run's non-realtime.
I see no reason to run it realtime.

Each (sub) interpreter has it's own motion component running on the servo_thread 1ms.
Responsible for scurve motion, probing sequence, homing, etc.

Then the base_tread has it's own components running to execute the position commands from the motion components.
This can be a ethercat servo, a stepgen component, a probe input sensor, etc.
The position feedback is done in the base_thread's, this feedback is stored in the shared memory region(s).

The gui, servo_thread, base_thread, can see the feedback positions by just calling the shared memory name and value.

Will introduce axis group's.
And introducing global variables that can be used by all 3 interpeters. As they now have their variables only local.

Finally i now can start the qt program and start the servo_thread & base_thread from there using a rt_loader class.
Before today this was a problem.
Now also using multiple shared memory region's works fine.



Edit 07 Dec 2024 12:10:
Today did a mayor bug fix. It turn's out that multiple shared memory regions updated by thread's, would not exchange data
properly. Even when mutex etc. was set.
In the end it worked by using a single shared memory region for all thread's.
This is now solved in the source code. Was not the cause.
 

I followed this guide exactly:
forum.linuxcnc.org/ethercat/45336-etherc...-how-to-step-by-step
along with the instructions from:
forum.linuxcnc.org/ethercat/53785-instal...epositories#309793.I reinstalled LinuxCNC, but there were no changes

 

The pinout is determined by the pinout file (PINXXXX.vhd)
This file is identical for Xilinx or Efinix chips. Basically to make
a new pinout, you copy an existing pinout file ( one that's similar
to what you want) to your new pinout file, edit that file to match
the required pinout and module counts. Add that new file to
the project  (with "Edit Project" --> "Design" -->  "Add design file")
and include  it in the toplevel source file (TopEthernet16HostMot2_efx.vhd)
by adding it like this:

---

--use work.PIN_7I85SD_7I76_SSI_34.all;
--use work.PIN_PMDX126x2_34.all;
use work.PIN_NEWPINOUTFILE_34.all;  <<<<<<<< 
--use work.PIN_7I85S_4PWMD_34.all;
--use work.PIN_APSX_SWISS.all;
--use work.PIN_IOONLY_34.all;
--use work.PIN_ST8_RC8_34.all;   


Note that only one pinout file is uncommented



The .xml files are for the project manager and the interface designer
you do not edit them directly, nor do you change anything with the interface
designer unless you have different hardware (a custom FPGA card for example)

 

I forgot to mention, in case of dual-purpose pins like the PINOUT_WLED1_DATA of the Tangbob board, it needs to be configured as regular I/O pin. (It is a dedicated SSPI pin.) In the IDE, it can be done under Place&Route -> Configuration by right mouse click.

Thanks for solving the diff issue, it has given me a real headache.

The Compile button is enabled now and I am going to check, if it compiles etc.

By the way, Tangbob config.json contains a plugin "blink" mapped to pin10, which is not available on the Tangbob FPGA board (not wired on your PCB). Furthermore, pin10 belongs to the bank 3, which works with 1.8V (not 3.3V) causing an error when placing in the toolchain.
(I used the generated files from your program in the Windows Gowin IDE for running the whole process. It gives me more control what's going on during the processing)

SPI should work though a Efinix specific top level file would need to be
made from the Xilinx source.  Efinix tools don't automatically
translate "Z" types into tristate pins so you have to export the signal
_and_ enable pins from the top level file. Note for the current SPI source
(GCSPI) The SPI clock must be routed to a FPGA clock pin.

Any package is OK

Hello,
i finished with my linuxcnc setup and now i have some trouble with the accuracy.
Im using qtDragon and the newest version of linuxcnc (2.9.3 i think).I home my maschine first and after i send it to the G54 g0 x0 y0 z0 and the machine is going there but not reaching exactly the 0 position.
anyone could maybe help me or explain me?
 
 

I've been gathering and planning quite a bit. My motors and drives came in yesterday and another batch of goodies should be here in the next few days.

I'm still working on my finished plan but have a much better idea of how thing will look coming together.

But with a floating head with a magnetic breakaway and about 5 inches of Z travel i came up with this so far.

 

length = hal.get_value("hor_pos")
length = (float(length) + 115)
mat = Box(60, -30, -30, length, 30, 30)
mat = Color([0.4, 0.6, 0.2, 0.4],[mat])
mat = Rotate([mat],0,45,0,0)
mat = Translate([mat],0,0,0)
mat = Color([1, 1, 0, 1],[mat])

This is how I build a material element mounted in a lathe.

For now, only the material length is determined automatically, depending on the position of the lathe tailstock.

After the first simulation run, the material dimensions are drawn correctly. The problem is with rebuilding the dimension after running another ngc file with different dimensions.

I tried using HalToolCylinder and HalToolTriangle in various ways, but I must be doing something wrong