Advanced Search

Thankyou, I have expanded out to 3x drives and all working well.

I am accessing my LCNC via RDP and noticed that response to the gui slowed considerably while LCNC is running.

My fix was to set coalesce on the interfaces, here is my /etc/networks/interfaces where enp2s0 is my user interface / general network access and the eno1 is my ethercat interface.

cnc@cnc02:/etc/network$ cat interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

auto enp2s0
iface enp2s0 inet static
        address 10.1.1.14
        hardware-irq-coalesce-rx-usecs 0

auto eno1
iface eno1 inet manual
    hardware-irq-coalesce-rx-usecs 0


 

So if I were to use a different brand of analog servo, what value should the Drive scale be set to?

Baazengr wrote:

I am also having this issue. The controller hangs when i use outputs.
Any luck finding a solution?

Hi, I have been looking at this and cannot replicate the issue. Please share your config file as all the combinations I have tried work ok for me.

Hi,

I've got M6 remap running well from pure Python remap on my Biesse Rover 322 and now want to extend the script with manual tool changes for some tools.

Is it possible to call a default manual tool change from the python script, or do I need to build my own within the script? I foresee some possible hassles with cuebusting if building my own, that could be avoided if using the default one.

If building my own, would the attached script be a good place to start stealing from?

I'm retrofitting a Sodick 450MC, got most of the stuff working and running up to automatic tool change part, the tool changing arm is driven by the stepper motor,
​the stepper will rotate some fix turns to change tool
So how can I config stepggen for the stepper ? btw I'm using mesa 7i95 board
​​​​
​​​​

Sorry to be the barer of bad news, but there are several topics here discussing the DMM servos inability to run in analog mode due to very high latency of encoder feedback.
Use them in Position mode (step/dir) as this seems to work a bit better from what i read, although i never used them and after seeing how they handled the issue, i never will.

NickH wrote:

Looking at the above post, I don't recall installing headers separately. Maybe that is it.

These are also needed to install anything with dkms like the Realtek r8168-dkms network driver.

Dmclements wrote:

Not to mention network manager seems to be missing on the pi image, or at least there is no straightforward way of launching the gui for it from any menu I’ve looked in. So currently no internet connection on the pi, will work on that tomorrow.

Please read the notes on the download page to set up your wifi. Network manager adds latency.
Please follow the instructions  in man hm2_eth to set an IP address for your connection to your mesa card

How was this resolved? I'm using MesaCT v 2.1.4 to configure 7i97T+7i76 and I also have a spindle tab with all option grayed out. I'm planning to use the TB4 spindle output output on 7i76.

I'm using MesaCT to build a new configuration for a 3 axis mill with DMM servos in Analog mode.

I get the message that "Drive x Scale must not be blank".  Since scale is defined as "the number of pules to move one user unit", should this value be 0 for analog servos?

Thanks,

Skylor

I pushed some initial work.
If you use basic probe, setting the probe tool number in the tab will now also compare to the current tool number. If they match a HAL pin will be set (qtbasicprobe.probe-loaded)

In Versa probe, it works the same but at the moment you must set the probe number by editing the preference file - I ran out of room on the tab.
It's pin name is : qtversaprobe.probe-loaded

You would then connect that pin to spindle.o.inhibit.

I pushed this to master.
I changed a couple property names ( base_color and base_gradient_color) and added properties for the gauge center color (center_color, center_gradient_color)

Also added the details to the widget docs.

Qtdragon-hd now uses your new gauge styling to showcase the changes.
Thank you for this work!

Chris

sorry for not replying sooner. usually I get an email when a reply comes in. i also have not had time to tinker but i will check that out

Thanks Mecanix for helping us test. The 5.4.279 kernel shouldn't cause any regressions as it's all just backported fixes, and the respective LinuxCNC package for it restored some files I shouldn't have deleted in the earlier Debian package, so if anything it should be better and not worse, and this is a run-on-sentence.

On the servo enables and alarms is usually possible to combine all the
enables together so they can be driven by a single output, and likewise,
combine all the alarms so they drive a single input.

If you used a 7I96S, you may need to add a daughtercard to get enough I/O
The 7I95T probably has enough I/O but lacks the 0-10V. The lack of 0-10V
may not matter if the spindle drive can use an alternate speed control method
(also 0-10V can be added to the 7I95T with a  SPINX1 adapter)