Advanced Search

Search Results (Searched for: )

  • 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:
(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>]
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
  • timo
  • timo
22 Aug 2025 17:44 - 31 Oct 2025 09:47
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.

Months later.... it works. No file opened. 
  • Teknic_Servo
  • Teknic_Servo's Avatar
22 Aug 2025 14:07 - 22 Aug 2025 14:08

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
  • PCW
  • PCW's Avatar
22 Aug 2025 13:26
Replied by PCW on topic Homing with 2 inputs/sensors?

Homing with 2 inputs/sensors?

Category: HAL

As I explained, it is possible with firmware that has a stepgen index enable pin
No custom components are needed.
  • ts
  • ts
22 Aug 2025 13:10

classic ladder with rs232 clp connection

Category: ClassicLadder

Hi
Could you give more details please and example communication with rs232 serial port?

Best regards
Alexander
  • ts
  • ts
22 Aug 2025 12:59 - 23 Aug 2025 14:34
Replied by ts on topic Use of ODOT Ethercat coupler I/O?

Use of ODOT Ethercat coupler I/O?

Category: EtherCAT

Hi
Is your modules state PreOp or you switch them to OPstate?
Please could you share your xml files for linixcnc?
Ps working on the same task, try to connect odot 8033 with linixcnc 2.9.4 as i understood oncase of beckhoff each module - coupler, di, next on di, do, next one do, ai - each have own id in ethercat network. But as in case of odot, perhaps, only coupler have own address ethercat, other modules using special address register according position from the coupler.
  • Todd Zuercher
  • Todd Zuercher's Avatar
22 Aug 2025 10:58
Replied by Todd Zuercher on topic Displaying Active Work Coordinate System

Displaying Active Work Coordinate System

Category: GladeVCP

Well, not sure why but it isn't working.  I'm seeing several references to "object has no attribute 'stat'" in the terminal, the first 3 of which were there before adding this modification to the glade panel.   Any ideas what I'm doing wrong?

Here is what was printed to the terminal.
digital4@digital4:~/Desktop$ linuxcnc
LINUXCNC - 2.7.15-28-gd7ded6e
Machine configuration directory is '/home/digital4/linuxcnc/configs/Digital_4g'
Machine configuration file is 'double.ini'
Starting LinuxCNC...
.
Found file(REL): ./Digital_4w.hal
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)
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'
/usr/bin/gladevcp:212: RuntimeWarning: missing handler 'on_window1_destroy'
  builder.connect_signals(handlers)
Xlib.protocol.request.QueryExtension
Xlib.protocol.request.QueryExtension
Traceback (most recent call last):
  File "./double.py", line 47, in periodic_check
    self.stat.poll()
AttributeError: HandlerClass instance has no attribute 'stat'
^Ctask: 105602 cycles, min=0.000034, max=0.022691, avg=0.010203, 0 latency excursions (> 10x expected cycle time of 0.010000s)
Traceback (most recent call last):
  File "/usr/bin/axis", line 3549, in <module>
    o.mainloop()
  File "/usr/lib/python2.7/lib-tk/Tkinter.py", line 1035, in mainloop
    self.tk.mainloop(n)
  File "/usr/lib/python2.7/lib-tk/Tkinter.py", line 1432, in __call__
    def __call__(self, *args):
KeyboardInterrupt
Shutting down and cleaning up LinuxCNC...
  • emresensoy
  • emresensoy
22 Aug 2025 09:49 - 22 Aug 2025 15:05
Türkçe was created by emresensoy

Türkçe

Category: Other Languages

Dear moderators, I would like to open a Turkish section. If you find it appropriate, I can also serve as a moderator for Turkish section.
  • rodw
  • rodw's Avatar
22 Aug 2025 05:58
Replied by rodw on topic Homing with 2 inputs/sensors?

Homing with 2 inputs/sensors?

Category: HAL

It might not be a trivial solution, but you could write a custom home component that takes the two pins as input. eg rough, then fine.
Ref: linuxcnc.org/docs/stable/html/man/man9/homecomp.9.html
Linuxcnc does this using home_latch_velocity eg fast sensing, then slow for accuraccy on the one pin.
  • hitchhiker
  • hitchhiker
22 Aug 2025 05:01
Replied by hitchhiker on topic Homing with 2 inputs/sensors?

Homing with 2 inputs/sensors?

Category: HAL

Hi
Thanks for answer.
Its openloop. I think the second sensor that wait for the metal pin on the pulley makes the homing more accurate.

Sensor 1 rough homing to a reference marked area.
Sensor 2 then fine homing.
Call it 2 state homing?

Original is the secomd sensor used for 2 things..
Thing 1 homing accurate..
Thing 2 counts the pin everytime the pulley is turned full.
The full rotation means as example 400 steps done.. is the pin triggering the sensor befor or later then its out of position.
But i only want to use the secomd sensor for more precise homing.

This is not possible right? To make it possible it needs a special component or?

i found this:

github.com/mydani/linuxcnc_misc/blob/mai...e_index_stepdir.comp

looks like inside linuxcnc there is no other option.

thanks
  • cmorley
  • cmorley
