Re: [Machinekit] Re: BiggleBone Red from element 14 and Machinekit with furaday cape

2018-02-18 Thread Charles Steinkuehler
Here's where it starts loading the hal_bb_gpio module: > Feb 18 12:20:36 beaglebone rtapi:0: 4:rtapi_app:17438:user hal_bb_gpio.so > default iparms: '' > Feb 18 12:20:36 beaglebone rtapi:0: 4:rtapi_app:17438:user halg_xinitfv:90 > HAL: initializing component 'hal_bb_gpio' type=1 arg1=0 ar > g2=

Re: [Machinekit] Re: BiggleBone Red from element 14 and Machinekit with furaday cape

2018-02-18 Thread 'schoone...@btinternet.com' via Machinekit
Hopefully with this info, someone who knows about the BBB will be able to see what is likely happening A SWAG from me would be that the correct device tree file is not being used, but what do I know ;-) On 18/02/18 12:25, Marius Alksnys wrote:

Re: [Machinekit] Re: BiggleBone Red from element 14 and Machinekit with furaday cape

2018-02-18 Thread Marius Alksnys
machinekit@beaglebone:~/CRAMPS$ DEBUG=5 realtime status /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_GB.utf8) msgd:0 stopped rtapi:0 stopped machinekit@beaglebone:~/CRAMPS$ DEBUG=5 realtime restart /bin/bash: warning: setlocale: LC_ALL: ca

Re: [Machinekit] Re: BiggleBone Red from element 14 and Machinekit with furaday cape

2018-02-18 Thread 'schoone...@btinternet.com' via Machinekit
On 18/02/18 12:01, Marius Alksnys wrote: Line 28: loadrt hal_bb_gpio output_pins=816,822,823,824,825,826,914,923,925 input_pins=807,808,809,810,817,911,913 I know nothing about BBB specifically

Re: [Machinekit] Re: BiggleBone Red from element 14 and Machinekit with furaday cape

2018-02-18 Thread Marius Alksnys
Ok, another halrun test after trying to run that CRAMPS config: machinekit@beaglebone:~/CRAMPS$ halrun /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_GB.utf8) /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_GB.utf8) msgd:0 stopped rtapi:0 stopped /bin/bash: w

Re: [Machinekit] Re: BiggleBone Red from element 14 and Machinekit with furaday cape

2018-02-18 Thread Marius Alksnys
Line 28: loadrt hal_bb_gpio output_pins=816,822,823,824,825,826,914,923,925 input_pins=807,808,809,810,817,911,913 2018 m. vasaris 18 d., sekmadienis 13:56:18 UTC+2, Schooner rašė: > > > On 18/02/18 11:37, Marius Alksnys wrote: > > > > CRAMPS.hal:28: insmod failed, returned -1: > > Whatever yo

Re: [Machinekit] Re: BiggleBone Red from element 14 and Machinekit with furaday cape

2018-02-18 Thread 'schoone...@btinternet.com' via Machinekit
On 18/02/18 11:37, Marius Alksnys wrote: CRAMPS.hal:28: insmod failed, returned -1: Whatever you are trying to load at line 28 of your hal file is what is producing the error That dangling 'DEALER' socket error sometimes shows up even in BB Black. Don't worry about that. Since we swit

Re: [Machinekit] Re: BiggleBone Red from element 14 and Machinekit with furaday cape

2018-02-18 Thread Marius Alksnys
I tried to run different stretch images and configs on BB Red - no success. They were working for me on BB Green and Black. Last test is made with ready image from here: https://machinekoder.com/machinekit-debian-stretch-beaglebone-black/ (If you eager to start without following the steps (altho

Re: [Machinekit] Re: BiggleBone Red from element 14 and Machinekit with furaday cape

2018-02-04 Thread Aurelien
Strange yes, if Marius send me news about this i reply here Damaged hardwar is possible ?. -- 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 Groups "Machinekit" grou

Re: [Machinekit] Re: BiggleBone Red from element 14 and Machinekit with furaday cape

2018-02-04 Thread Frederic RIBLE
Good news! But strange, because on my side I have swap a black by a red without hassle. Need to double check with another red I have in stock. Frederic. On 2018-02-03 23:10, Moi Toi wrote: Hi I have replaced the red fro a "standard" BBB by IGH and now start fine. Ps : i have send the old red t