Search Results (Searched for: )

  • TheTinkeringMechanic1
02 May 2026 22:33 - 02 May 2026 22:54
Replied by TheTinkeringMechanic1 on topic Can't read gcode text in dark mode when editing.
How do I tell what one it is?
  • rodw
02 May 2026 22:00
Replied by rodw on topic HAL component for tangential knife
Finally, I have sent a PR to Linuxcnc on Github for this
github.com/LinuxCNC/linuxcnc/pull/3995

It was a lot harder than I thought. Many thanks to grandixximo for his help ensuring all the runtime tests passed.
  • zbeeru
02 May 2026 21:43
Yes, I need DIR signals. I don' have a preference for pinout.
  • HansU
02 May 2026 21:41
We can only help you if you tell us which GUI do you use.
  • fer662
02 May 2026 21:17 - 02 May 2026 21:18
Update:
I've got a draft electronics panel with all the ethercat stuff working with linuxCNC, including the servos which i'm able to jog around, which is a great start! it'll be a while until they are mounted physically on the machine, but i want to get started better understanding the process of tuning them, specially since i'm basically blocked from continuing with the physical part of the build until a few more things arrive.
I was able to get the stepperonline software running on a windows 10 vm within qemu and perform the inertia autotune part( which i'll obviously have to do again when they are really mounted ). I understand after that comes a manual part in which you tune the gain along with other stuff, basically testing movements and see what minimizes the error, but i've no idea about how this is done concretely, like what steps in which pieces of software, and specially how it is done for the 2 motors that share an axis.
  • PCW
02 May 2026 20:05
Replied by PCW on topic MESA card (LAN) failing to connect.
local host should always be 127.0.0.1/8
Don't change that.

You either need to figure out the issue with the  setting up a static IP address
with the network manager or edit the interfaces file as described in the
hm2_eth manual page.

googling debian setup static ip address

will give some more options.
 
  • Accipiter
02 May 2026 19:54
Replied by Accipiter on topic MESA card (LAN) failing to connect.
I then went to /etc/hosts and changed the local host to 10.10.10.100/24 which it accepted, then went to ping 10.10.10.10 and got the so far standard response 5 packets transmitted, 0 received
  • Accipiter
02 May 2026 19:36
Replied by Accipiter on topic MESA card (LAN) failing to connect.
I went to the network manager and tried to input 10.10.10.100/24 and it wouldn't accept the input??  Is there another way to set the host address?
  • PCW
02 May 2026 19:18
Replied by PCW on topic MESA card (LAN) failing to connect.
No, it's not set in the IP address range of the FPGA card

I would set the host address to 10.10.10.100/24

 
  • PCW
02 May 2026 19:15
Firmware for a 7I76EU with a 7I85 on P2 and 2 PWMgens on P3

Note that since P3 pins are unbuffered/unprotected it's best to add
a say 100 to 220 Ohm series resistor to pins connected to the rest of the system
(or use a cheap parallel port breakout card)

 

File Attachment:

File Name: 7i76eu_7i7...wm2d.zip
File Size:298.56 KB

 
  • Accipiter
02 May 2026 19:08
Replied by Accipiter on topic MESA card (LAN) failing to connect.
 

Your browser does not support embedded PDFs. Please download the file here: Download PDF.

  Please advise if this is an appropriate response.  Thank you.
  • PCW
02 May 2026 18:15
Replied by PCW on topic MESA card (LAN) failing to connect.
Whats does the command:

ip a

report?

 
  • Accipiter
02 May 2026 17:43
Replied by Accipiter on topic MESA card (LAN) failing to connect.
I am back at my problem and the same issue keeps arising.  I went through the Mesa ethernet setup tutorial, went to ping my card and nothing.  The response: 5 packets transmitted.  0 received. 100% packet loss.   I thought maybe my ethernet card was not compatible with Linux, so I tried on a second linux machine, same thing.  When I am looking at my 7i92 card with the ethernet port on the left side, I am interpreting up as away from me and down as towards me when it is lying flat on a surface.  According to my interpretation from the manual, the w5 jumper is down or towards me, and the W6 jumper is up or away from me this should give me the mesa's address as 10.10.10.10 .  I am convinced it is something basic that I am missing.  One more thing:  in the terminal I typed:  mesaflash --addr 10.10.10.10 --device=ETHER --readhmid and the response: No ETHER board found.  
  • COFHAL
02 May 2026 17:43
Replied by COFHAL on topic Qtvcp GUI and hal pins
I can now call macros with external buttons, but unlike the buttons created and displayed on the main screen, which automatically switch QTDRAGON to MDI when clicked, with external buttons you have to manually switch to MDI for them to run. Another problem I'm having is that it can't execute macros defined as `O <XXXXXXXXX> call`. The status screen always shows "File not open," and the terminal debugs this error:

[QTvcp.QTVCP.WIDGETS.ACTION_BUTTON][DEBUG] INI MDI COMMAND #: 7 (action_button.py:717)
[QTvcp.QTVCP.QT_ACTION][DEBUG] COMMAND= O <touch_plate_z> call (qt_action.py:234)
[QTvcp.QTVCP.QT_ACTION][DEBUG] CALL_INI_MDI command:O <touch_plate_z> call (qt_action.py:249)
emc/task/emctask.cc 70: interp_error: File not open
File not open
The path where the macros are executed is defined in SUBROUTINE_PATHS= There are .ngc files to run those macros.
  • dedlefou
02 May 2026 17:36
yes exactly please
Displaying 4171 - 4185 out of 11906 results.
Time to create page: 0.394 seconds
Powered by Kunena Forum