[Machinekit] Re: RPI gipo help

2018-08-08 Thread Daren Schwenke
Curious, what kind of step rates can you reliably get out of this on the Pi?

On Sunday, June 17, 2018 at 12:06:02 PM UTC-4, Timothy March wrote:
>
> Having trouble getting gipo's to work can get all to show up as outputs 
> but when I load comp no pins are available output or input. The following 
> is my work sheet for what I am trying to achieve
>
> BOBSIGNAL GIPOIN or OUT   RPI PINBINARY
>
> P2 =XPUL= GIPO2  =   OUT  =   3=1
> P3 =XDIR = GIPO3  =   OUT  =   5=1
> P4 =YPUL= GIPO4  =   OUT  =   7=1
> P5 =YDIR = GIPO5  =   OUT  =  29   =1
> P6 =UPUL= GIPO6  =   OUT  =  31   =1
> P7 =UDIR = GIPO7  =   OUT  =  26=1
> P8 =VPUL= GIP08  =   OUT   =  24=1
> P9 =VDIR= GIPO9  =   OUT   =  21=1
> P10=   ESTOP = GIPO10 =   IN =  19=0
> P11=X AXIS LIMIT= GIPO11 =   IN=  23=0
> P12=Y AXIS LIMIT= GIPO12 =   IN=  32=0
> P13=U AXIS LIMIT= GIPO13 =   IN=  33=0
> P14=ENABLE= GIPO14 = OUT  =   8=1
> P15=V AXIS LIMIT= GIPO15 =   IN=  10=0
> P16=BPUL= GIPO16 =OUT=  36=1
> P17=  BDIR/RELAY= GIPO17 =OUT   =  11=1
> P1 =PWM  = GIPO18 =OUT   =  12=1
> GND=   PC GROUND=   ~  =~=   9=~
> PCGND= PC GROUND=   ~=~   =  14=~
> PC5V=  PC 5 VOLT=   ~=~=   2=~
> PC5V=  PC 5 VOLT=   ~   =~ =   4=~
> --
> loadrt hal_gpio dir=0x??
> 1 means output
> 0 means input
>
> you can exclude pins that you will not use
>
> loadrt hal_gpio dir=0x exclude=0x???
> 1 means don't use this pin
> 0 means use this pin
>
> or you can directly write binary numbers in loading hal_gpio comp
> 
>
> #rpi2_gpios[] = {2, 3, 4,  5,  6,  7,  8,  9, 10, 11, 12, 13, 14, 15, 16, 
> 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27 };
> #rpi2_pins[] =  {3, 5, 7, 29, 31, 26, 24, 21, 19, 23, 32, 33,  8, 10, 36, 
> 11, 12, 35, 38, 40, 15, 16, 18, 22, 37, 13 };
>
>  dir=0x  1  1  1   1   1   1   1   1   0   0   0   0   1   0   1   
> 1   1   0   0   0   0   0   0   0   0   0  
>  exclude=0  0  0   0   0   0   0   0   0   0   0   0   0   0   0   
> 0   0   1   1   1   1   1   1   1   1   
> 1
> 
> #commandline
> echo 'ibase=2;A;101110' | bc
> 10
> 66858496
>
> echo 'ibase=2;A;01' | bc
> 10
> 511
> --
> #For my BOB
> loadrt hal_gpio dir=0x101110 
> exclude=0x01
> or
> loadrt hal_gpio dir=66858496 exclude=511
>
> --
>
> To get pins to show as all outputs I use:
> loadrt hal_gipo
>
> I am running Raspbian Jessie this is a new install of OS the output for 
> dmesg is as follows
>
> pi@raspberrypi:~ $ machinekit
> MACHINEKIT - 0.1
> Machine configuration directory is '/home/pi/machinekit/configs/my-foam'
> Machine configuration file is 'my-foam.ini'
> Starting Machinekit...
> rtapi_msgd command:  /usr/libexec/linuxcnc/rtapi_msgd --instance=0 
> --rtmsglevel=1 --usrmsglevel=1 --halsize=524288
> rtapi_app command:  /usr/libexec/linuxcnc/rtapi_app_rt-preempt --instance=0
> io started
> halcmd loadusr io started
> standard_pinout.hal:25: Pin 'hal_gpio.pin-03-out' does not exist
> Shutting down and cleaning up Machinekit...
> Cleanup done
> Machinekit terminated with an error.  You can find more information in the 
> log:
> /home/pi/linuxcnc_debug.txt
> and
> /home/pi/linuxcnc_print.txt
> as well as in the output of the shell command 'dmesg' and in the terminal
> pi@raspberrypi:~ $ dmesg
> [0.00] Booting Linux on physical CPU 0x0
> [0.00] Linux version 4.14.43-rt31-rc1-v7+ (pi@raspberrypi) (gcc 
> version 4.9.2 (Raspbian 4.9.2-10+deb8u1)) #1 SMP PREEMPT RT Mon Jun 11 
> 01:27:42 EDT 2018
> [0.00] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), 
> cr=10c5383d
> [0.00] CPU: div instructions available: patching division code
> [0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing 
> instruction cache
> [0.00] OF: fdt: Machine model: Raspberry Pi 3 Model B Rev 1.2
> [0.00] Memory policy: Data cache writealloc
> [0.00] cma: Reserved 8 MiB at 0x3a80
> [0.00] On node 0 totalpages: 241664
> [0.00] free_area_init_node: node 0, pgdat 80c898c0, node_mem_map 
> b9faa000
> [0.00]   Normal zone: 2124 pages used for memmap
> [   

Re: [Machinekit] launching machinekit after build

2018-08-08 Thread 'schoone...@btinternet.com' via Machinekit

  
  
If you are building from sources please read the documentation

http://www.machinekit.io/docs/developing/machinekit-developing/

Sounds like you probably have not set the pathspec, which is covered
in this document.

On 08/08/18 11:43, mngr wrote:


  
Hi,


I have build machinekit from source, now I am trying to
  launch it.


marco@tmarco:~/machinekit$ ./bin/machinekit 
  ./bin/machinekit: line 1: linuxcnc: command not found

I tried to make a simbolic link to tcl/linuxcnc.so in
  /usr/lib/ but nothing changed
I am sure I am simply noob, and don't know the standard
  procedure... can you please help me?


now I don't have a kernel-rt, but I will only do test, does
  this change anything?



mngr

  
  -- 
  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" group.
  To unsubscribe from this group and stop receiving emails from it,
  send an email to machinekit+unsubscr...@googlegroups.com.
  Visit this group at https://groups.google.com/group/machinekit.
  For more options, visit https://groups.google.com/d/optout.


  




-- 
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" group.
To unsubscribe from this group and stop receiving emails from it, send an email to machinekit+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.


[Machinekit] launching machinekit after build

2018-08-08 Thread mngr
Hi,

I have build machinekit from source, now I am trying to launch it.

marco@tmarco:~/machinekit$ ./bin/machinekit 
./bin/machinekit: line 1: linuxcnc: command not found

I tried to make a simbolic link to tcl/linuxcnc.so in /usr/lib/ but nothing 
changed
I am sure I am simply noob, and don't know the standard procedure... can 
you please help me?

now I don't have a kernel-rt, but I will only do test, does this change 
anything?

mngr

-- 
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" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to machinekit+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.


Re: [Machinekit] mklauncher "Can not find -sec DISPLAY -var INTRO_GRAPHIC"

2018-08-08 Thread 'schoone...@btinternet.com' via Machinekit



On 08/08/18 03:43, Cameron McQuinn wrote:

..was able to successfully start the config several months ago, 
but I had to set the project aside for a while. When I returned, I 
upgraded the kernel from 4.9 to 4.14, and upgraded machinekit and 
QtQuickVcp to the latest versions, but didnt' change anything else.


The error in your title is consequential not causal.

The error is here.
I will leave those who know more about it to pinpoint what caused it.  I 
would tend to suspect the kernel change and wonder if the firmware is 
present or correct.

Aug  8 02:01:24 socfpga rtapi:0: 4:rtapi_app:1890:user hm2_soc_ol: 
soc_program_fpga
Aug  8 02:01:24 socfpga rtapi:0: 4:rtapi_app:1890:user hm2_soc_ol: FPGA overlay 
status: applied
Aug  8 02:01:26 socfpga rtapi:0: 1:rtapi_app:1890:user hm2_soc_ol: failed to 
map hm2-socfpga0 to /dev/uioX
Aug  8 02:01:26 socfpga rtapi:0: 1:rtapi_app:1890:user hm2_soc_ol: 
soc_mmap_fail hm2-socfpga0
Aug  8 02:01:26 socfpga rtapi:0: 1:rtapi_app:1890:user hm2/foo: failed to 
program fpga, aborting hm2_register
Aug  8 02:01:26 socfpga rtapi:0: 1:rtapi_app:1890:user foo: hm2_soc_ol_board 
fails HM2 registration
Aug  8 02:01:26 socfpga rtapi:0: 1:rtapi_app:1890:user hm2_soc_ol: error 
registering UIO driver: -22
Aug  8 02:01:26 socfpga rtapi:0: hal_call_usrfunct(newinst,-- 
config="firmware=zynq/dtbo/replicookie_7z020_ol.dtbo num_pwmgens=5 
num_stepgens=5" debug=1 already_programmed=1) failed: -1 - Operation not permitted
Aug  8 02:01:26 socfpga rtapi:0: 1:rtapi_app:1890:user hal_call_usrfunct(newinst,-- 
config="firmware=zynq/dtbo/replicookie_7z020_ol.dtbo num_pwmgens=5 
num_stepgens=5" debug=1 already_programmed=1) failed: -1 - Operation not permitted
Aug  8 02:01:26 socfpga msgd:0: hal_lib:1904:user halg_exit:293 HAL: removing 
component 99 'halcmd1904'


--
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" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to machinekit+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.


[Machinekit] Re: Rpi3, Beagleboard X15, And Avnet Ultra96

2018-08-08 Thread Claudio Lorini
Nice and compact board, but i cannot understand the choice of removing 
wired Ethernet. 
Also missing CAN bus comms, so for 'usual' control applications a 
daughter-board is required 
and the somewhat limited IOs gets plundered even more...

 

-- 
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" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to machinekit+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.