that's everything it needs, hope you can pick something from that example
ju
On Friday, February 21, 2020 at 6:10:23 PM UTC-5, Sergio Alejandro Salinas
wrote:
>
> Thanks jgnoss, it is true it is important.
>
> ~$ ls machinekit/configs/ARM.BeagleBone.CRAMPS/
... 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
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
Thanks for detailed explanation.
I had a look at the code before, got kind of lost, so I decided to post
here.
Now it makes more sense too.
So I may also go back and further investigate that glitchy PWM signal I got
from the hal_pru_generic pwmgen.
about the thread period1=*10*
I know it's
Damien you are my hero.
Yes, that did the trick. Still necessary a bit of fine tuning but it goes
in the direction I want.
And with your description of the proper way, I'll be there in no time.
I was wondering what that minvel parameter is for, but now it makes a lot
of sense.
thanks a lot,
J
I observed some strange behavior on the hal_arm335xQEP component.
If I boot the bbb the hal_arm335xQEP won't load.
I do config-pin by cli as well as loading the components in halrun by hand
cat ./epconfig.sh
#!/bin/bash
/usr/bin/config-pin P9.27 qep
/usr/bin/config-pin P9.91 qep
/usr/bin/config