22 Aug 2025 01:28 - 22 Aug 2025 01:31
Replied by cmorley on topic Displaying Active Work Coordinate System

Displaying Active Work Coordinate System

Category: GladeVCP

I think you need to add a timer to call a function to read linuxcnc's stat.
Here is most of the odea - not tested:

# add this at top:
import gobject

#add this to to bottom of __init__ :
# called every 100 ms
gobject.timeout_add(100, self.periodic_check)
self.last = 1
self.convert = { 1:"G54(Front)", 2:"G55(Rear)", 3:"56", 4:"57", 5:"58", 6:"59", 7:"59.1", 8:"59.2", 9:"59.3"}

# add this function
def periodic_check(self):
    self.stat.poll()
    current =  self.stat.g5x_index
    if current != self.last:
        text = self.convert[int(current)]
        # update label
        self.builder.get_object('work_coord_label').set_text(text)
    self.last = current
    return True
  • PCW
  • PCW's Avatar
21 Aug 2025 21:13 - 21 Aug 2025 21:31
Replied by PCW on topic Homing with 2 inputs/sensors?

Homing with 2 inputs/sensors?

Category: HAL

You cannot connect an output pin to joint.N.index-enable
because joint.N.index-enable pins are bidirectional ("Tri-State")

When index is used for homing, LinuxCNC expects to use encoder
hardware to detect the actual index pin and signal that detection
to LinuxCNC via the joint.N.index-enable pin. joint.N.index-enable
is used as a bidirectional signal, that is, when LinuxCNC detects the
coarse home position, it then sets joint.N.index-enable true. This signals
the hardware to enable index detection. When the index is detected,
the hardware normally does two things: it clears (sets to false)
joint.N.index-enable (signaling LinuxCNC that the index has been detected)
and normally also zeros the position.

Does this joint have encoder feedback or it this an open-loop step/dir system?

If no encoder (and you have an up-to-date LinuxCNC installation) , there is firmware
that supports homing to index in open loop step/dir systems, so instead of connecting
a GPIO pin to joint.N.index-enable you would connect to hm2_7i92.0.stepgen.NN.index-enable
to joint.N.index-enable.




 
  • hitchhiker
  • hitchhiker
21 Aug 2025 20:23
Homing with 2 inputs/sensors? was created by hitchhiker

Homing with 2 inputs/sensors?

Category: HAL

Hi!

i have here a axis which has 2 home sensors.
The first sensor is the reference.
the second is a sensor on the pulley.

how it works? Home to first sensor.. then go back until sensor 2 is active.

i the first sensor works on linuxcnc..then i add the second..
net index-sensor gpio001.... 
inet index-sensor joint...index-enable

but then i get error.. 

cant add i/o pin to index... its already output pin hm2_7192.0.gpio.005.in

in the ini i change the parameter for use index as true.. but this doesnt solve anything.

do i need to add a encoder in the bitfile or what is my failure??

thanks
  • Martin.L
  • Martin.L
21 Aug 2025 17:49 - 21 Aug 2025 17:59
Replied by Martin.L on topic Carousel ATC setup on Probe Basic

Carousel ATC setup on Probe Basic

Category: QtPyVCP

Understanding this is not a quick answer I drop here an AI analysis of your sample atc_sim config. Maybe it can be a good starting point?
  • scsmith1451
  • scsmith1451's Avatar
21 Aug 2025 16:02
Replied by scsmith1451 on topic Set program zero using XY positioning laser

Set program zero using XY positioning laser

Category: Advanced Configuration

After several attempt to use the _ini() variables in my macro to move the table to the x/y offset location, I've finally just hard coded the values into the macro.  While this is not the ideal implementation, it does keep the values in a single location should I need to modify them in the future.

At this point I now have all of my gvcp buttons working except the combo box to select the current coordinate system to use for a given job.  I'll work on that option at a later date.  The key frustration is the inability to jog once the laser is toggled.

This is particularly interesting in that both the spindle enable and the spindle coolant are enabled via relays as well and neither of them inhibit jogging after they are activated. 

Does anyone have any suggestions regarding why the laser might inhibit jogging? 

These are the HAL commands associated with the laser:

# *** Crosshair laser Toggle and LED ***
net machine-is-on => gladevcp.crosshair-ctl-active
net crosshair-toggle-out <= gladevcp.crosshair-toggle
net crosshair-toggle-out => hm2_5i25.0.7i76.0.0.output-02
net crosshair-toggle-out => gladevcp.crosshair-led

I don't see anything that might be interfering with jogging.

Spindle-enable and coolant-flood, (I'm using M8 to cool my spindle), are configured as follows:
# --- SPINDLE-ENABLE ---
net spindle-enable  =>     hm2_5i25.0.7i76.0.0.output-00

# --- COOLANT-FLOOD ---
net coolant-flood  =>     hm2_5i25.0.7i76.0.0.output-01

The main difference that I notice is that these function are activated by LCNC signals. Maybe there is something associate with these two signals that needs to be added to the laser activation process.

I'm open to any suggestions that might point me in the right direction to resolve this issue.

Kind regard,
 
Displaying 10801 - 10815 out of 17139 results.
Time to create page: 0.332 seconds
Powered by Kunena Forum