Advanced Search

Thanks for the answer.
I will respect that. It's just a matter of opinion.
I mostly work as an LCNC integrator, or teach someone. So I often need to switch between several tools and always have to go back.

Sometimes after using those three buttons I get stuck on the TOOL_PAGE page. Now I know that this is a bug. That's also why I opened this thread.

Thank you for your reply!
That's already the right direction, but I'm more interested in the commands like:
"net joint.0-pos-cmd <= joint.0.motor-pos-cmd"
These are the commands I would like to understand!

Next, I would like to understand which pins I can connect to which.
I often get a message like:
"you cannot connect this pin since PinX has already been connected to PinY"

Maybe this helps:
linuxcnc.org/docs/html/hal/basic-hal.html

I need to set the jog increment to a specific value and bind it to a key, let's say 'e'.  I'm using the Axis GUI so the key binding is done like this in .axisrc, which works:

root_window.bind( "<e>", set_jog_inc_precise )

The contents of the function set_jog_inc_precise is the issue.  I've tried the following

vars.jog.increment.set( "0.001" )

linuxcnc.command().jog( linuxcnc.JOG_INCREMENT, True, 0, 10, 0.001 )

j = root_window.nametowidget( ".pane.top.jogspeed.jogincrement")
j.set( "0.001" )

root_window.tk.eval( "set jogincrement 0.001" )
commands.set_jog_increments()

Only the second (linuxcnc.command()...) had an effect.  It actually jogged the axis, when I was watching the DRO.  So when I press "e" it would jog X 0.001 in the positive direction but when I used the arrow, it jogged X based on the drop-down menu in the Manual Control tab.

The backstory is that I have a pendant that isn't supported and have managed to map it from /dev/hidraw<n> to a virtual keyboard.  Most of the buttons work but the relative adjustment of the jog increment (i, I) is not the best because the dial on the pendant is labeled and it's easy to get out of sync. 

I've spent a few hours trying to get this working, reviewed the documentation for the python linuxcnc module, and even asked a few chatbots.  What am I doing wrong?

UPDATE:
After i stopped the servo from spinning on it´s own I went on to setup the limits and the X-Axis ran away like carzy, you´d give 0,05V on to the servo drive and it would react with max speed. I was confused since everything worked fine with 0,02V.
From the other axis i knew it should behave diffrent and should have a slow smooth motion with 0,5V

I´ve swapped the drives with each other, same
I´ve swapped the driver with a new one, same
I´ve checked the wiring, everything on the correct terminal.
I´ve checked the Tacho signal: 0V - THATS IT. The servodrive trys to keep up with the command, but since the Servo isn´t moving it gives even more power until it goes into fault or the axis crashes.

So i was sure the servo is cooked. I was already checking the sister machine for a spare Servo, already loosening the screws and was kinda like:
"oh let´s first remove the broken one".

As i pulled the cables i noticed the cable to the Tacho was ripped out INSIDE the screw thingy where the cable enters the housing. I repaired the wiring and voilá, servo works as expected.

So long story short, the previous owner already had the ripped wire and tried to fix it with tuning the drive, just like i did. The real problem was the severed cable to the tacho.

I've just heard back from the team at Leadshine.

It looks like the EL7 drives have a 0.0625ms delay on the encoder outputs.

Know people have had an issue with the 5ms delay on the DMM drives. Anyone think this might be an issue?

I've just enquired regarding any delay from analog velocity signal to drive reaction, which I assume would effect tuning as well.

Thanks,

J

Hey,
I'm currently working on configuring different setups using various Mesa boards (7i96S and 7i95T).
For creating the configurations, I’ve been using either the pncconf Wizard or Mesact. Unfortunately, neither tool seems to produce fully working configurations for my particular setup.That’s why I’m now trying to better understand which HAL functions are actually necessary.
Specifically, I’d like to learn what the different pins mean and how they should be connected in a way that makes sense.Could you point me toward some resources or documentation that would help me learn these basics?

Thanks a lot for your time!

Thank you very much - zz912.
Your last change is now working.
Regards, Hermann

Yes, that is a wanted behavior!
All the mentioned buttons leads to a tool change, so after that for sure you want to go on with your work, so why do you want to stay in tool table page?

Norbert

Thank you. The system I am working on is a water jet with dual cutting heads< two x and two z-axis, I use x and u as x2, and for the z, I used the problem I face is understanding how to implement the slave master on the x-axis and keep the z-axis independent,

Thank you so much. I have taken a look, and the difficulty is understanding the right way to implement the edit of the HAl and ini files to adapt this< I tried using gantrykins, but it wouldn't recognize this, is there a way to make slave and master axis once again you

Nah my images do work out the box, fark I can actually test them before releasing them in the wild, so far the zram issue has only affected one user. Which whilst I have wanted to put up a new image with the fix there has been push back.
The issue that seems to be with the RPi images is that users think that everything is the same as the images from Raspberry Pi, it's like they can't seperate the board from a particular OS.
The fact that I can run mine with either a 7c81 clone that I've put together myself or a Spartan 6 Dev board with an ethernet interface both running slightly modified hostmot2 firmware proves that it does work. Oh and the RPi platform is younger than the whole Linuxcnc project itself....
But an x86 platform is the best bang for buck, no 2 ways about it. You buy a PC and it's complete ready to go. An RPi5 will need a case, PSU a secondary board to run a NVMe drive or a SATA adaptor board if you want something more spritely than an SD card. The x86 platform is tried and true, it works, it's common, it's rugged and has been used it 54 billion installations by Tommy alone this month, as my estimates go.
The only advantage of the RPi platform is size, tho an Odroid H4 or the older H3 isn't much larger and maybe the SPI interface. The mini HDMI connectors are a pain. In saying that waveshare does do some nice boards that plugin to the existing HDMI, power and audio connectors to bring them out to the same side as the USB & ethernet, a nice NVMe adaptor and a aluminium case to suit.

Quiet PC will mean nothing in a workshop.
I've never been a fan of the Atom platform, those small form factor PC's run hot, even just sitting in an open room my industrial PC running pfsense needs a reboot every day or so in summer.
Your mileage may vary but just be aware of the heat issue.
If you want dual NICs in a small form factor I'd choose an Odroid H4 and just bung it in the CNC enclosure, my H3 has never given a issue, even when running in the Australian summer.