1. Forum
  3. Search

Advanced Search

Search Results (Searched for: )

  • PCW
  • PCW's Avatar
12 Aug 2025 15:49 - 12 Aug 2025 15:51
Replied by PCW on topic "pwm/dir" (Out1) switches for spindle CCW

"pwm/dir" (Out1) switches for spindle CCW

Category: Basic Configuration

What fIrmware are you using? 

5i25_5ABOBx2.bit should have the correct pinout and GPIO 7 is just GPIO on that firmware

 
  • joshualee777
  • joshualee777
12 Aug 2025 15:26
Replied by joshualee777 on topic Amplifier Fault ECT60 Closed Loop

Amplifier Fault ECT60 Closed Loop

Category: EtherCAT

Thank you all. I will study more and receive help to bring this knowledge to a commercial level. I'm happy to be able to do something.
  • dannym
  • dannym
12 Aug 2025 15:03
Storing the most extreme dimensions found on preview was created by dannym

Storing the most extreme dimensions found on preview

Category: AXIS

So, I've got this great idea on checking bit Z-height before running: forum.linuxcnc.org/38-general-linuxcnc-q...hecking-on-top-datum

This hinges on there being a highly reliable way to calc the lowest Z the G-code will go to- one that there's no way around like loading a file in an unusual way, or any method that changes the user offsets that either evaded  recalculation or recalculates wrong.

It seems the best way to do this would be to modify AXIS so whenever it analyzes a g-code file, it saves the lowest Z found in a special .nc file.  Once the rangefinder sees that someone has changed or might have changed the bit, it requires this check of a physical tool touch-off on a fixed sensor.

