not getting the signals to the pins
- TheProcessTechnician
- Offline
- New Member
Less
More
- Posts: 8
- Thank you received: 0
10 Oct 2024 15:01 - 10 Oct 2024 15:02 #311737
by TheProcessTechnician
not getting the signals to the pins was created by TheProcessTechnician
Hi there!
Total newbie here. I cant get the LinuxCNC signals to the Pins, I am getting following error:
Linux parallel port 0 not found
hal_parport: rtapi_app_main: No such file or directory (-2)
if I am trying to set up the pins in the terminal following happens:
halcmd: loadrt hal_gpio outputs=GPIO13,GPIO19
Note: Using POSIX realtime
The GPIO line GPIO13 can not be found
hal_gpio: rtapi_app_main: Operation not permitted (-1)
<stdin>:6: waitpid failed /usr/bin/rtapi_app hal_gpio
<stdin>:6: /usr/bin/rtapi_app exited without becoming ready
<stdin>:6: insmod for hal_gpio failed, returned -1
What am I doing wrong?
Setup:
Raspi5
LinuxCNC 2.9.1
Milling machine BADOG Cubique
Driver: Badog CNC MikroNC
me (Noob, LinuxCNC beginner)
configuration with Stepconfwizard
GPIO Pins are directly connected to the Driver (should work according to BADOG)
Changes in the .hal file:
#net estop-out => parport.0.pin-01-out
net xdir => hal_pi_gpio.pin-13-out
net xstep => hal_pi_gpio.pin-19-out
setp hal_pi_gpio.pin-19-out-reset 1
net ydir => hal_pi_gpio.pin-05-out
net ystep => hal_pi_gpio.pin-06-out
setp parport.0.pin-05-out-reset 1
net zdir => hal_pi_gpio.pin-27-out
net zstep => hal_pi_gpio.pin-22-out
setp hal_pi_gpio.pin-22-out-out-reset 1
net adir => hal_pi_gpio.pin-04-out
net astep => hal_pi_gpio.pin-17-out
setp hal_pi_gpio.pin-17-out -reset 1
#net spindle-cw => parport.0.pin-14-out
#net spindle-pwm => parport.0.pin-16-out
#net xenable => parport.0.pin-17-out
Report file attached.
Total newbie here. I cant get the LinuxCNC signals to the Pins, I am getting following error:
Linux parallel port 0 not found
hal_parport: rtapi_app_main: No such file or directory (-2)
if I am trying to set up the pins in the terminal following happens:
halcmd: loadrt hal_gpio outputs=GPIO13,GPIO19
Note: Using POSIX realtime
The GPIO line GPIO13 can not be found
hal_gpio: rtapi_app_main: Operation not permitted (-1)
<stdin>:6: waitpid failed /usr/bin/rtapi_app hal_gpio
<stdin>:6: /usr/bin/rtapi_app exited without becoming ready
<stdin>:6: insmod for hal_gpio failed, returned -1
What am I doing wrong?
Setup:
Raspi5
LinuxCNC 2.9.1
Milling machine BADOG Cubique
Driver: Badog CNC MikroNC
me (Noob, LinuxCNC beginner)
configuration with Stepconfwizard
GPIO Pins are directly connected to the Driver (should work according to BADOG)
Changes in the .hal file:
#net estop-out => parport.0.pin-01-out
net xdir => hal_pi_gpio.pin-13-out
net xstep => hal_pi_gpio.pin-19-out
setp hal_pi_gpio.pin-19-out-reset 1
net ydir => hal_pi_gpio.pin-05-out
net ystep => hal_pi_gpio.pin-06-out
setp parport.0.pin-05-out-reset 1
net zdir => hal_pi_gpio.pin-27-out
net zstep => hal_pi_gpio.pin-22-out
setp hal_pi_gpio.pin-22-out-out-reset 1
net adir => hal_pi_gpio.pin-04-out
net astep => hal_pi_gpio.pin-17-out
setp hal_pi_gpio.pin-17-out -reset 1
#net spindle-cw => parport.0.pin-14-out
#net spindle-pwm => parport.0.pin-16-out
#net xenable => parport.0.pin-17-out
Report file attached.
Last edit: 10 Oct 2024 15:02 by TheProcessTechnician.
Please Log in or Create an account to join the conversation.
- tommylight
- Away
- Moderator
Less
More
- Posts: 19422
- Thank you received: 6516
10 Oct 2024 15:09 #311738
by tommylight
Replied by tommylight on topic not getting the signals to the pins
WTH?
Is that a PC or RPI?
hal_parport = does not work on RPI, it is for PC with parallel port
hal_gpio = does not work on PC, it is for RPI pins
Is that a PC or RPI?
hal_parport = does not work on RPI, it is for PC with parallel port
hal_gpio = does not work on PC, it is for RPI pins
Please Log in or Create an account to join the conversation.
- TheProcessTechnician
- Offline
- New Member
Less
More
- Posts: 8
- Thank you received: 0
10 Oct 2024 15:19 #311740
by TheProcessTechnician
Replied by TheProcessTechnician on topic not getting the signals to the pins
Its a RPI, as stated in the setup.
I dont need the spindle or the estop, so i didnt change them and commented them out.
I dont need the spindle or the estop, so i didnt change them and commented them out.
Please Log in or Create an account to join the conversation.
- TheProcessTechnician
- Offline
- New Member
Less
More
- Posts: 8
- Thank you received: 0
10 Oct 2024 15:27 #311743
by TheProcessTechnician
Replied by TheProcessTechnician on topic not getting the signals to the pins
OMG, I am stupid, half of the .hal file is still filled with hal_parport commands... can i just replace hal_parport with hal_gpio?
but it still doesnt solve the problem of the try in the terminal.
but it still doesnt solve the problem of the try in the terminal.
Please Log in or Create an account to join the conversation.
- tommylight
- Away
- Moderator
Less
More
- Posts: 19422
- Thank you received: 6516
10 Oct 2024 15:29 #311744
by tommylight
Replied by tommylight on topic not getting the signals to the pins
OK, remove hal_parport from the hal file, although that might not fix your issues as hal_gpio errors out with permission denied, and there i can not help as i do not use RPI.
The following user(s) said Thank You: TheProcessTechnician
Please Log in or Create an account to join the conversation.
- TheProcessTechnician
- Offline
- New Member
Less
More
- Posts: 8
- Thank you received: 0
10 Oct 2024 16:30 #311751
by TheProcessTechnician
Replied by TheProcessTechnician on topic not getting the signals to the pins
thank you sir, I solved the hal_parport problem, but i still got the permission denied. tried to add user to the group with adduser and gpasswd, sadly no result. anybody got a solution to the problem? error output:
Note: Using POSIX realtime
The GPIO line GPIO4 can not be found
hal_gpio: rtapi_app_main: Operation not permitted (-1)
Note: Using POSIX realtime
The GPIO line GPIO4 can not be found
hal_gpio: rtapi_app_main: Operation not permitted (-1)
Please Log in or Create an account to join the conversation.
Time to create page: 0.095 seconds