Re: [Machinekit] Re: testing machine-client & anddemo

2019-04-09 Thread Charles Steinkuehler 

This is a fairly common problem with lots of potential causes:

https://superuser.com/questions/730288/why-do-some-wifi-routers-block-multicast-packets-going-from-wired-to-wireless

On 4/7/2019 11:28 AM, c...@tuta.io wrote:

Hi,
great to hear it's working. Sorry, I didn't realize the dns-sd program and
command is part of the Apple Bonjour package which I installed on my
computer in the past, so I presumed it is part of Windows10 like SSH client.

It's little odd to hear that connecting directly by Ethernet cable to your
router solved the issue, that looks like your router created two
subnetworks, for wired and wireless networking. Given how many printers use
this technology and nowadays have both wi-fi and RJ-45 connection, I would
think that it would cause problems.

C.

Dne čtvrtek 4. dubna 2019 23:30:53 UTC+2 Jeff Pollard napsal(a):


Hi,

   Thanks for responding.  I don't have dns-sd, but googled it, and started
reading a bit.  While reading, I realized my Windows10 PC was connected to
the LAN with wifi.  I directly connected the PC to the router with an
Ethernet cable and it (anddemo from the BBB to the WIn10 PC) started to
work.  If I unplug the cable it won't work properly.  So that looks like
the problem - hopefully :-)

   Now I can try to proceed with Cetus again.

Thanks again,

Jeff

On Thursday, April 4, 2019 at 12:14:52 PM UTC-7, ce...@tuta.io wrote:


Hi,
I don't know the exact image, so maybe my advice is not accurate. But on
normal minimal Debian ISO, there is no avahi-daemon package installed.
Machinekit does not care because it has it's libavahi-dev (or something
like this), no error is thrown but services are not broadcasted to local
network.

On Windows 10 computer try running dns-sd -B _machinekit._tcp in command
line and see if it can find anything.

C.

Dne čtvrtek 4. dubna 2019 0:15:53 UTC+2 Jeff Pollard napsal(a):



Hi,

   I am trying to get machine-client to run with Cetus, but with no luck,
so I've backed up to trying with anddemo.
   Also no luck.
   I'm using: bone-debian-8.11-machinekit-armhf-2019-04-01-4gb.img.xz on
a BBB
   After downloading that to uSD I follow up with

  sudo apt-get update
  sudo apt-get upgrade

   then

  sudo nano /etc/linuxcnc/machinekit.ini

   to set REMOTE=1
   Next I downloaded the anddemo files and then run:
   ./run.py
   From that I get:

starting realtime...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
done
loading anddemo.py... done
starting mklauncher... done
starting configserver... done
-
   I then try machinekit-client (both 32 and 64 bit windows versions) on
my Windows PC on the network.
   but it can't find the BBB client in either unicast or multicast
   I can however ssh in to the BBB from Windows running putty, so the BBB
is visible to Windows on the network.

   Any suggestions on how to get the communications link working properly?

Thanks,

Jeff










--
Charles Steinkuehler
char...@steinkuehler.net

--
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] BBB - No "bone_capemgr.*/slots" files/directory found

2019-04-09 Thread Sardar Vayghannezgad 
Hi everyone.
On my laptop, I, as a beginner, am using BBB connected to Windows, with the 
following specs
Static hostname: beaglebone
 Icon name: computer
Machine ID: 8b5a86912858117221dc298b5c72a450
   Boot ID: 38e5bb9f7df54135ada2dd3fefd3ef14
  Operating System: Debian GNU/Linux 9 (stretch)
Kernel: Linux 4.4.155-ti-rt-r153
  Architecture: arm

Starting machinekit on element 14 BBB fails giving the error below:
MACHINEKIT - 0.1
Machine configuration directory is 
'/home/machinekit/machinekit/configs/ARM.BeagleBone.PocketNC'
Machine configuration file is 'PocketNC.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
*grep: /sys/devices/bone_capemgr.*/slots: No such file or directory*
*Loading PocketNCdriver overlay*
*bash: /sys/devices/bone_capemgr.*/slots: No such file or directory*
*Error loading device tree overlay file: PocketNCdriver*
*PocketNC.hal:10: program 
'/home/machinekit/machinekit/configs/ARM.BeagleBone.PocketNC/setup.bridge.sh' 
failed, returned 1*
Shutting down and cleaning up Machinekit...
Cleanup done
Machinekit terminated with an error.  For simple cases more information
can be found in the following files:
/home/machinekit/linuxcnc_debug.txt
/home/machinekit/linuxcnc_print.txt

For other cases get more meaningfull information by restarting after
export DEBUG=5

and look at the output of:
/var/log/linuxcnc.log
dmesg

When looking for errors, specifically look for libraries that fail to load
by looking for lines with 'insmod failed' as per example below.

insmod failed, returned -1:
do_load_cmd: dlopen: nonexistant-component.so: cannot open shared object 
file:
No such file or directory

For getting help, please have a look here: 
www.machinekit.io/docs/getting-help/

To solve this, I have implemented instructions here 
and 
checked all but all there 
, but couldn't 
come up with anything.

Just in case it is useful, inside my *PocketNCdriver-00A0.dts* file seems 
like:
/dts-v1/;
/plugin/;

/ {
compatible = "ti,beaglebone", "ti,beaglebone-black";

/* identification */
//  part-number = "BB-LCNC-BEBOPRBR";
part-number = "PocketNCdriver";
version = "00A0";

/* state the resources this cape uses */
exclusive-use =
/* the pin header uses */
"P8.7", /* gpio2.2  Enablen */
"P8.8", /* gpio2.3  X_Min   */
"P8.9", /* gpio2.5  X_Max   */
"P8.10",/* gpio2.4  Y_Min   */
"P8.11",/* gpio1.13 X_Dir   */
"P8.12",/* gpio1.12 X_Step  */
"P8.13",/* gpio0.23 PWM0*/
"P8.14",/* gpio0.26 Y_Max   */
"P8.15",/* gpio1.15 Y_Dir   */
"P8.16",/* gpio1.14 Y_Step  */
"P8.17",/* gpio0.27 Z_Min   */
"P8.18",/* gpio2.01 Z_Max   */
"P8.19",/* gpio0.22 B Index */
"P8.26",/* gpio1.29 M.Power */
"P9.11",/* gpio0.30 SpndDir */
"P9.12",/* gpio1.28 SpndIdx */
"P9.14",/* gpio1.18 PWM2*/
"P9.15",/* gpio1.16 Z_Step  */
"P9.16",/* gpio1.19 A_Home  */
"P9.17",/* gpio0.05 B_Dir   */
"P9.18",/* gpio0.04 B_Step  */
"P9.21",/* gpio0.03 A_Dir   */
"P9.22",/* gpio0.02 A_Step  */
"P9.23",/* gpio1.17 Z_Dir   */
"P9.24",/* gpio0.15 Spindle */
"P9.13",/* gpio0.31 A_Min   */
"P9.26",/* gpio0.14 Mtr_Ena */
"P8.22",/* gpio1.05 SpndAtS */
//  "P9.33",/* AIN4 Therm0  */
//  "P9.35",/* AIN6 Therm2  */
//  "P9.36",/* AIN5 Therm1  */

/* the hardware IP uses */
/* The following 4 pins conflict with the on-board mmc flash */
"gpio2_2",
"gpio2_3",
"gpio2_5",
"gpio2_4",
"gpio1_13",
"gpio1_12",
"gpio0_23",
"gpio0_26",
"gpio1_15",
"gpio1_14",
"gpio0_27",
"gpio2_1",
"gpio0_22",
"gpio1_29",