My current thought is that it won't try to second guess you and set your Z offset to what it thinks you want.  You'd still be in control of that.  Regardless of whether you zeroed the machine on the bed or top of the wood (which you'd want to do for V-carving), it's just going to check how deep the loaded job would go and if it's going to cut more than 0.5mm into the spoilboard, it will not allow running until it's addressed and clears a repeat of the bit check and/or loading a file that doesn't go as deep.

To do this, I figure when AXIS triggers a reevaluation on the Preview (file loading, or the user changes the user offsets, it rewrites that .nc file.  The nc file isn't anything the user interacts with directly.  The system's bit check routine just calls this external ,nc and AXIS would update that every time you load a file so it should be reliable, right? 

Hmm, what's my question?
1.  Am I correct in thinking that the evaluation it does while loading a file is definitive, except perhaps for manually written G-code subroutines/conditionals it can't display in the 3D workbox area? 
2.  And it's definitive in that there's no way it could get out of sync?  That is, there's nothing else that can change the toolpath that doesn't come through that load-and-evaluate code in AXIS?  I see the "Edit G-code" function has to do another load-and-evaluate to change the toolpath, so there's no fooling it that way. 
3.  I know it's Python and thus the source is right there, but if anyone wants to point me to the "right spot", that could be a huge timesaver.
  • smv
  • smv
12 Aug 2025 14:40
Replied by smv on topic Request for Community Feedback on g-code++ (sterp) Integration with LinuxCNC

Request for Community Feedback on g-code++ (sterp) Integration with LinuxCNC

Category: Show Your Stuff

Thanks a lot for reaching out!

Yes, in the current fork, it lives under src/emc/sterp as a plug-in interpreter.
In fact, I modeled it after studying how canterp works.

I understand that it might not gain much traction.

I'd love to maintain and extend the project as long as life permits me! Currently, I’m just an undergraduate, so I can’t promise a fixed 20-year roadmap just yet, but I've built sterp/gcode++ with maintainability in mind.
I might also extend it in the near future and add more preliminary unit tests.
  • smv
  • smv
12 Aug 2025 14:18
Replied by smv on topic Request for Community Feedback on g-code++ (sterp) Integration with LinuxCNC

Request for Community Feedback on g-code++ (sterp) Integration with LinuxCNC

Category: Show Your Stuff

Right now gcode++ extends g-code by introducing for loops, while/do-while loops, as well as imports (currently working on test cases for the same for the latest LinuxCNC release).

The inclusion of these control structures and import statements could greatly improve readability and code reusability.

It also ships with an in-house REPL for dry-running programs that can be used outside of LinuxCNC and has richer logging - I intend to add a simple debugger to it possibly in the future.
  • tommylight
  • tommylight's Avatar
12 Aug 2025 14:15
Replied by tommylight on topic Amplifier Fault ECT60 Closed Loop

Amplifier Fault ECT60 Closed Loop

Category: EtherCAT

I know quite a lot about EtherCAT from reading here, but no experience, so i refrain from replying completely.
Tank you, Hakan.
  • PCW
  • PCW's Avatar
12 Aug 2025 14:01
Replied by PCW on topic M66 keeps waiting

M66 keeps waiting

Category: G&M Codes

Yes, I just copy/pasted the G code sample into a file.

It worked with master and 2.9.4 (I can't easily try 2.8 because of the Python 2-3 change)

I don't think the OS matters but this is Mint 20.2 with a recent kernel (6.15)
 
  • Firehunter
  • Firehunter
12 Aug 2025 13:13
Replied by Firehunter on topic M66 keeps waiting

M66 keeps waiting

Category: G&M Codes

Did you run it as G-code? Which version LinuxCNC and OS are you using?
  • Aciera
  • Aciera's Avatar
12 Aug 2025 12:42
Replied by Aciera on topic New member from Germany - CNC retrofit of a Leinen FM1

New member from Germany - CNC retrofit of a Leinen FM1

Category: General LinuxCNC Questions

Service Manual for the TNC113:
product.heidenhain.de/JPBC/image/FILEBAS...C/599239-00-a-02.pdf

As far as I'm aware the glassscales directly plug into the TNC113. I rather doubt that you are going to find any EXE units in there.
  • meister
  • meister
12 Aug 2025 12:13
Replied by meister on topic M1xx: Controlling Relays (solenoids) from within axis MDI

M1xx: Controlling Relays (solenoids) from within axis MDI

Category: Advanced Configuration

you can reuse the 'iocontrol.0.coolant-mist' hal-pin and change the name in the Axis-GUI to 'Clamp'

  • andypugh
  • andypugh's Avatar
12 Aug 2025 11:17
Replied by andypugh on topic New member from Germany - CNC retrofit of a Leinen FM1

New member from Germany - CNC retrofit of a Leinen FM1

Category: General LinuxCNC Questions

Is it this one?
www.instagram.com/furniturenmarkt/p/CKTauBwrZ-F
Which claims that it might be the only one?

The circuit board is odd, in that it seems to have only one connection.

Do you have any pictures of the inside of the control cabinet? I would not be surprised to find that you already own some EXE units, in that cabinet.
  • my1987toyota
  • my1987toyota's Avatar
12 Aug 2025 10:05 - 12 Aug 2025 12:28
Replied by my1987toyota on topic ARE YOU KIDDING ME YOUTUBE !!!

ARE YOU KIDDING ME YOUTUBE !!!

Category: Off Topic and Test Posts

  I have multiple YT channels as well but only post on my main one . I admittedly suck at video making. The only
one making money off my stuff is YouTube themselves. Honestly I will most likely be shutting down my other
channels just because I was using them to compartmentalize things. With what YT and most of the world is trying
to do, I may just decide to go dark. (aside from a few sites)
  • seuchato
  • seuchato
12 Aug 2025 10:04
Replied by seuchato on topic M1xx: Controlling Relays (solenoids) from within axis MDI

M1xx: Controlling Relays (solenoids) from within axis MDI

Category: Advanced Configuration

....
For more outputs/stuff, you would have to go with what you did, and there are probably many ways of doing it, and you can use PyVCP panel to show info about it at all times:
linuxcnc.org/docs/html/gui/pyvcp.html
I use PyVCP panels a lot with Axis GUI, a lot, even for showing all Mesa IO and everything else, on industrial machines. :)
forum.linuxcnc.org/30-cnc-machines/31792...ofit?start=100#88523
See the right side, all is added as PyVCP panels.
 

I see there is a "sim.pyvcp.demo" "pyvcp.embed.tab" Which fits my bill quite closely. What I'd really would love is something added on the "F3" panel of axis:



I have no idea how to do that.
But also, maybe that is another thread in axis and at the wrong place here. Pls let know and I'd open a new thread there, leaving a hint here. 
greez
chris
  • seuchato
  • seuchato
12 Aug 2025 08:15
Replied by seuchato on topic M1xx: Controlling Relays (solenoids) from within axis MDI

M1xx: Controlling Relays (solenoids) from within axis MDI

Category: Advanced Configuration

... following up on this, instead of working :-)
my parport pin usage:

 

So, it turns out langdons was right about some pins still being unused. I my case, pins 1, 8, 9 and 16 wait to be used. Hope I got the connection diagram of said 1N4148 diode and relays right, (I lack electronics knowledge). I am about to order this board:

www.conrad.com/en/p/tru-components-tc-99...-1-pc-s-2481804.html

I have a feeling, it has some sort of protection built in. The manual is not clear on this however. Anyway, some 1N4148 never seem to be unnecessary, so I order these:

www.conrad.com/en/p/tru-components-ultra...-150-ma-1581846.html

Are these OK?

greez
chris
 
  • juergen-home
  • juergen-home
12 Aug 2025 07:52
Replied by juergen-home on topic "pwm/dir" (Out1) switches for spindle CCW

"pwm/dir" (Out1) switches for spindle CCW

Category: Basic Configuration

Thanks Peter for coming by. I put your 3 lines in my .hal file but there is an error message:
...
Debug file information:
Note: Using POSIX realtime
./ttm_a.hal:298: parameter or pin 'hm2_6i25.0.gpio.007.is_output' not found
2077
Stopping realtime threads
...
Perhaps this is because  gpio.007 is "hm2/hm2_6i25.0:     IO Pin 007 (P3-17): PWMGen #0, pin Out1 (Dir or Down) (Output)"

Seems this gpio.007 is bound to "pwm/dir" (Out1) for signaling CCW, what I want to do is to use it as a signal to enable my VFD while CW rotation.
Because I'm low on outputs I want to use this gpio.007 with the relay.

Juergen


Error report created by /usr/lib/tcltk/linuxcnc/show_errors.tcl:

Print file information:
RUN_IN_PLACE=no
LINUXCNC_DIR=
LINUXCNC_BIN_DIR=/usr/bin
LINUXCNC_TCL_DIR=/usr/lib/tcltk/linuxcnc
LINUXCNC_SCRIPT_DIR=
LINUXCNC_RTLIB_DIR=/usr/lib/linuxcnc/modules
LINUXCNC_CONFIG_DIR=
LINUXCNC_LANG_DIR=/usr/lib/tcltk/linuxcnc/msgs
INIVAR=inivar
HALCMD=halcmd
LINUXCNC_EMCSH=/usr/bin/wish8.6
LINUXCNC - 2.8.4-1-gb7824717b
Machine configuration directory is '/home/cnc/linuxcnc/configs/ttm_a'
Machine configuration file is 'ttm_a.ini'
INIFILE=/home/cnc/linuxcnc/configs/ttm_a/ttm_a.ini
VERSION=1.1
PARAMETER_FILE=linuxcnc.var
TASK=milltask
HALUI=halui
DISPLAY=axis
COORDINATES=XYZ
KINEMATICS=trivkins coordinates=XYZ
Starting LinuxCNC...
Starting LinuxCNC server program: linuxcncsvr
Loading Real Time OS, RTAPI, and HAL_LIB modules
Starting LinuxCNC IO program: io
Starting HAL User Interface program: halui
Found file(REL): ./ttm_a.hal
Shutting down and cleaning up LinuxCNC...
Running HAL shutdown script
hm2: loading Mesa HostMot2 driver version 0.15
hm2_pci: loading Mesa AnyIO HostMot2 driver version 0.7
hm2_pci: discovered 6i25 at 0000:06:00.0
hm2/hm2_6i25.0: Low Level init 0.15
hm2/hm2_6i25.0: Smart Serial Firmware Version 43
hm2/hm2_6i25.0: 34 I/O Pins used:
hm2/hm2_6i25.0:     IO Pin 000 (P3-01): PWMGen #0, pin Out0 (PWM or Up) (Output)
hm2/hm2_6i25.0:     IO Pin 001 (P3-14): IOPort
hm2/hm2_6i25.0:     IO Pin 002 (P3-02): StepGen #0, pin Step (Output)
hm2/hm2_6i25.0:     IO Pin 003 (P3-15): IOPort
hm2/hm2_6i25.0:     IO Pin 004 (P3-03): StepGen #0, pin Direction (Output)
hm2/hm2_6i25.0:     IO Pin 005 (P3-16): IOPort
hm2/hm2_6i25.0:     IO Pin 006 (P3-04): StepGen #1, pin Step (Output)
hm2/hm2_6i25.0:     IO Pin 007 (P3-17): PWMGen #0, pin Out1 (Dir or Down) (Output)
hm2/hm2_6i25.0:     IO Pin 008 (P3-05): StepGen #1, pin Direction (Output)
hm2/hm2_6i25.0:     IO Pin 009 (P3-06): StepGen #2, pin Step (Output)
hm2/hm2_6i25.0:     IO Pin 010 (P3-07): StepGen #2, pin Direction (Output)
hm2/hm2_6i25.0:     IO Pin 011 (P3-08): StepGen #3, pin Step (Output)
hm2/hm2_6i25.0:     IO Pin 012 (P3-09): StepGen #3, pin Direction (Output)
hm2/hm2_6i25.0:     IO Pin 013 (P3-10): IOPort
hm2/hm2_6i25.0:     IO Pin 014 (P3-11): IOPort
hm2/hm2_6i25.0:     IO Pin 015 (P3-12): IOPort
hm2/hm2_6i25.0:     IO Pin 016 (P3-13): IOPort
hm2/hm2_6i25.0:     IO Pin 017 (P2-01): Encoder #0, pin A (Input)
hm2/hm2_6i25.0:     IO Pin 018 (P2-14): Encoder #4, pin B (Input)
hm2/hm2_6i25.0:     IO Pin 019 (P2-02): Encoder #0, pin B (Input)
hm2/hm2_6i25.0:     IO Pin 020 (P2-15): Encoder #4, pin Index (Input)
hm2/hm2_6i25.0:     IO Pin 021 (P2-03): Encoder #0, pin Index (Input)
hm2/hm2_6i25.0:     IO Pin 022 (P2-16): IOPort
hm2/hm2_6i25.0:     IO Pin 023 (P2-04): Encoder #1, pin A (Input)
hm2/hm2_6i25.0:     IO Pin 024 (P2-17): IOPort
hm2/hm2_6i25.0:     IO Pin 025 (P2-05): Encoder #1, pin B (Input)
hm2/hm2_6i25.0:     IO Pin 026 (P2-06): Encoder #1, pin Index (Input)
hm2/hm2_6i25.0:     IO Pin 027 (P2-07): Encoder #2, pin A (Input)
hm2/hm2_6i25.0:     IO Pin 028 (P2-08): Encoder #2, pin B (Input)
hm2/hm2_6i25.0:     IO Pin 029 (P2-09): Encoder #2, pin Index (Input)
hm2/hm2_6i25.0:     IO Pin 030 (P2-10): Encoder #3, pin A (Input)
hm2/hm2_6i25.0:     IO Pin 031 (P2-11): Encoder #3, pin B (Input)
hm2/hm2_6i25.0:     IO Pin 032 (P2-12): Encoder #3, pin Index (Input)
hm2/hm2_6i25.0:     IO Pin 033 (P2-13): Encoder #4, pin A (Input)
hm2/hm2_6i25.0: registered
hm2_6i25.0: initialized AnyIO board at 0000:06:00.0
hm2_6i25.0: dropping AnyIO board at 0000:06:00.0
hm2/hm2_6i25.0: unregistered
hm2_pci: driver unloaded
hm2: unloading
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments

Debug file information:
Note: Using POSIX realtime
./ttm_a.hal:298: parameter or pin 'hm2_6i25.0.gpio.007.is_output' not found
2077
Stopping realtime threads
Unloading hal components
RTAPI_PCI: Unmapped 65536 bytes at 0x7f0222141000
Note: Using POSIX realtime



-----------------------------------------------------------------------
Info report created by linuxcnc_info:
The file:    /tmp/linuxcnc_info.txt
can be posted to a forum or a web site like:
     http://pastebin.com
in order to provide information about the linuxcnc
system and configuration.

                Date: Di 12. Aug 09:22:22 CEST 2025
            UTC Date: Di 12. Aug 07:22:22 UTC 2025
        this program: /usr/bin/linuxcnc_info
              uptime: 09:22:22 up 10 min, 1 user, load average: 1,09, 0,87, 0,52
     lsb_release -sa: Debian Debian GNU/Linux 10 (buster) 10 buster
      which linuxcnc: /usr/bin/linuxcnc
                 pwd: /home/cnc/linuxcnc/configs/ttm_a
                USER: cnc
             LOGNAME: cnc
                HOME: /home/cnc
              EDITOR:
              VISUAL:
            LANGUAGE:
                TERM: dumb
           COLORTERM:
             DISPLAY: :0.0
             DESKTOP: lightdm-xsession
        display size: 1920x1080 pixels (508x285 millimeters)
                PATH: /usr/bin:/home/cnc/linuxcnc/configs/ttm_a/bin:/usr/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games

uname items:
         nodename -n: debian
      kernel-name -s: Linux
      kernel-vers -v: #1 SMP PREEMPT RT Debian 4.19.316-1 (2024-06-25)
          machine -m: x86_64
        processor -p: unknown
         platform -i: unknown
      oper system -o: GNU/Linux

/proc items:
             cmdline: BOOT_IMAGE=/boot/vmlinuz-4.19.0-27-rt-amd64 root=UUID=9c449597-d44a-4504-9fed-3d2541ad317f ro initrd=/install/initrd.gz quiet
          model name: Intel(R) Core(TM) i5-4440 CPU @ 3.10GHz
               cores: 4
             cpu MHz: 1935.655
             parport: 0000-0000 : parport0
              serial: 0000-0000 : serial

Versions:
                 gcc: gcc (Debian 8.3.0-6) 8.3.0
              python: Python 2.7.16
                 git: not_in_PATH
          git commit: NA
                 tcl: 8.6
                  tk: 8.6
               glade: not_in_PATH
          glade-gtk2: not_in_PATH

linuxcnc_var all:

     LINUXCNCVERSION: 2.8.4-1-gb7824717b
LINUXCNC_AUX_GLADEVCP: /usr/share/linuxcnc/aux_gladevcp
LINUXCNC_AUX_EXAMPLES: /usr/share/linuxcnc/aux_examples
            REALTIME: /etc/init.d/realtime
                 RTS: uspace
          HALLIB_DIR: /usr/share/linuxcnc/hallib

dpkg -l '*linuxcnc*':
Gewünscht=Unbekannt/Installieren/R=Entfernen/P=Vollständig Löschen/Halten
| Status=Nicht/Installiert/Config/U=Entpackt/halb konFiguriert/
         Halb installiert/Trigger erWartet/Trigger anhängig
|/ Fehler?=(kein)/R=Neuinstallation notwendig (Status, Fehler: GROSS=schlecht)
||/ Name                Version              Architektur  Beschreibung
+++-===================-====================-============-=====================================================================
un  linuxcnc            <keine>              <keine>      (keine Beschreibung vorhanden)
un  linuxcnc-dev        <keine>              <keine>      (keine Beschreibung vorhanden)
un  linuxcnc-doc        <keine>              <keine>      (keine Beschreibung vorhanden)
ii  linuxcnc-doc-en     1:2.8.4.1.gb7824717b all          motion controller for CNC machines and robots (English documentation)
ii  linuxcnc-doc-es     1:2.8.4.1.gb7824717b all          controlador de movimiento para máquinas CNC y robots (Español).
ii  linuxcnc-doc-fr     1:2.8.4.1.gb7824717b all          motion controller for CNC machines and robots (French documentation)
un  linuxcnc-sim        <keine>              <keine>      (keine Beschreibung vorhanden)
un  linuxcnc-sim-dev    <keine>              <keine>      (keine Beschreibung vorhanden)
ii  linuxcnc-uspace     1:2.8.4.1.gb7824717b amd64        motion controller for CNC machines and robots
ii  linuxcnc-uspace-dev 1:2.8.4.1.gb7824717b amd64        PC based motion controller for real-time Linux
Displaying 11611 - 11625 out of 16735 results.
  1. Forum
  3. Search
Time to create page: 0.401 seconds
Powered by Kunena Forum