[Machinekit] Re: Pru Driver conflict with gpio

2020-03-03 Thread Sergio Alejandro Salinas
This especific problem is now *solved*. Thank you for your support jgnoss! In fact, our files were pretty similar, but I noticed something trying your example example: $ /usr/bin/config-pin -q P9.23 P9_23 Mode: default Direction: in Value: 0 $ /usr/bin/config-pin P9.23 out $ /usr/bin/config-pin -

[Machinekit] Re: Pru Driver conflict with gpio

2020-02-22 Thread jgnoss
>Does anyone using kernel 4.19? Yes, I do. I'm not sure if all that slots and bone_capemgr thing still applies or need to be touched. I remember that I've had some issues finding that stuff running the 4.19 kernel. currently I'm running Linux beaglebone 4.19.82-bone-rt-r41 #1stretch PREEMPT R

[Machinekit] Re: Pru Driver conflict with gpio

2020-02-21 Thread Sergio Alejandro Salinas
Thanks jgnoss, it is true it is important. ~$ ls machinekit/configs/ARM.BeagleBone.CRAMPS/ 3D.postgui.hal autosave.halscope CRAMPS.bbio CRAMPS.ini pru-stepper.var README setup.sh ShuttleXpress. postgui.hal 3D.Temps.panel.xml CRAMPS2.halCRAMPS.ha

[Machinekit] Re: Pru Driver conflict with gpio

2020-02-19 Thread jgnoss
... and you didn't tell us what files at what location you are editing. you should have all related files in one folder, cd to that folder edit them according to your configuration supposed you didn't change the file names you then call machinekit CRAMPS.ini ju -- website: http://www.machin

[Machinekit] Re: Pru Driver conflict with gpio

2020-02-19 Thread Sergio Alejandro Salinas
Thanks for your response jgnoss. For now I am ignoring the Z axis. It is true I forgot to attach the .bbio file. -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Gro

[Machinekit] Re: Pru Driver conflict with gpio

2020-02-19 Thread jgnoss
You forgot to attach the .bbio file and you didn't mention what files you are editing There is no magic copying of files going on behind the scenes. all files used should be located in the same directory and be referred as ./filename or with absolute path step 1 configure the Pins as input outp