Advanced Search

Search Results (Searched for: )

  • DarkPhoinix
  • DarkPhoinix
10 May 2025 16:59
Replied by DarkPhoinix on topic Which kernel version is best for real time?

Which kernel version is best for real time?

Category: General LinuxCNC Questions

If your CNC setup works, then don't worry and just move on.

If you are paranoid, just set your max jitter to some really high value in your config.

Don't worry about stuff unless you need to.

I did it and the situation gets worse! if I only move the linucnc window the steppers make absurd noises and change the speed of movement, they are not yet on the machine they are free.. I don't dare to think what they could do at work!
do you mean this SERVO_PERIOD = 1000000 ?
I set it to 35000000. in the video with glxgear it is again at 1000000.
  • chrstrvs
  • chrstrvs
10 May 2025 16:50

Remora - ethernet NVEM / EC300 / EC500 cnc board

Category: Computers and Hardware

Hello, everybody!

About 1.5 years ago I tried going the Remora route on my NVEM V2 with the STM32F207 and a Raspberry Pi 4. After a steep learning curve I finally managed to get the motors to turn, but experienced an issue where the motors would stutter, or skip steps, for some reason. Despite some kind peoples best effort to help, I was never successful in solving the issue and my PrintNC has been out of order since then.

I finally gathered some energy and wanted to give this another go, so I bought a mini-PC, a Lenovo M93p, mainly because I feel more comfortable using a real PC rather than a RasPi, and because it feels like there is more support for it.
Anyway, I followed all the same steps as the last time to get Remora up and running, but unfortunately the result is the same, the motors turn, but stutters.

1.5 years is a long time in the world of open source firmware development, so first of all I would like to ask if the Remora-NVEM repo is still the latest one for the NVEM V2? Or has the old NVEM V2 been integrated in another repo and has seen some updates since?

My next question would be, if it turns out that I simply can't get the NVEM to work properly, what is the board to buy nowadays? Is it the EC300?

Regards,
Christian
  • kello711
  • kello711's Avatar
10 May 2025 16:44 - 10 May 2025 17:40
7i96 with THCAD-2 setup on Everlast 82i was created by kello711

7i96 with THCAD-2 setup on Everlast 82i

Category: Plasma & Laser

Hello all. I'm having some issues with getting my THCAD-2 setup with the Everlast 82i. I'm pretty sure I have all the settings correct. I opened the Everlast and set the jumper to the 16:1 divider ratio (as suggested). On the THCAD-2 I used the 10:1 (W1 Up setting) and left the card divider on 1. I used pnfconf to configure the THCAD and got the following settings:

Arc Voltage Offset = 100200.0
Arc Voltage Scale = 0.000199

In Qtplasmac I'm getting a -20 voltage reading instead of 0 V. I set the machine to run a small bit of G code and measured the voltage coming off pins 4,6 from the Everlast. This is consistently getting ~4.5V when running at 40A cut power. When I connected a 9V battery to the I+ and I- directly on the THCAD-2 the power in HALSHOW is jumping all over the place. However, when I connect the wires from the plasma back to the THCAD, I get no indication of any voltage when running a job.

Any help you can provide would be greatly appreciated.
  • zz912
  • zz912's Avatar
10 May 2025 16:32
Replied by zz912 on topic Leaving from TOOL page

Leaving from TOOL page

Category: Gmoccapy

I would be interested in Norbert's opinion.
  • Onkelmat
  • Onkelmat's Avatar
10 May 2025 16:32

analog Servo spins on its own when connected to 7i77

Category: General LinuxCNC Questions

UPDATE

okay, I'm feeling ashamed and stupid.

so the servo drives have 5 potentiometers at their front for several adjustments. guess you already know where this is going...

offset 1 and 2
rpm
P as of PID
and current

i already tried to adjust the offsets with zero effect days ago.

turns out you have to turn the potis like 8 times to get an effect from 60% to 0% offset, you can go both directions so like 20 turns at max. in fact I wasn't adjusting hard enough to get an effect.

and to my defense i bought the machines with minor problems and didn't touch the drives before and x-axis was always spinning like crazy, right from the very first start it ran into hardware endstops.

