Search Results (Searched for: )
- hitchhiker
- hitchhiker
23 Aug 2025 08:24 - 23 Aug 2025 11:02
Replied by hitchhiker on topic Homing with 2 inputs/sensors?
Homing with 2 inputs/sensors?
Category: HAL
ahhhhaaaaa...
i think i got the firmware fixed on my table/labor mesa 7i92....
to explain:
I have everytime i configurate a new machine or want to try something a mesa 7i92 for learning on my table...
i load the firmware file for the 7i96 and look into it and found the example where index on a stepgen was attached.
Download:
link to the 7i96 firmware files
then extract and look for:
PIN_7I96_StepIDXD_51.vhd
then i saw in the file:
(StepGenTag, x"C2", ClockLowTag, x"04", StepGenRateAddr&PadT, StepGenNumRegs, x"00", StepGenMPBitMask),
bingo!
i add the stuff to my 7i92 bitfile...
and tada after flash i saw this in my terminal output:
this is how it must look, right?
thanks
i think i got the firmware fixed on my table/labor mesa 7i92....
to explain:
I have everytime i configurate a new machine or want to try something a mesa 7i92 for learning on my table...
i load the firmware file for the 7i96 and look into it and found the example where index on a stepgen was attached.
Download:
link to the 7i96 firmware files
then extract and look for:
PIN_7I96_StepIDXD_51.vhd
then i saw in the file:
(StepGenTag, x"C2", ClockLowTag, x"04", StepGenRateAddr&PadT, StepGenNumRegs, x"00", StepGenMPBitMask),
bingo!
i add the stuff to my 7i92 bitfile...
library IEEE;
use IEEE.std_logic_1164.all; -- defines std_logic types
use IEEE.STD_LOGIC_ARITH.ALL;
use IEEE.STD_LOGIC_UNSIGNED.ALL;
-- Copyright (C) 2007, Peter C. Wallace, Mesa Electronics
-- http://www.mesanet.com
--
-- This program is is licensed under a disjunctive dual license giving you
-- the choice of one of the two following sets of free software/open source
-- licensing terms:
--
-- * GNU General Public License (GPL), version 2.0 or later
-- * 3-clause BSD License
--
--
-- The GNU GPL License:
--
-- This program is free software; you can redistribute it and/or modify
-- it under the terms of the GNU General Public License as published by
-- the Free Software Foundation; either version 2 of the License, or
-- (at your option) any later version.
--
-- This program is distributed in the hope that it will be useful,
-- but WITHOUT ANY WARRANTY; without even the implied warranty of
-- MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
-- GNU General Public License for more details.
--
-- You should have received a copy of the GNU General Public License
-- along with this program; if not, write to the Free Software
-- Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
--
--
-- The 3-clause BSD License:
--
-- Redistribution and use in source and binary forms, with or without
-- modification, are permitted provided that the following conditions
-- are met:
--
-- * Redistributions of source code must retain the above copyright
-- notice, this list of conditions and the following disclaimer.
--
-- * Redistributions in binary form must reproduce the above
-- copyright notice, this list of conditions and the following
-- disclaimer in the documentation and/or other materials
-- provided with the distribution.
--
-- * Neither the name of Mesa Electronics nor the names of its
-- contributors may be used to endorse or promote products
-- derived from this software without specific prior written
-- permission.
--
--
-- Disclaimer:
--
-- THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
-- "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
-- LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
-- FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
-- COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
-- INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
-- BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
-- LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
-- CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-- LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
-- ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
-- POSSIBILITY OF SUCH DAMAGE.
--
use work.IDROMConst.all;
package PIN_VMC100 is
constant ModuleID : ModuleIDType :=(
(HM2DPLLTag, x"00", ClockLowTag, x"01", HM2DPLLBaseRateAddr&PadT, HM2DPLLNumRegs, x"00", HM2DPLLMPBitMask),
(WatchDogTag, x"00", ClockLowTag, x"01", WatchDogTimeAddr&PadT, WatchDogNumRegs, x"00", WatchDogMPBitMask),
(IOPortTag, x"00", ClockLowTag, x"02", PortAddr&PadT, IOPortNumRegs, x"00", IOPortMPBitMask),
(QcountTag, x"02", ClockLowTag, x"01", QcounterAddr&PadT, QCounterNumRegs, x"00", QCounterMPBitMask),
(StepGenTag, x"C2", ClockLowTag, x"04", StepGenRateAddr&PadT, StepGenNumRegs, x"00", StepGenMPBitMask),
(PWMTag, x"00", ClockHighTag, x"00", PWMValAddr&PadT, PWMNumRegs, x"00", PWMMPBitMask),
(LEDTag, x"00", ClockLowTag, x"01", LEDAddr&PadT, LEDNumRegs, x"00", LEDMPBitMask),
(NullTag, x"00", NullTag, x"00", NullAddr&PadT, x"00", x"00", x"00000000"),
(NullTag, x"00", NullTag, x"00", NullAddr&PadT, x"00", x"00", x"00000000"),
(NullTag, x"00", NullTag, x"00", NullAddr&PadT, x"00", x"00", x"00000000"),
(NullTag, x"00", NullTag, x"00", NullAddr&PadT, x"00", x"00", x"00000000"),
(NullTag, x"00", NullTag, x"00", NullAddr&PadT, x"00", x"00", x"00000000"),
(NullTag, x"00", NullTag, x"00", NullAddr&PadT, x"00", x"00", x"00000000"),
(NullTag, x"00", NullTag, x"00", NullAddr&PadT, x"00", x"00", x"00000000"),
(NullTag, x"00", NullTag, x"00", NullAddr&PadT, x"00", x"00", x"00000000"),
(NullTag, x"00", NullTag, x"00", NullAddr&PadT, x"00", x"00", x"00000000"),
(NullTag, x"00", NullTag, x"00", NullAddr&PadT, x"00", x"00", x"00000000"),
(NullTag, x"00", NullTag, x"00", NullAddr&PadT, x"00", x"00", x"00000000"),
(NullTag, x"00", NullTag, x"00", NullAddr&PadT, x"00", x"00", x"00000000"),
(NullTag, x"00", NullTag, x"00", NullAddr&PadT, x"00", x"00", x"00000000"),
(NullTag, x"00", NullTag, x"00", NullAddr&PadT, x"00", x"00", x"00000000"),
(NullTag, x"00", NullTag, x"00", NullAddr&PadT, x"00", x"00", x"00000000"),
(NullTag, x"00", NullTag, x"00", NullAddr&PadT, x"00", x"00", x"00000000"),
(NullTag, x"00", NullTag, x"00", NullAddr&PadT, x"00", x"00", x"00000000"),
(NullTag, x"00", NullTag, x"00", NullAddr&PadT, x"00", x"00", x"00000000"),
(NullTag, x"00", NullTag, x"00", NullAddr&PadT, x"00", x"00", x"00000000"),
(NullTag, x"00", NullTag, x"00", NullAddr&PadT, x"00", x"00", x"00000000"),
(NullTag, x"00", NullTag, x"00", NullAddr&PadT, x"00", x"00", x"00000000"),
(NullTag, x"00", NullTag, x"00", NullAddr&PadT, x"00", x"00", x"00000000"),
(NullTag, x"00", NullTag, x"00", NullAddr&PadT, x"00", x"00", x"00000000"),
(NullTag, x"00", NullTag, x"00", NullAddr&PadT, x"00", x"00", x"00000000"),
(NullTag, x"00", NullTag, x"00", NullAddr&PadT, x"00", x"00", x"00000000")
);
constant PinDesc : PinDescType :=(
-- Base func sec unit sec func sec pin -- 26 HDR -- IDC DB25
IOPortTag & x"00" & StepGenTag & StepGenIndexPin, -- I/O 00 PIN 1 PIN 1 just GPIO
IOPortTag & x"01" & StepGenTag & StepGenIndexPin, -- I/O 01 PIN 2 PIN 14 just GPIO
IOPortTag & x"02" & StepGenTag & StepGenIndexPin, -- I/O 02 PIN 3 PIN 2 just GPIO
IOPortTag & x"00" & NullTag & NullPin, -- I/O 03 PIN 4 PIN 15 just GPIO
IOPortTag & x"00" & NullTag & NullPin, -- I/O 04 PIN 5 PIN 3 just GPIO
IOPortTag & x"00" & NullTag & NullPin, -- I/O 05 PIN 6 PIN 16 just GPIO
IOPortTag & x"00" & NullTag & NullPin, -- I/O 06 PIN 7 PIN 4 just GPIO
IOPortTag & x"00" & NullTag & NullPin, -- I/O 07 PIN 8 PIN 17 just GPIO
IOPortTag & x"00" & NullTag & NullPin, -- I/O 08 PIN 9 PIN 5 just GPIO
IOPortTag & x"00" & NullTag & NullPin, -- I/O 09 PIN 11 PIN 6 just GPIO
IOPortTag & x"00" & NullTag & NullPin, -- I/O 10 PIN 13 PIN 7 just GPIO
IOPortTag & x"00" & NullTag & NullPin, -- I/O 11 PIN 15 PIN 8 just GPIO
IOPortTag & x"00" & NullTag & NullPin, -- I/O 12 PIN 17 PIN 9 just GPIO
IOPortTag & x"00" & NullTag & NullPin, -- I/O 13 PIN 19 PIN 10 just GPIO
IOPortTag & x"00" & NullTag & NullPin, -- I/O 14 PIN 21 PIN 11 just GPIO
IOPortTag & x"00" & NullTag & NullPin, -- I/O 15 PIN 23 PIN 12 just GPIO
IOPortTag & x"00" & NullTag & NullPin, -- I/O 16 PIN 25 PIN 13 just GPIO
-- 26 HDR -- IDC DB25
IOPortTag & x"00" & NullTag & NullPin, -- I/O 17 PIN 1 PIN 1 just GPIO
IOPortTag & x"00" & NullTag & NullPin, -- I/O 18 PIN 2 PIN 14 just GPIO
IOPortTag & x"00" & StepGenTag & StepGenStepPin, -- I/O 19 PIN 3 PIN 2 X Step
IOPortTag & x"00" & NullTag & NullPin, -- I/O 20 PIN 4 PIN 15 just GPIO
IOPortTag & x"00" & StepGenTag & StepGenDirPin, -- I/O 21 PIN 5 PIN 3 X Dir
IOPortTag & x"00" & NullTag & NullPin, -- I/O 22 PIN 6 PIN 16 just GPIO
IOPortTag & x"01" & StepGenTag & StepGenStepPin, -- I/O 23 PIN 7 PIN 4 Y Step
IOPortTag & x"00" & NullTag & NullPin, -- I/O 24 PIN 8 PIN 17 just GPIO
IOPortTag & x"01" & StepGenTag & StepGenDirPin, -- I/O 25 PIN 9 PIN 5 Y Dir
IOPortTag & x"02" & StepGenTag & StepGenStepPin, -- I/O 26 PIN 11 PIN 6 Z Step
IOPortTag & x"02" & StepGenTag & StepGenDirPin, -- I/O 27 PIN 13 PIN 7 Z Dir
IOPortTag & x"00" & NullTag & NullPin, -- I/O 28 PIN 15 PIN 8 Spindle on/off
IOPortTag & x"03" & StepGenTag & StepGenStepPin, -- I/O 29 PIN 17 PIN 9 Spindle Step
IOPortTag & x"03" & StepGenTag & StepGenDirPin, -- I/O 30 PIN 19 PIN 10 Spindle Dir
IOPortTag & x"00" & QCountTag & QCountIdxPin, -- I/O 31 PIN 21 PIN 11 (Encoder Quad Idx)
IOPortTag & x"00" & QCountTag & QCountQAPin, -- I/O 32 PIN 23 PIN 12 (Encoder Quad A)
IOPortTag & x"00" & QCountTag & QCountQBPin, -- I/O 33 PIN 25 PIN 13 (Encoder Quad B)
emptypin,emptypin,emptypin,emptypin,emptypin,emptypin,emptypin,emptypin, -- added for 34 pin 5I25
emptypin,emptypin,emptypin,emptypin,emptypin,emptypin,
emptypin,emptypin,emptypin,emptypin,emptypin,emptypin,emptypin,emptypin, -- added for IDROM v3
emptypin,emptypin,emptypin,emptypin,emptypin,emptypin,emptypin,emptypin,
emptypin,emptypin,emptypin,emptypin,emptypin,emptypin,emptypin,emptypin,
emptypin,emptypin,emptypin,emptypin,emptypin,emptypin,emptypin,emptypin,
emptypin,emptypin,emptypin,emptypin,emptypin,emptypin,emptypin,emptypin,
emptypin,emptypin,emptypin,emptypin,emptypin,emptypin,emptypin,emptypin,
emptypin,emptypin,emptypin,emptypin,emptypin,emptypin,emptypin,emptypin,
emptypin,emptypin,emptypin,emptypin,emptypin,emptypin,emptypin,emptypin,
emptypin,emptypin,emptypin,emptypin,emptypin,emptypin,emptypin,emptypin,
emptypin,emptypin,emptypin,emptypin,emptypin,emptypin,emptypin,emptypin,
emptypin,emptypin,emptypin,emptypin,emptypin,emptypin,emptypin,emptypin,
emptypin,emptypin,emptypin,emptypin,emptypin,emptypin,emptypin,emptypin);
end package PIN_VMC100;
Configuration Name: HOSTMOT2
General configuration information:
BoardName : MESA7I92
FPGA Size: 20 KGates
FPGA Pins: 256
Number of IO Ports: 2
Width of one I/O port: 17
Clock Low frequency: 100.0000 MHz
Clock High frequency: 175.0000 MHz
IDROM Type: 3
Instance Stride 0: 4
Instance Stride 1: 64
Register Stride 0: 256
Register Stride 1: 256
Modules in configuration:
Module: DPLL
There are 1 of DPLL in configuration
Version: 0
Registers: 7
BaseAddress: 7000
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes
Module: WatchDog
There are 1 of WatchDog in configuration
Version: 0
Registers: 3
BaseAddress: 0C00
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes
Module: IOPort
There are 2 of IOPort in configuration
Version: 0
Registers: 5
BaseAddress: 1000
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes
Module: QCount
There are 1 of QCount in configuration
Version: 2
Registers: 5
BaseAddress: 3000
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes
Module: StepGen
There are 4 of StepGen in configuration
Version: 194
Registers: 10
BaseAddress: 2000
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes
Module: PWM
There are 0 of PWM in configuration
Version: 0
Registers: 5
BaseAddress: 4100
ClockFrequency: 175.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes
Module: LED
There are 1 of LED in configuration
Version: 0
Registers: 1
BaseAddress: 0200
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes
Configuration pin-out:
IO Connections for P2
DB25 pin# I/O Pri. func Sec. func Chan Sec. Pin func Sec. Pin Dir
1 0 IOPort StepGen 0 Index (In)
14 1 IOPort StepGen 1 Index (In)
2 2 IOPort StepGen 2 Index (In)
15 3 IOPort None
3 4 IOPort None
16 5 IOPort None
4 6 IOPort None
17 7 IOPort None
5 8 IOPort None
6 9 IOPort None
7 10 IOPort None
8 11 IOPort None
9 12 IOPort None
10 13 IOPort None
11 14 IOPort None
12 15 IOPort None
13 16 IOPort None
IO Connections for P1
DB25 pin# I/O Pri. func Sec. func Chan Sec. Pin func Sec. Pin Dir
1 17 IOPort None
14 18 IOPort None
2 19 IOPort StepGen 0 Step/Table1 (Out)
15 20 IOPort None
3 21 IOPort StepGen 0 Dir/Table2 (Out)
16 22 IOPort None
4 23 IOPort StepGen 1 Step/Table1 (Out)
17 24 IOPort None
5 25 IOPort StepGen 1 Dir/Table2 (Out)
6 26 IOPort StepGen 2 Step/Table1 (Out)
7 27 IOPort StepGen 2 Dir/Table2 (Out)
8 28 IOPort None
9 29 IOPort StepGen 3 Step/Table1 (Out)
10 30 IOPort StepGen 3 Dir/Table2 (Out)
11 31 IOPort QCount 0 Quad-IDX (In)
12 32 IOPort QCount 0 Quad-A (In)
13 33 IOPort QCount 0 Quad-B (In)
this is how it must look, right?
thanks
- rodw
23 Aug 2025 07:49
Replied by rodw on topic Debian Trixie upgrade/install to 2.9.4
Debian Trixie upgrade/install to 2.9.4
Category: Installing LinuxCNC
Great feedback. Nothing to worry about. The etherlabmaster's certificate in their repository only has a life of 2 years. If you are not using ethercat, there is nothing to worry about. It is outside of our control.
- jjdege
23 Aug 2025 07:03
Replied by jjdege on topic Debian Trixie upgrade/install to 2.9.4
Debian Trixie upgrade/install to 2.9.4
Category: Installing LinuxCNC
Good morning,
I followed Rodw's instructions (thanks, Rodw), and upgraded from Bookworm to Trixie.
I can say that everything is fine. I only had two problems:
Several packages weren't installing automatically; they were always in the update list.
I installed them manually and solved the problem.
The Network Manager GUI in the top-right panel wouldn't start, and it was impossible to manage the network
with a graphical interface.
I solved the problem by searching online.
The thing that worries me is the warning that appears after I update from the terminal.
What does this warning mean?
Thanks
I followed Rodw's instructions (thanks, Rodw), and upgraded from Bookworm to Trixie.
I can say that everything is fine. I only had two problems:
Several packages weren't installing automatically; they were always in the update list.
I installed them manually and solved the problem.
The Network Manager GUI in the top-right panel wouldn't start, and it was impossible to manage the network
with a graphical interface.
I solved the problem by searching online.
The thing that worries me is the warning that appears after I update from the terminal.
What does this warning mean?
Thanks
- hitchhiker
- hitchhiker
23 Aug 2025 06:56 - 23 Aug 2025 07:16
Replied by hitchhiker on topic Homing with 2 inputs/sensors?
Homing with 2 inputs/sensors?
Category: HAL
Hi
If i understand correct... i must change the firmware on my 7i92?
I need to add encoder to the bitfile.. but only the index? So it must be a index that is coming from the stepgen.. i only know how to add stepgen with step and dir to the bitfile..
I run the stepgen in position mode ..not velocity..
So instead what i try with the gpio i need a index pin in the bitfile which is linked to the stepgen, right?
Sorry i am a little bit confused and doesnt understand it.. i use linuxcnc 2.9 and a mesa 7i92. Changing the bitfile/firmware is not a problem. But i look everytime to existing files and copy from them... and i cant find a documentation about it...
it should be look like:
IOPortTag & x"NN" & StepGenTag & StepGenIndexPin, "
but i never saw something like this...
thanks
If i understand correct... i must change the firmware on my 7i92?
I need to add encoder to the bitfile.. but only the index? So it must be a index that is coming from the stepgen.. i only know how to add stepgen with step and dir to the bitfile..
I run the stepgen in position mode ..not velocity..
So instead what i try with the gpio i need a index pin in the bitfile which is linked to the stepgen, right?
Sorry i am a little bit confused and doesnt understand it.. i use linuxcnc 2.9 and a mesa 7i92. Changing the bitfile/firmware is not a problem. But i look everytime to existing files and copy from them... and i cant find a documentation about it...
it should be look like:
IOPortTag & x"NN" & StepGenTag & StepGenIndexPin, "
but i never saw something like this...
thanks
- pippin88
- pippin88
23 Aug 2025 04:28
Replied by pippin88 on topic Set program zero using XY positioning laser
Set program zero using XY positioning laser
Category: Advanced Configuration
Please post your full config files
- MikkelRS
23 Aug 2025 01:21
Replied by MikkelRS on topic For Those Who Have to Use Windows
For Those Who Have to Use Windows
Category: Off Topic and Test Posts
Remember that first 64 bit desktop OS... BeOS?
If you ever ran that for a bit, incomplete was its epitaph haha.
If you ever ran that for a bit, incomplete was its epitaph haha.
- Todd Zuercher
23 Aug 2025 01:10
Replied by Todd Zuercher on topic Displaying Active Work Coordinate System
Displaying Active Work Coordinate System
Category: GladeVCP
I had noticed that just after I posted it, but I thought I tried uncommenting it and it I didn't think it seemed to make any difference. (Error messages were still the same and the Label didn't change.)
But I thought I had better test again before posting a reply. I loaded up a 2.7 Wheezy live cd image in a VM and ran a simulation with this GladeVCP files (and that line uncommented, and it works! I don't know maybe I forgot to save after uncommenting that line earlier today. But I'll have to wait until Monday to try it out on the real machine at work.
Thanks alot for your help.
PS any ideas on these other "error" messages that show up in the terminal but with no noticeable effect on functionality.
But I thought I had better test again before posting a reply. I loaded up a 2.7 Wheezy live cd image in a VM and ran a simulation with this GladeVCP files (and that line uncommented, and it works! I don't know maybe I forgot to save after uncommenting that line earlier today. But I'll have to wait until Monday to try it out on the real machine at work.
Thanks alot for your help.
PS any ideas on these other "error" messages that show up in the terminal but with no noticeable effect on functionality.
File "/usr/lib/pymodules/python2.7/gladevcp/hal_actions.py", line 99, in _f
return f(self, *a, **kw)
File "/usr/lib/pymodules/python2.7/gladevcp/hal_actions.py", line 461, in on_activate
ensure_mode(self.stat, self.linuxcnc, linuxcnc.MODE_MDI)
AttributeError: 'EMC_Action_MDI' object has no attribute 'stat'
Traceback (most recent call last):
File "/usr/lib/pymodules/python2.7/gladevcp/hal_actions.py", line 99, in _f
return f(self, *a, **kw)
File "/usr/lib/pymodules/python2.7/gladevcp/hal_actions.py", line 461, in on_activate
ensure_mode(self.stat, self.linuxcnc, linuxcnc.MODE_MDI)
AttributeError: 'EMC_Action_MDI' object has no attribute 'stat'
Traceback (most recent call last):
File "/usr/lib/pymodules/python2.7/gladevcp/hal_actions.py", line 99, in _f
return f(self, *a, **kw)
File "/usr/lib/pymodules/python2.7/gladevcp/hal_actions.py", line 461, in on_activate
ensure_mode(self.stat, self.linuxcnc, linuxcnc.MODE_MDI)
- tommylight
23 Aug 2025 00:14
Replied by tommylight on topic Türkçe
Türkçe
Category: Other Languages
Sorry for the late reply, but i was waiting for someone else to reply as i am not sure if i can create a new section or not.
In the mean time, start a new topic here in Tyrkqe ? (is that correct) or rename this one and we will move or delete stuff around as needed.
In the mean time, start a new topic here in Tyrkqe ? (is that correct) or rename this one and we will move or delete stuff around as needed.
- cmorley
- cmorley
22 Aug 2025 21:57
Replied by cmorley on topic Displaying Active Work Coordinate System
Displaying Active Work Coordinate System
Category: GladeVCP
You have commented out the line that defines self.stat:
class HandlerClass:
def __init__(self, halcomp,builder,useropts):
self.builder = builder
self.halcomp = halcomp
# self.stat = linuxcnc.stat()
- PCW
22 Aug 2025 19:47
Replied by PCW on topic Stop feed when spindle rpm lower
Stop feed when spindle rpm lower
Category: AXIS
That's simpler than my solution using adaptive feed.
- Aciera
22 Aug 2025 19:16 - 22 Aug 2025 19:23
NativeCam has always output gcode in parametric form because it uses subroutines for it's operations (ie the output does not look like what you would expect on a regular 'CAM'). SO there may actually be nothing wrong with that output (except of course that it would need to be formatted properly)
Replied by Aciera on topic Nativecam running on 2.9.4 almost so close
Nativecam running on 2.9.4 almost so close
Category: NativeCAM
if I try exporting the project as gcode the .ngc file is mostly composed of stuff that looks like this:
NativeCam has always output gcode in parametric form because it uses subroutines for it's operations (ie the output does not look like what you would expect on a regular 'CAM'). SO there may actually be nothing wrong with that output (except of course that it would need to be formatted properly)
- Henk
- Henk
22 Aug 2025 18:56
Replied by Henk on topic Stop feed when spindle rpm lower
Stop feed when spindle rpm lower
Category: AXIS
I always impliment the following on my retrofits.
set up a spindle-at-speed signal in the usual way using encoder feedback and a near component.
invert it using a not component to set up a spindle-not-at-speed signal a d tie it to motion.feed-inhibit.
this will stop all motion when the spindle is not near enough to the commanded speed.
henk
set up a spindle-at-speed signal in the usual way using encoder feedback and a near component.
invert it using a not component to set up a spindle-not-at-speed signal a d tie it to motion.feed-inhibit.
this will stop all motion when the spindle is not near enough to the commanded speed.
henk
- Doug Crews
- Doug Crews
22 Aug 2025 18:31
Nativecam running on 2.9.4 almost so close was created by Doug Crews
Nativecam running on 2.9.4 almost so close
Category: NativeCAM
Hello everyone,I managed to get Nativecam loaded and running on the 2.9.4 iso, using the
github.com/freemoore/NativeCAM
download, and Giovanni’s instruction pdf plus all the corrections along the way. I ran a huge victory lap when I saw the Nativecam Tab in Axis not blank but how it supposed to look! But…..as usual the fight is not over and my troubleshooting skills are limited by my total lack of experience with Nativcam as I have never used it before.The problem is the Nativecam project is not dynamically updating in the Axis preview ,tab and if I try exporting the project as gcode the .ngc file is mostly composed of stuff that looks like this:I’ve been asking the AI questions about how Nativecam is supposed to work and I think its been mostly correct but is often describing how it “used to work” and not necessarily how it works now. My gut tells me the problem has something to do with a symbolic link or a missing ncam.ngc file. Any thoughts are greatly appreciated!-Doug
(begin Workpiece)(workpiece definition author : Fernand Veilleux) #<wp_width> = [5.906000]#<wp_length> = [13.780000]#<wp_depth> = [0.125000]#<wp_wall> = [0.000000]#<wp_corner_radius> = [0.000000]#<wp_inside_width> = [#<wp_width> - #<wp_wall> * 2]#<wp_inside_length> = [#<wp_length> - #<wp_wall> * 2] #<wp_x> = -2.953000#<wp_y> = 0.000000 o<select> CALL [31] [0] [-2.953000] [-2.953000 - #<wp_length> / 2] [-2.953000 - #<wp_length>]#<wp_left> = #31#<wp_right> = [#<wp_left> + #<wp_length>]
- timo
- timo
22 Aug 2025 17:44
Replied by timo on topic Machine crash
Machine crash
Category: AXIS
I was too upset, did not touch the machne since
lucky me the workpiece spindle and y motor are both not very strong, so no damage on tool or machine.

- Teknic_Servo
22 Aug 2025 14:07 - 22 Aug 2025 14:08
Replied by Teknic_Servo on topic Mesa 7i96S step and direction signals go high on power loss
Mesa 7i96S step and direction signals go high on power loss
Category: Driver Boards
Hello satiowadahc,
I’m an applications engineer for Teknic and I came across your post. I’m sorry that you’re experiencing undesirable machine movement during a controller shutdown while the servo drive is still enabled. You've been working with my colleague here (and it sounds like you've also been implementing some other protective measures on the machine) - it's possible you've already fixed the issue, but I thought it might be helpful to post some additional relevant information in case anyone else experiences something similar and sees your post.
If a controller sends a static 5V signal, the drive would not respond (there isn’t any way for the drive to interpret a single high state as a command for motion). The Eclipse drives will only respond to step pulses (specifically, the falling edge of the change in state from a step pulse).
Digital devices rely on a voltage threshold to define high versus low signals. As a controller powers down, its output may decay and fluctuate around this threshold, creating multiple false transitions that the drive interprets as steps. The oscilloscope shots that you sent over to Teknic suggest that this is likely what's happening to the signal on the step line (as your controller powers down).
For safety, we recommend shutting down by first removing power (or disabling) the motion-generating device, then powering down the controller. Powering down the controller first introduces a fair amount of uncertainty because shutdown behavior varies across different controller manufacturers and configurations.
If you find that there is also noise on the signal, there are step input filters that can be programmed into your Eclipse Servo Drive to help with noise filtering, if you haven’t already configured that (there is more information on this in the Eclipse User Manual – pages 19-20).
I’d also recommend (if you haven’t already done so) grounding the Step and Direction lines according to the manufacturer's documentation. There are also instructions in the Eclipse User Manual that explain how to properly ground the signals to Eclipse.
I hope that this information is helpful. If you have any questions, please feel free to give Teknic a call (or contact the engineer that you’ve already been working with).
Best,
Andy O. – Teknic Servo Systems Engineer
I’m an applications engineer for Teknic and I came across your post. I’m sorry that you’re experiencing undesirable machine movement during a controller shutdown while the servo drive is still enabled. You've been working with my colleague here (and it sounds like you've also been implementing some other protective measures on the machine) - it's possible you've already fixed the issue, but I thought it might be helpful to post some additional relevant information in case anyone else experiences something similar and sees your post.
If a controller sends a static 5V signal, the drive would not respond (there isn’t any way for the drive to interpret a single high state as a command for motion). The Eclipse drives will only respond to step pulses (specifically, the falling edge of the change in state from a step pulse).
Digital devices rely on a voltage threshold to define high versus low signals. As a controller powers down, its output may decay and fluctuate around this threshold, creating multiple false transitions that the drive interprets as steps. The oscilloscope shots that you sent over to Teknic suggest that this is likely what's happening to the signal on the step line (as your controller powers down).
For safety, we recommend shutting down by first removing power (or disabling) the motion-generating device, then powering down the controller. Powering down the controller first introduces a fair amount of uncertainty because shutdown behavior varies across different controller manufacturers and configurations.
If you find that there is also noise on the signal, there are step input filters that can be programmed into your Eclipse Servo Drive to help with noise filtering, if you haven’t already configured that (there is more information on this in the Eclipse User Manual – pages 19-20).
I’d also recommend (if you haven’t already done so) grounding the Step and Direction lines according to the manufacturer's documentation. There are also instructions in the Eclipse User Manual that explain how to properly ground the signals to Eclipse.
I hope that this information is helpful. If you have any questions, please feel free to give Teknic a call (or contact the engineer that you’ve already been working with).
Best,
Andy O. – Teknic Servo Systems Engineer
Time to create page: 0.258 seconds