Advanced Search

Have you run the "gpioinfo" command? That will list the available pins. If it doesn't work that may mean that you don't have gpiod installed.

Is your user account a member of the "dialout" group?

forums.raspberrypi.com/viewtopic.php?t=225274

Hi,
I'm a bit desperate. I want to replace my very old pc based linuxcnc with the actual version running on a raspberry pi 5.
I've been trying to get signals to the pin header for a day now.
First of all: Is there a tutorial for raspberry configuration? I found nothing except the general docu and then went from one error message to another.
What I did is:
1. Started Stepconf wizard
2. Replaced parallel port Pins with hal_gpioxxx, see attached hal file
When I start this Setup following error occurs:  

This was my try to set the PINs:
Would be nice if onyone could show my where I'm wrong.

Andy

 

PCW wrote:

It also causes errors even
at a constant spindle speed, as the offset changes with thread
depth over the multiple threading passes 
 

Which LinuxCNC version? Not being able to cut threads would be a huge problem. 

In your constant speed example, is there any possibility that what you are seeing is the "virtual compound angle" Q ?

Can _what_ be run on Linux?

Can you explain what you want to do?

Check and lower the P value in the ini.

Estop fixed, my mistake.
But as soon as i enable, the servos howl like mad, even though i had just tuned them perfectly. Hmmmmmm.

Have you raised an issue on the LinuxCNC github page?

While I've raised a couple issues in the past, I am reluctant to directly engage on GH because I don't speak 'computer' fluently.  I can describe an issue in laymans terms, but as soon as any discussion moves towards code-type testing & solutions I'm lost.  My typical modus operandi is to prompt enough discussion on this forum that somone clever takes up the torch over on GH.

I'll raise one now, thanks for the reminder about it.

EDIT: github.com/LinuxCNC/linuxcnc/issues/3455

I have no working config.
ill figure it out after lunch.

I just came from a fight with e-stop in a new config with qtdragon, and I didn't win. I'm quite sure I don't have the answers.

If you have a working config, one option is to replace the hal file in that one. Idea is that it overall worked before so it should overall work now.
Another way is to start with the simplest axis interface config from linuxcnc examples, replace the sim* hal files with the cia402.hal file.
 

Hi Halas,

There is added a hal param for inertia wich can be set to from 0 up to 1 to run at programmed feed.
This results in less feed fluctiations at corners.

See the param section :  readme.

Also program execution time should be faster. As i reverted the acc max change.

Hehe that was a joke. Although right now the machine is stuck on estop and I'm not sure why. I'm sure it will be something dumb.

I'm new to this and was asking Chat GPT what the problems were with Lichuan drives. It says EtherCat Master stacks on Linux CNC expect drives to follow CiQ 402 correctly, but Lichuan drives lack full state machine compliance, and incorrectly transition from Ready to Switch ON to Operation Enabled, etc. Windows stacks are more tolerant of violations. So by plugging the drive in after they have done an illegal transition, Linux CNC stacks remain happy.

Thanks for waking me up
It's even worse, not only - and _ got mixed up, it should have been:
net tool-change iocontrol.0.tool-change => sauter.0.toolchange
net tool-changed iocontrol.0.tool-changed => sauter.0.toolchanged
net tool-number iocontrol.0.tool-prep-number => sauter.0.newtoolnumber

Now Linuxcnc at least starts ok again. Let's see if I can get the turret move...

Cabinet almost ready for sand blasting and paint. 

So, change made, AC power component is gone and first small test job ran successfully. Hoping for the best . Thank you again!