Advanced Search

Where the network symbol is in the top right, click on that and that opens the network manager. Can't remember whether Rod left this off to reduce image size, so it may not be there. I was assisting Rod when he was putting the image together and I was including a "little bit extra" in the images I was putting together, so that's why the old memory maybe a bit hazy.

I there any reason you have a /8 mask (16,777,216 hosts from memory this is a publcily routable network, it's be a while since my networking course) rather than a /24 mask (256 hosts which is reserved for private\home networks ) and there is no need for a gateway as there are no other devices on that network subnet. Who recommended these values ?

Since there is no clause for x86 (whatever the 32 bit define is) so ret never gets defined in the scope of the function.

It's bit of a moot point really, since googling that card turns up with the serial port components unpopulated. Most of these chips can be configured via hardware (on board links) to operate as either serial or parallel ports. One of the AX chips also has an SPI interface that can be enabled. But a lot of this is dependant on the schematic & PCB being designed for such.

From the source I could find matching that card, it seems there is a patch for the kernels parport driver, but that only adds the PCI id to the kernel source. Those sources in the package were for 2.6 & 2.4 kernels. The OP may have a different archive, but I think even Wheezy was on a 3.x kernel.

The OP is using a sherline machine and the files sherline provides is for Lcnc 2.6, on another thread I did suggest Wheezy might be the go. I did suggest that Bookworm might be the better option, until I went and checked if it was the same user. In my second post I did apologise taht I didn't realise it was the same user with the sherline machine. It may have been easier if it was kept all in the one thread.
Since there has been no response it's difficult to take this thread further.
Even if the driver parport module was needed to loaded and a PCI id isn't matching for that device the kernel can be forced to load a driver via some udev magic.

There's some info here, just for interest:
unix.stackexchange.com/questions/67936/a...bedded/165845#165845

udev is pretty good, you can use it to mount USB drives by matching serial# or whatever automagically to a particular folder.

The code is already here: forum.linuxcnc.org/24-hal-components/364...trol?start=20#151315

That version has the print lines commented out, they were used only to debug while developing.

HI guys, been away from this for a while but need to build a control box for another user.
Whats the best  way to keep up to date today for a non tech savvy user?
1. Sebs Buildbot and master buildbot2.highlab.com/
2. 2.92 ISO on downloads linuxcnc.org/downloads/
3. Andy's Debian Script in the 2.9 Getting LInuxcnc docs? 
linuxcnc.org/docs/stable/html/getting-st...th_preempt_rt_kernel

Thanks in advance I spent years running on master but the last year or so itts been purely BBookworm 2.9.x for me,
 

It might be my ignorance, doesn't this line define 'ret'?

#if defined(__x86_64__) || defined(__amd64__)
int ret = 0,size=8,mem_size=4096;

To me it looked like that when they added support for aarch64 they added the if x86_64. In this driver for example you don't see the if x86_86 before that line.
forum.ubuntu-fr.org/viewtopic.php?id=1993441

Otherwise wouldn't installing Debian Bookworm be an option with the rtai kernel, modules and headers from:
www.linuxcnc.org/dists/bookworm/base/binary-amd64/

Using the official download image without any modifications.

I cannot find Network Manager on this release.

Used Terminal to launch "menu-config".
Get a dialog box with options to edit entries.
All wifi channels deactivated.
Only one one wired channel activated and edited per:
- Device: eth0 ( ::::: ) as reported by "ip a",
- IPv4 config: Auto,
- Address: 10.10.10.11/8,
- Gateway" 10.10.10.1,
- IPv6: Ignore,
- Automatically connect: [x],
- Available all users: [x].

All workshop equipment and ancillaries de-energized.
Steppers powered off.
VFD in adjacent cubicle powered on, but not operating spindle.
Operation as reported earlier with lost packets.

John.

ret will only be defined for the arm platforms in the next stanza.
The thing is neither of the the #if statements are being acted on. There's no define for a 32 bit platform.

What happens when you remove these lines in that file?
#if defined(__x86_64__) || defined(__amd64__)

And the "    #endif" after that

thankyou tommy, that makes sense now, so my "net probe-input motion.probe-input <= parport.0.pin-15-in" is getting a signal from pin 15 on my paralell breakout board, so those signal names are connected to components in my HAL.files, if i get it right? when i was putting that line into my machine.hal and setting up easyprobe, i kept getting errors, with help from aceira and you just explaining that, i shortened that line to "net motion.probe-input <= parport.0.pin-15-in" and pow, it works, the only reason i was using that line was because i read a forum post, that said that that pin in software controls all probing routines, it worked fine with my toolsetter but when trying this out easyprobe 2 it came up with errors that flagged that comment, without your help id have not been able to get it running, thankyou guys so much, tommy, aciera, talla, tillman, and julian, great work on the add on, and thanks for taking the time to help me guys i really appreciate it, i just have one problem left to solve, as my toolsetter uses an m6 remap which causes the spindle to do a manual toolchange subroutine, insert tool, move to toolsetter coordinates, and probe Z tool height, how would i stop this happening when i want to use the touch probe? the subroutines are in my macros folder and any m6 command causes the toolchange routine as i explained, is there a way to do this? i thought of making seperate macros folders for the toolchange macros and the probing macros, but the m6 would still cause a toolchange subroutine, and the toolsetter is quite tall so i cant just let the routine run without the toolsetter in place as it would break my touch probe,and if i let it run and move the toolsetter it would fail to touch the wasteboard before reaching the max Z travel i specified in the m6 subroutine if the probe isnt triggered, any ideas? ps when i get the last part sorted out i will write a tutorial and or make a video on how to get this set up if you already have a postgui.hal file, as already having certain files made the whole install tricky but again with every mountain to climb ive learned some very useful stuff, which i could probably pass on or help another newbie to linuxcnc to get this up and running
 

Ok that makes sense, so if that is just a comment where in the code does the pin number for the 7i84 get assigned? Is this just a set of lines in one of the .hal files?
Short of me copying the pinout exactly I'm assuming that I will need to change this to suit my wiring.

What error do you get after omitting the dpll line?
The attached report contains the dpll error.

Think of hal file as a distribution box full of wires, the "net" command is literally "connect this pin to that pin"
Usually the firts name after net is whatever you want to call a signal (think of it as a buss bar) and other pins can be wired to it and can be used over and over throughout the hal file as needed.
Other names must be existing LinuxCNC pins.

First line is missing
hm2_

hahaha

My mini lathe has a 6HP three phase motor on it because I had it on hand... so I know the feeling well

FA1045-NP/C/T is a good choice  this one