so it was just a drive someone messed with, before I got it, to get the machine running again.

no more spinning on its own. thanks.
  • Aciera
  • Aciera's Avatar
10 May 2025 16:19
Replied by Aciera on topic Leaving from TOOL page

Leaving from TOOL page

Category: Gmoccapy

I believe this is the intended behavior.
  • Aciera
  • Aciera's Avatar
10 May 2025 16:14 - 11 May 2025 19:17

Planning to Retrofit a Mazak Integrex200Y Mill-Turn Machine

Category: Advanced Configuration

Here is the promised sim config:
 

File Attachment:

File Name: mazak-inte...-dev.zip
File Size:111 KB


To test:
1. unzip
2. 'halcompile --install' the enclosed 'mazak_integrex_200y_kins.comp'
3. start 'mazak-integrex-200y' config and run the preloaded gcode program


If you have any questions, which is likely, just ask.

Text from the enclosed README file:

Experimental simulation of a 5axis Mill/Turn machine (eg MAZAK Integrex 200Y)

Implemented Gcodes:

- 'G67 B':          Moves the B-axis to the 'B'-word position and activates 'HALF TCP Lathe' mode.
- 'G68 B (X Y Z)':  Moves the B-axis to the 'B'-word position then defines and activates a work plane perpendicular the this current tool orientation with the origin at the current WCS (optionally offset by any [X,Y,Z]-Words). This will change WCS to 'G59' where the transformed work offset values have been written to (ie the prior values stored in G59 will be lost!).
- 'G68.1 (X Y Z)':  Defines and activates a work plane perpendicular the the current tool orientation with the origin at the current WCS (optionally offset by any [X,Y,Z]-Words). For change to WCS see 'G68'
- 'G69':            Cancels the work plane set by 'G68' and (currently) switches back to 'G54'.

NOTES:
- This config defines the work-spindle as '$0' and the tool-spindle as '$1'. Example: 'M19 $1 R90' will orient the tool-spindle to 90°. (For real hardware it is recommended to use the spindle encoder-position instead of using 'spindle.1.orient-angle'.)
- 'HALF/FULL TCP MILL/LATHE' modes include tracking of tool-spindle rotation.
- 'HALF TCP MILL/LATHE' modes do not track the work spindle rotation, this is intended behavior.
- 'FULL TCP MILL' mode will track all rotations.
- Tool-offsets must only be changed in 'Identity' mode as it may cause sudden joint movements otherwise.
- Lathe tools must only be used in 'Identity' or 'HALF TCP Lathe' mode.
- Mill tools must only be used in 'HALF/FULL TCP Mill' or 'TWP' mode.
- Due to easier abort handling we currently restrict the use of twp to G54 as LinuxCNC seems to revert to G54 as the default system.
  Abort behavior can be handled by using a subroutine defined in the ini file under [RS274NGC]ON_ABORT_COMMAND'.
- The TWP remap code in this config does not implement virtual rotations (ie no optional 'R' word).
  • zz912
  • zz912's Avatar
10 May 2025 15:44
Replied by zz912 on topic Leaving from TOOL page

Leaving from TOOL page

Category: Gmoccapy

My English is bad. Could you explain your message easier?
  • zz912
  • zz912's Avatar
10 May 2025 15:41

Change Tool Offsets after editing the Tool Table

Category: Gmoccapy

So try this:
        if "G43" in self.active_gcodes:
            self.command.wait_complete()
            self.command.mode(linuxcnc.MODE_MDI)
            self.command.wait_complete()
            self.command.mdi("G43")
            self.command.wait_complete()
            self.command.mode(linuxcnc.MODE_MANUAL)
            self.command.wait_complete()
        
        self.stat.poll()    
        toolinfo = self.widgets.tooledit1.get_toolinfo(self.stat.tool_in_spindle)
        if toolinfo:
            self.widgets.lbl_tool_no.set_text(str(toolinfo[1]))
            self.widgets.lbl_tool_dia.set_text(toolinfo[12])
            self.halcomp["tool-diameter"] = float(locale.atof(toolinfo[12]))
            self.widgets.lbl_tool_name.set_text(toolinfo[16])  
  • PCW
  • PCW's Avatar
