Advanced Search

I've went through the pncconf wizard to set up a 7i76eu board. I can get the x-axis to job in Linuxcnc but the motors are not moving.  All wiring is connected correctly to the board and driver.  I know this because it was moving at one point and then i made the mistake of trying to swap from Axis to Probe Basic and ChatGpt was telling me to do some stuff that obviously messed it up.  So my files here are the result of going through the set up wizard a second time.  It's not the originals.  I'm essentially trying to get back to where i was.  I have communication with the board.  DMM Dyn4 drivers has a solid green light on the front of each.  The only thing of note worthy is the Z-Axis pins from the driver are connected to the Step 0 pins on TB2, X axis on Step 1 pins, and Y axis on Step 2 pins.  This is due to short cables and i don't want to move them.  I made these changes in the wizard too.Can anyone take a look at my Hal and Ini files to see any issues?  I'm attaching the files and TXT files for reading.

Linuxcnc fails at startup and just sits there.

My machine does not show the error logs unless I start from terminal.

My machine has been working flawlessly for a number of years and it seems that I have forgotten how to start  it from the terminal.

2.7 debian stretch.

Hi! The LinuxCNC ISO distribution includes Raspberry Pi firmware packages (raspi-firmware) that serve no purpose on AMD64 systems since they're specifically designed for Raspberry Pi hardware. However, these packages create a significant problem: they prevent the installation of other firmware packages that are actually needed for proper hardware support on x86_64 systems. The main issue is with Realtek Ethernet hardware, which requires specific firmware to function correctly. The presence of raspi-firmware packages blocks the installation of these necessary Realtek firmware packages, leaving users with non-functional network adapters.

This is essentially a packaging conflict where Pi-specific firmware interferes with the installation of legitimate x86_64 hardware drivers. The fix is straightforward but important for users who need working Ethernet connectivity (Realtek).

Temporary solution: apt purge raspi-firmware

kworm wrote:

Thanks Tommy. The attached files will support the 7i97t.  I created a config successfully but I don't have a card to test with so maybe the OP or someone can give it a try and let me know if it works.  I can send in a pull request if it's good.   This will only work with 2.10 master.

After updating to latest master just copy the attached private_data.py file to /usr/lib/python3/dist-packages/pncconf/ and the pncconf.py to /usr/bin/pncconf

I would suggest making a backup copies of the original files first just in case.
 

Can I send you a 7I97T?
 

Studying the XHC-WHB04B-6 component and configuration with Qtplasmac.

I have these hal connections in my Qtplasmac hal file:

net    plasmac:program-pause         plasmac.program-pause       =>     halui.program.pause
net    plasmac:program-resume       plasmac.program-resume     =>     halui.program.resume
net    plasmac:program-run              plasmac.program-run           =>      halui.program.runHowever,

I also wish to connect the following XHC wireless pendant pins to the above hal pins.

whb.halui.program.pause 
whb.halui.program.resume
whb.halui.program.run

So do I need 2 input OR components to do this, example:

plasmac.program-resume
               OR                                                                    gives out:                         halui.program.resume
whb.halui.program.resume

My question rabbit hole goes deeper.
Is it possible that say my plasmac.program-run pin is logic HIGH, but then from the pendant the whb.halui.program.pause pin goes HIGH also, creating a “command conflict”.

Confused about all this at the moment.

Hello i am pretty new with linux and aslo with linuxcnc, i know the basic things about programing, i can do that a scara can move into my control board, but i have a question, moving the joints it moves correctrly that the screen says, but when i try to move on world mode, on x it mad kind of well but made like a reallly big circule, but on y made a small circule that not move on the right axis, and i have to but on these order X Y Z C , i have to use the C axis to the rotatory becuase if i use the A it dont move and start to do more strange things.

can somebody help or have any idea about that issue i am using the last linuxcnc and the scarakins, now im trying to do an personal scara kinematics but i have some library errors.

Hi all.

As I write this I'm suddenly uncertain whether it counts as a poor use of AI; in any case, I asked the chatGPT 4o for a mod and the result appears to work. I wanted better file search abilities since lcnc's default behaviour means it takes a lot of clicks and scrolling for me to find the files I want to run - particularly 'last modified' sorting.

Do sudo apt-get install zenity,

Follow BigJohnT's instructions regarding bigfileopen.tcl

Then use the attached as your bigfileopen.tcl (copy it in to your config folder and change the extension)

This calls the zenity app on using file Open within Axis. It should default to the Desktop the first time, then to the last folder used. Hope it's some use.


Andy

 

I just tried to create a config in pncconf for a 7i97t and I encountered an error.
Attached is a pic of the error.
I am a novice so I may be doing something wrong, I am barely sure I updated to 2.10.
 

I played with 1704 on my servos and you have to have every single fixed pdo matching in your xml. if you accidentally have an extra one, or one less, or a wrong one that's not in the fixed pdo, it wont work.

Looks like there is more support for Mesa than I was aware of.
linuxcnc.org/docs/2.9/html/drivers/mesa_...us.html#_quick_start

But it still looks more complicated than using USB.

Using the USB dongle is much simpler and uses supported drivers that are included with Linuxcnc.

Using the Mesa board for controlling an RS485 device is more involved. Someone please correct me if I'm wrong, but I thought that you would be required to a custom firmware that would then need a custom modified Linux driver that supports your specific RS485 device (each device implements Modbus control differently.) There is very little if any documented support for this using Mesa. I've only read a few threads where people were wanting to try this, but I don't think I've seen any posts declaring success, let alone instructions.

If those are AI suggestions, they are pure nonsense...

To reduce network latency:

1. Make sure basic host latency setup is done (disable power management etc)

2. If you have an intel MAC on the host PC, disable IRQ coalescing.

3. Use isolcpus to run LinuxCNC on the last CPU

4.  (in conjunction with #3) Pin the Ethernet IRQ to the last CPU
(and set irqbalance to one-shot mode so it doesn't mess with the IRQ pinning)

To check maximum network latency:

sudo chrt 99 ping -i .001 -q -c 60000 10.10.10.10

( Assuming 10.10.10.10 is the 7I76E IP address ) 

This will run for 1 minute and print statistics

 

Thank you Erick, i am not sure but i think it was the LB version, but if possible wait till i confirm that as i am not near it nor is the person that uses it.
Thank you very much for the offer.

Mesa nutzt die Smart Serial, die pins wird automatich gemacht, mus nur im hal diese pins mit anderen pins werknupfen.
Ich denke es gibt etwas im PncConf uber das, aber kein firmware wechsel ist notig.

I may be able to help if you can tell me which control(s) are on it. 160i could be L, P, LA, PA, LB, PB. I think those were all the versions of the 160i that would be on such a machine.