Advanced Search

See here, no skipping
forum.linuxcnc.org/10-advanced-configura...glass-scale-feedback

I had the link for that one. Perhaps I wandered off this thread when I found it. It was a compilation of I think all of the macros showing the actual operation on a lathe much like the video you referenced, just for all the different operations quite a good video, no idea where I found it and can't seem to find it.

Thanks

I am certainly willing to test it.

I would suggest that we either fix VersaProbe or remove it completely from the project as it's really annoying to not have this working
as expected.
 
I can also move over to Basic Probe but I'd need some of the documents cleaned up as to what is to actually happen for each
button/control. Some controls are documented but, other controls as well as their functionality are not.

I'd be more than happy to work with you and even document the process for the project(Linuxcnc).

Send me some ideas and I can act on them.

Thanks for that David, I have been pretty busy this week.

ok, so the 160 V on your website corresponds to a peak voltage?
For the input voltage, for reasons of economy, a DC power supply to manage the 6 motors is likely to be expensive.
What's more, being in Europe, I have to manage with 240/400 volts. It's easier to find an auto-transformer to output 110V and add a 3-phase bridge rectifier with capacitor.
is it possible to supply your amps with RMS voltage?

for resolvers, is there a way to manage robot position data with batteries (like kuka) without continuously powering the computer with linuxcnc open? because manually homing robot axes could take a long time ...
 

Hi, MR.ACIERA  MR. TOMMY

Thank you for reply and sorry in weekend slow reply. 
This below post file gcode problem.
example about in gcode file at N15 to N3900 


**Also, what acceleration is set in the ini file?**
Tomorow at workshop I will check and told again.

Thank you
Asis,

 
 

Hello everyone,
first of all I don't know if I'm in the right place in the frum, but if I need to move my message please let me know.

Like you, I am in the process of retrofitting my 5-axis CNC type XYZBC.
In fact, having important torque reducers on the B&C axes I want to add encoders directly on these two axes. For this, I have started to buy a 7i96s where only one encoder is available but a daughter board can be added like a 7I85.
I've started to connect the system under linuxcnc 2.9.3, and I can't synchronize the scale between the Axis display and the actual position of my encoder.
my encoder is 1000 pulses/hole in quadrature, which gives 4000 pulses per revolution. With variables SCALE_ENCODEUR = 11.11 I manage to synchronize the display & the actual position of my axis; unfortunately my “joint” doesn't follow; I need at least a value of 3000 pulses/hole to no longer have this “joint tracking error”. And even with this value, the motor remains very reactive to the slightest movement of my encoder. Of course, the display no longer corresponds (since there's only the value of 11.11 to synchronize the display and the position of my axis).

I've been struggling for two months just to get this setting right.

Does anyone have an idea for my problem?

Thanks in advance for your help

 

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.