10 May 2025 15:03
Replied by PCW on topic LinuxCNC compatible industrial PC

LinuxCNC compatible industrial PC

Category: Computers and Hardware

Not a specific recommendation, but in general I would suggest
hardware with a Intel rather than RealTek Ethernet interface
(as this avoids the needed DKMS driver installation with RealTek
and newer kernels)
  • cmorley
  • cmorley
10 May 2025 14:27
Replied by cmorley on topic G-code file loading at G53 instead of G54

G-code file loading at G53 instead of G54

Category: Qtvcp

Ok great we are getting there.
I'm now betting that these debug lines are showing the problem:
libnml/buffer/shmem.cc 320: Shared memory buffers toolCmd and toolCmd may conflict. (key=1004(0x3EC))
libnml/buffer/shmem.cc 320: Shared memory buffers toolSts and toolSts may conflict. (key=1005(0x3ED))
libnml/buffer/shmem.cc 320: Shared memory buffers emcError and emcError may conflict. (key=1003(0x3EB))

Unfortunately I don't know what would cause this message.
Hopefully someone else will see and help us. I'll look at your INI some more tomorrow.
 
  • vre
  • vre
10 May 2025 13:51
Replied by vre on topic Ganty sawmill

Ganty sawmill

Category: Advanced Configuration

Yes i have 15.6'' 1080p touch monitor
  • CallumRD1
  • CallumRD1
10 May 2025 13:42
Replied by CallumRD1 on topic G-code file loading at G53 instead of G54

G-code file loading at G53 instead of G54

Category: Qtvcp

Thank for your the response. Here is some more information in response to your suggestions.

This first image is the machine showing G53 coordinates. The tool is in the center of the work envelope, as you can tell by the non-zero coordinates (0, 0, 0 is the top front left corner). 

This next image is after having switched to G54 using the gui button. As you can see, I set the G54 origin to be the current position, so it reads 0, 0, 0 while the tool is in the center of the work envelope. The work envelope image shows the work offset origin (3 vector arrows) as at the current position, as expect. This is all behaving as I expect.

But when I look at the offsets table, it hasn't reflected the changes to the G54 origin. No values have updated.

More so, when I clicked on the G54 Z value of 4 and tried to directly change it, I got this error, with the full text copied below.


Error message:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/qtvcp/widgets/origin_offsetview.py", line 370, in dataChanged
    self.reload_offsets()
  File "/usr/lib/python3/dist-packages/qtvcp/widgets/origin_offsetview.py", line 232, in reload_offsets
    temp[STATUS.stat.g5x_index-1] = STATUS.stat.g5x_offset
    ~~~~^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: 'tuple' object does not support item assignment

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/qtvcp/widgets/origin_offsetview.py", line 373, in dataChanged
    self.reload_offsets()
  File "/usr/lib/python3/dist-packages/qtvcp/widgets/origin_offsetview.py", line 232, in reload_offsets
    temp[STATUS.stat.g5x_index-1] = STATUS.stat.g5x_offset
    ~~~~^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: 'tuple' object does not support item assignment
  • Roger S
  • Roger S
10 May 2025 13:29 - 10 May 2025 13:33
Replied by Roger S on topic Using POSIX realtime

Using POSIX realtime

Category: EtherCAT

I just tested it. When I restart the system, the link is down. with
lsmod | grep ec_generic
sudo modprobe ec_generic
lsmod | grep ec_generic

it works again

This is enough of a workaround for me. I can also do updates in the future with a clear conscience?
 
  • Hakan
  • Hakan
10 May 2025 13:15
Replied by Hakan on topic Using POSIX realtime

Using POSIX realtime

Category: EtherCAT

Wow! It works.I was ready to give up.
I don't know why it didn't work for you, exactly. More than there was a problem to load the ec_generic module using the ethercatctl script.
It will probably not work next time again.
I don't know of a permanent fix, but the two commands "sudo rmmod ec_generic" followed by "sudo modprobe ec_generic" will probably load the ec_generic module.
I don't know why it didn't work right away. But there is a fix.
Displaying 15046 - 15060 out of 17586 results.
Time to create page: 0.486 seconds
Powered by Kunena Forum