from:"schoone...@gmail.com"


Thanks, I'll have a look later

On 3/5/2019 7:24 PM, Dennis wrote:
Digging through github history in between 4th and 9th of December 2018 
I found a commit 
(https://github.com/machinekit/machinekit/commit/e207745f52181562d22cacd636bc03721d2c2587) 
that modified the function pci_enable_device in rtapi_pci.c. This is 
the same function that throws the parse error in my linuxcnc.log.


Maybe this is the problem...

Am Dienstag, 5. März 2019 20:13:23 UTC+1 schrieb Dennis:

By geometric search I could narrow down the first 'problematic'
package, I hope this is helpful to you:

the last working version is:
0.1.1543935482

the first non working version is:
0.1.1544363499

Thanks again for your help!

Best regards
Dennis

Am Dienstag, 5. März 2019 18:56:37 UTC+1 schrieb Schooner:

No need for the github issue, we are looking at it!

The commit that was OK was quite old, it would be good to try
and narrow down a bit to where the problem arose.
It will not have been very recently, since those were all ARM
config changes.

If you are happy to do it, I can only suggest picking a
package from a mid-point, say the first one in 2019 and
installing that.
If it fails work back to say mid Dec 2018, if it succeeds work
forward to end of Jan 2019 and so on.

In the absence of specific changes to hm2_pci, I suspect that
another change, of which there were quite a few to
correct warnings etc, must have had an unforeseen effect
elsewhere.

Anything you can do to isolate a commit or series of commits
as causing this, would be very helpful

Tomorrow hopefully I can test on a 5i25/7i76 setup in the
workshop, so having an idea where to look would speed things
greatly

regards


On 05/03/19 17:08, Dennis wrote:

Thanks to you both!

I've done some further testing:

1) Mesa 6i25 in different PCI-E slot --> same result, not working
2) Different Mesa 6i25 from another working linuxcnc PC in
original slot and second slot --> not working
3) Procedure from Schooner (downgrade to last working
version) --> !working!
4) To countercheck I upgraded again to latest version of
machinekit, the one that was not working --> not working

So to me something with the new version of machinekit is now
working with my Mesa 6i25. It is not the card, not the PC and
not the configuration.

Should I file an issue on the github tracker?

Best regards
Dennis


Am Dienstag, 5. März 2019 13:31:57 UTC+1 schrieb Schooner:


On 05/03/19 11:32, Bas de Bruijn wrote:


Not sure how much i can help here.
Further on there’s this section:

:rt halg_xinitfv:90 HAL: initializing component
'hm2_pci' type=1 arg1=0 arg2=0/0x0

Mar  5 11:38:33 labor-linuxcnc-m2 msgd:0:
hal_lib::rt PCI_ID: 2718:5125 2718:5125

Mar  5 11:38:33 labor-linuxcnc-m2 msgd:0:
hal_lib::rt RTAPI_PCI: DeviceID: 2718 5125 2718 5125

Mar  5 11:38:33 labor-linuxcnc-m2 msgd:0:
hal_lib::rt RTAPI_PCI: Calling driver probe function

Mar  5 11:38:33 labor-linuxcnc-m2 msgd:0:
hal_lib::rt RTAPI_PCI: Enabling Device :03:00.0

Mar  5 11:38:33 labor-linuxcnc-m2 msgd:0:
hal_lib::rt Resource 0: 0xf7e0 0xf7e0 

Mar  5 11:38:33 labor-linuxcnc-m2 msgd:0:
hal_lib::rt Failed to parse

"/sys/devices/pci:00/:00:1c.2/:02:00.0/:03:00.0/resource"

Mar  5 11:38:33 labor-linuxcnc-m2 msgd:0:
hal_lib::rt hm2_pci: skipping AnyIO board at
:03:00.0, failed to enable PCI device

Mar  5 11:38:33 labor-linuxcnc-m2 msgd:0:
hal_lib::rt Driver probe function failed!

Mar  5 11:38:33 labor-linuxcnc-m2 msgd:0:
hal_lib::rt hm2_pci: error registering PCI driver

Mar  5 11:38:33 labor-linuxcnc-m2 msgd:0: hal_lib:


Did other things get updates too perhaps?



hm2_pci has not changed for 3 years and I cannot
immediately see any other changes that might affect

First step is to reverse the process

apt remove machinekit*

Then download

http://deb.machinekit.io/debian/pool/main/m/machinekit/machinekit_0.1.1543327459.gite758f69-1~stretch_amd64.deb



http://deb.machinekit.io/debian/pool/main/m/machinekit/machinekit-rt-preempt-dbgsym_0.1.1543327459.gite758f69-1~stretch_amd64.deb

Re: [Machinekit] Mesa 6i25 & 7i76 - Operation not permitted with new Machinekit Version


  
  
No need for the github issue, we are looking at it!

The commit that was OK was quite old, it would be good to try and
narrow down a bit to where the problem arose.
It will not have been very recently, since those were all ARM config
changes.

If you are happy to do it, I can only suggest picking a package from
a mid-point, say the first one in 2019 and installing that.
If it fails work back to say mid Dec 2018, if it succeeds work
forward to end of Jan 2019 and so on.

In the absence of specific changes to hm2_pci, I suspect that
another change, of which there were quite a few to
correct warnings etc, must have had an unforeseen effect elsewhere.

Anything you can do to isolate a commit or series of commits as
causing this, would be very helpful

Tomorrow hopefully I can test on a 5i25/7i76 setup in the workshop,
so having an idea where to look would speed things greatly

regards


On 05/03/19 17:08, Dennis wrote:


  
Thanks to you both!


I've done some further testing:


1) Mesa 6i25 in different PCI-E slot --> same result,
  not working
2) Different Mesa 6i25 from another working linuxcnc PC in
  original slot and second slot --> not working
3) Procedure from Schooner (downgrade to last working
  version) --> !working!
4) To countercheck I upgraded again to latest version of
  machinekit, the one that was not working --> not working


So to me something with the new version of machinekit is
  now working with my Mesa 6i25. It is not the card, not the PC
  and not the configuration.


Should I file an issue on the github tracker?


Best regards
Dennis




Am Dienstag, 5. März 2019 13:31:57 UTC+1 schrieb Schooner:

   
On 05/03/19 11:32, Bas de Bruijn wrote:


  
  


Not sure how much i can help here.
Further on there’s this section:



  :rt halg_xinitfv:90
  HAL: initializing component 'hm2_pci' type=1
  arg1=0 arg2=0/0x0
  Mar  5 11:38:33
  labor-linuxcnc-m2 msgd:0: hal_lib::rt PCI_ID:
  2718:5125 2718:5125
  Mar  5 11:38:33
  labor-linuxcnc-m2 msgd:0: hal_lib::rt
  RTAPI_PCI: DeviceID: 2718 5125 2718 5125
  Mar  5 11:38:33
  labor-linuxcnc-m2 msgd:0: hal_lib::rt
  RTAPI_PCI: Calling driver probe function
  Mar  5 11:38:33
  labor-linuxcnc-m2 msgd:0: hal_lib::rt
  RTAPI_PCI: Enabling Device :03:00.0
  Mar  5 11:38:33
  labor-linuxcnc-m2 msgd:0: hal_lib::rt Resource
  0: 0xf7e0 0xf7e0 
  Mar  5 11:38:33
  labor-linuxcnc-m2 msgd:0: hal_lib::rt Failed
  to parse
  "/sys/devices/pci:00/:00:1c.2/:02:00.0/:03:00.0/resource"
  Mar  5 11:38:33
  labor-linuxcnc-m2 msgd:0: hal_lib::rt hm2_pci:
  skipping AnyIO board at :03:00.0, failed to
  enable PCI device
  Mar  5 11:38:33
  labor-linuxcnc-m2 msgd:0: hal_lib::rt Driver
  probe function failed!
  Mar  5 11:38:33
  labor-linuxcnc-m2 msgd:0: hal_lib::rt hm2_pci:
  error registering PCI driver
  Mar  5 11:38:33
  labor-linuxcnc-m2 msgd:0: hal_lib:



Did other things get updates too perhaps?

  


hm2_pci has not changed for 3 years and I cannot immediately
see any other changes that might affect

First step is to reverse the process

apt remove machinekit*

Then download 
http://deb.machinekit.io/debian/pool/main/m/machinekit/machinekit_0.1.1543327459.gite758f69-1~stretch_amd64.deb
http://deb.machinekit.io/debian/pool/main/m/machinekit/machinekit-rt-preempt-dbgsym_0.1.1543327459.gite758f69-1~stretch_amd64.deb

and install with
dpkg -i machinekit_0.1.1543327459.gite758f69-1~stretch_amd64.deb
machinekit-rt-preempt-dbgsym_0.1.1543327

Re: [Machinekit] Mesa 6i25 & 7i76 - Operation not permitted with new Machinekit Version


  
  

On 05/03/19 11:32, Bas de Bruijn wrote:


  
  
  


Not sure how much i can help here.
Further on there’s this section:



  :rt halg_xinitfv:90 HAL:
  initializing component 'hm2_pci' type=1 arg1=0 arg2=0/0x0
  Mar  5 11:38:33 labor-linuxcnc-m2
  msgd:0: hal_lib::rt PCI_ID: 2718:5125 2718:5125
  Mar  5 11:38:33 labor-linuxcnc-m2
  msgd:0: hal_lib::rt RTAPI_PCI: DeviceID: 2718 5125
  2718 5125
  Mar  5 11:38:33 labor-linuxcnc-m2
  msgd:0: hal_lib::rt RTAPI_PCI: Calling driver probe
  function
  Mar  5 11:38:33 labor-linuxcnc-m2
  msgd:0: hal_lib::rt RTAPI_PCI: Enabling Device
  :03:00.0
  Mar  5 11:38:33 labor-linuxcnc-m2
  msgd:0: hal_lib::rt Resource 0: 0xf7e0 0xf7e0
  
  Mar  5 11:38:33 labor-linuxcnc-m2
  msgd:0: hal_lib::rt Failed to parse
"/sys/devices/pci:00/:00:1c.2/:02:00.0/:03:00.0/resource"
  Mar  5 11:38:33 labor-linuxcnc-m2
  msgd:0: hal_lib::rt hm2_pci: skipping AnyIO board at
  :03:00.0, failed to enable PCI device
  Mar  5 11:38:33 labor-linuxcnc-m2
  msgd:0: hal_lib::rt Driver probe function failed!
  Mar  5 11:38:33 labor-linuxcnc-m2
  msgd:0: hal_lib::rt hm2_pci: error registering PCI
  driver
  Mar  5 11:38:33 labor-linuxcnc-m2
  msgd:0: hal_lib:



Did other things get updates too perhaps?

  


hm2_pci has not changed for 3 years and I cannot immediately see any
other changes that might affect

First step is to reverse the process

apt remove machinekit*

Then download 
http://deb.machinekit.io/debian/pool/main/m/machinekit/machinekit_0.1.1543327459.gite758f69-1~stretch_amd64.deb
http://deb.machinekit.io/debian/pool/main/m/machinekit/machinekit-rt-preempt-dbgsym_0.1.1543327459.gite758f69-1~stretch_amd64.deb

and install with
dpkg -i machinekit_0.1.1543327459.gite758f69-1~stretch_amd64.deb
machinekit-rt-preempt-dbgsym_0.1.1543327459.gite758f69-1~stretch_amd64.deb

from wherever you downloaded them to

Then try again with DEBUG=5 set and attach the linuxcnc.log whatever
the result.
(blank linuxcnc.log first)

On the face of it the error is failing to contact the board, not
failing to load the driver and the error from the driver is
resultant from that.


If you did not have this working immediately before ( the same day)
you updated machinekit, I would check all cabling
and possibly remove the 6i25, clean the slot and board contacts with
methylated spirits or similar, re-seat and try again.




  




-- 
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] Mesa 6i25 & 7i76 - Operation not permitted with new Machinekit Version


  
  
Please read
http://www.machinekit.io/docs/getting-help/

No-one can help you with this amount of information.


On 05/03/19 07:16, destra...@gmail.com
  wrote:


  
Hello dear Machinekit community,
we've successfully implemented a self built 3d printer with
  Machinekit. For stepper signal generation, we use the above
  mentioned cards. Up until yesterday, our config was working
  with the string


  
  rt.loadrt('hm2_pci',
  config='num_encoders=1
  num_stepgens=4 sserial_port_0="00"')

  
  Yesterday I updated via apt-get upgrade to Machinekit version
  0.1.1551530147.git6a143ec-1~stretch and now we get the
  following error on launch:



  
  RuntimeError:
  rtapi_loadrt '('hm2_pci', 'config=num_encoders=1
  num_stepgens=4
  sserial_port_0="00"')'
  failed: Operation not
  permitted

  
  Have you seen this error before?


Best regards
Dennis

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

Re: [Machinekit] Re: Kinematics configuration for a new machine

2019-02-28 Thread schoone...@gmail.com


  
  


  Dne čtvrtek 28. února 2019 1:04:09 UTC+1
bradley.j...@student.uts.edu.au napsal(a):

  Perhaps I should have loaded that and it would
prevent some of the errors generated later in the file.
But the system I am looking to control is a
  stepper-based setup, and I'm not certain if the reference
  to SERVO_PERIOD is directly related to a servo drive, or
  if it is just a concept that applies to both servo and
  stepper based systems.

  

  

SERVO_PERIOD is just a tag, it could be ELEPHANT_PERIOD

Traditionally there was a base_thread and servo_thread
The base_thread ran as fast as the machine was capable of and was
used for things like software step generation which were time
critical.
The servo_thread was used for components that whilst they needed to
be polled regularly, were not so time critical.

The servo_thread at some point probably got the name because it was
fast enough to run servos

Machinekit has dropped software step generation and its reliance
upon rtai kernels to get a low a latency as possible to make it
work.
The recommended stepper generation methods are FPGA card or SOC,  or
the BBB PRU

Therefore there is generally only a servo_thread, but if the INI
file referred to 
ELEPHANT_PERIOD = 100
that would function just as well :)


  




-- 
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] Updated install of machinekit -- new errors

2019-02-28 Thread schoone...@gmail.com


  
  
Now hopefully fixed the problem and new packages in the repo

Purge your old packages, do an apt update and then install again.


On 28/02/19 08:56, schoone...@gmail.com
  wrote:


  
  OK
  
  I have found the problem, an unintended corruption of the package
  name, causing an overwrite in the Packages text and
  linking to the wrong package.
  
  I have pushed a fix, but it needs to be tested, merged and in the
  meanwhile I may need to purge the repo or it will not correct
  
  On 28/02/19 07:30, schoone...@gmail.com
wrote:
  
  

Please say what you are installing on what.
You appear to be trying to install a Jessie package on
  Stretch, because Jessie is the only one with that version
  dependency.
So make sure your sources.list is correct and run apt update
  first

Yes for now, purge your packages and reinstall
I will check later that the packages contain what they
  should.

On 2/28/2019 4:25 AM, Condit Alan
  wrote:


  
  Cern,
  
  
  Thanks, I have only done install or upgrades on
the beaglebone black via “sudo apt-get install machinekit”.
  So, I don’t even know how to get apt to install
those particular versions.
  I am more used to using synaptic on my linux pc.
  
  
  I finally found them with my browser. I wasn’t
looking for the second package.
  
  
  I saw a notice about installing machinekit-hal
and machinekit-cnc, I don’t know whether that has
complicated issues also.
  
  
  I tried install machinekit and got an error
message
  
machinekit@beaglebone:~$ sudo apt-get install machinekit
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may
mean that you have
requested an impossible situation or if you are
using the unstable
distribution that some required packages have
not yet been created
or been moved out of Incoming.
The following information may help to resolve
the situation:


The following packages have unmet dependencies:
 machinekit : Depends: machinekit-rt-threads
              Depends: python-gst0.10 but it is
not installable
E: Unable to correct problems, you have held
broken packages.
  
  

  I tried install machinekit-rt-preempt and got an
  error message
  
  machinekit@beaglebone:~$ sudo apt-get install machinekit-rt-preempt
  Reading package lists... Done
  Building dependency tree       
  Reading state information... Done
  Some packages could not be installed. This
  may mean that you have
  requested an impossible situation or if you
  are using the unstable
  distribution that some required packages have
  not yet been created
  or been moved out of Incoming.
  The following information may help to resolve
  the situation:
  
  
  The following packages have unmet
  dependencies:
   machinekit-rt-preempt : Depends: machinekit
  (= 0.1.1551246384.gitdc0dd15-1~stretch) but
  0.1.1551000781.git82d727d-1~stretch is to be installed
  E: Unable to correct problems, you have held
  broken packages.
  


  So, then I tried install machinekit
  machinekit-rt-preempt
  
  machinekit@beaglebone:~$ sudo apt-get install machinekit
  machinekit-rt-preempt
  Reading package lists... Done
  Building dependency tree       
  Reading state information... Done
  Some packages could not be installed. This
  may mean that you have
  requested an impossible situation or if you
  are using the unstable
  distribution that some required packages have
  not yet been created
  or been moved out of Incoming.
  The following information may help to resolve
  the situation:
  
  
  The following packages have unmet
  dependencies:
   machinekit

Re: [Machinekit] Updated install of machinekit -- new errors

2019-02-28 Thread schoone...@gmail.com


  
  
OK

I have found the problem, an unintended corruption of the package
name, causing an overwrite in the Packages text and
linking to the wrong package.

I have pushed a fix, but it needs to be tested, merged and in the
meanwhile I may need to purge the repo or it will not correct

On 28/02/19 07:30, schoone...@gmail.com
  wrote:


  
  Please say what you are installing on what.
  You appear to be trying to install a Jessie package on Stretch,
because Jessie is the only one with that version dependency.
  So make sure your sources.list is correct and run apt update
first
  
  Yes for now, purge your packages and reinstall
  I will check later that the packages contain what they should.
  
  On 2/28/2019 4:25 AM, Condit Alan
wrote:
  
  

Cern,


Thanks, I have only done install or upgrades on
  the beaglebone black via “sudo apt-get install machinekit”.
So, I don’t even know how to get apt to install
  those particular versions.
I am more used to using synaptic on my linux pc.


I finally found them with my browser. I wasn’t
  looking for the second package.


I saw a notice about installing machinekit-hal and
  machinekit-cnc, I don’t know whether that has complicated
  issues also.


I tried install machinekit and got an error
  message

  machinekit@beaglebone:~$ sudo apt-get install machinekit
  Reading package lists... Done
  Building dependency tree       
  Reading state information... Done
  Some packages could not be installed. This may
  mean that you have
  requested an impossible situation or if you are
  using the unstable
  distribution that some required packages have not
  yet been created
  or been moved out of Incoming.
  The following information may help to resolve the
  situation:
  
  
  The following packages have unmet dependencies:
   machinekit : Depends: machinekit-rt-threads
                Depends: python-gst0.10 but it is
  not installable
  E: Unable to correct problems, you have held
  broken packages.


  
I
tried install machinekit-rt-preempt and got an error message

machinekit@beaglebone:~$ sudo apt-get install machinekit-rt-preempt
Reading package lists...
Done
Building dependency tree 
     
Reading state
information... Done
Some packages could not be
installed. This may mean that you have
requested an impossible
situation or if you are using the unstable
distribution that some
required packages have not yet been created
or been moved out of
Incoming.
The following information
may help to resolve the situation:


The following packages
have unmet dependencies:
 machinekit-rt-preempt :
Depends: machinekit (=
0.1.1551246384.gitdc0dd15-1~stretch) but
0.1.1551000781.git82d727d-1~stretch is to be installed
E: Unable to correct
problems, you have held broken packages.

  
  
So, then I tried install machinekit
machinekit-rt-preempt

machinekit@beaglebone:~$ sudo apt-get install machinekit
machinekit-rt-preempt
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may
mean that you have
requested an impossible situation or if you are
using the unstable
distribution that some required packages have
not yet been created
or been moved out of Incoming.
The following information may help to resolve
the situation:


The following packages have unmet dependencies:
 machinekit : Depends: python-gst0.10 but it is
not installable
 machinekit-rt-preempt : Depends: machinekit (=
0.1.1551246384.gitdc0dd15-1~stretch) but
0.1.1551264903.git0634d7c-1~stretch is to be installed
E: Unable to correct problems, you have held
broken packages.

  
  
Do I need to purge and start over

Re: [Machinekit] Updated install of machinekit -- new errors

2019-02-27 Thread schoone...@gmail.com


Please say what you are installing on what.

You appear to be trying to install a Jessie package on Stretch, because 
Jessie is the only one with that version dependency.


So make sure your sources.list is correct and run apt update first

Yes for now, purge your packages and reinstall

I will check later that the packages contain what they should.

On 2/28/2019 4:25 AM, Condit Alan wrote:

Cern,

Thanks, I have only done install or upgrades on the beaglebone black 
via “sudo apt-get install machinekit”.

So, I don’t even know how to get apt to install those particular versions.
I am more used to using synaptic on my linux pc.

I finally found them with my browser. I wasn’t looking for the second 
package.


I saw a notice about installing machinekit-hal and machinekit-cnc, I 
don’t know whether that has complicated issues also.


I tried install machinekit and got an error message
machinekit@beaglebone:~$ sudo apt-get install machinekit
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 machinekit : Depends: machinekit-rt-threads
            Depends: python-gst0.10 but it is not installable
E: Unable to correct problems, you have held broken packages.

I tried install machinekit-rt-preempt and got an error message
machinekit@beaglebone:~$ sudo apt-get install machinekit-rt-preempt
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 machinekit-rt-preempt : Depends: machinekit (= 
0.1.1551246384.gitdc0dd15-1~stretch) but 
0.1.1551000781.git82d727d-1~stretch is to be installed

E: Unable to correct problems, you have held broken packages.

So, then I tried install machinekit machinekit-rt-preempt
machinekit@beaglebone:~$ sudo apt-get install machinekit 
machinekit-rt-preempt

Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 machinekit : Depends: python-gst0.10 but it is not installable
 machinekit-rt-preempt : Depends: machinekit (= 
0.1.1551246384.gitdc0dd15-1~stretch) but 
0.1.1551264903.git0634d7c-1~stretch is to be installed

E: Unable to correct problems, you have held broken packages.

Do I need to purge and start over?
How do I get apt to show me the files that I need to use?
There used to be a way to download a particular .deb and install it. 
Is that still possible?


Alan


On Feb 27, 2019, at 3:20 PM, c...@tuta.io  wrote:

Should be these:
http://deb.machinekit.io/debian/pool/main/m/machinekit/machinekit-rt-preempt_0.1.1551246384.gitdc0dd15-1~stretch_armhf.deb
http://deb.machinekit.io/debian/pool/main/m/machinekit/machinekit_0.1.1551246384.gitdc0dd15-1~stretch_armhf.deb

Cannot it be browser caching? Can you see them with apt?

C.

Dne čtvrtek 28. února 2019 0:11:09 UTC+1 mugginsac napsal(a):

I was looking for either, but I need the rtpreempt for arm.



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

Re: [Machinekit] Updated install of machinekit -- new errors

2019-02-26 Thread schoone...@gmail.com

Just check the repo to see if there is a new package with the right git 
Sha to match the commit


On 2/26/2019 10:32 PM, Condit Alan wrote:

Bas,

The answer would be yes and no. After I first ran it, and saw the new messages, 
I knew people would want to see it with debugging support in order to help, I 
ran it again after “export DEBUG=5”. In essence the new messages in 
/var/log/linuxcnc.log were identical and there weren’t any errors in the 
earlier stuff in the log. But, it wasn’t until shortly after I posted it that 
the significance hit me and that was when I started searching for where those 
new messages were coming from.

How long after a pull request is moved to master, will a “sudo apt-get install 
machinekit” get the updated files from a build? Or should I set up a cross 
build on my linux pc and build from source?

Alan




On Feb 25, 2019, at 10:18 PM, Bas de Bruijn  wrote:




On 26 Feb 2019, at 06:32, mugginsac  wrote:

Found the culprits. Three more calls to rtapi_print() affected by the change 
from RTAPI_MSG_ERR to RTAPI_MSG_ALL.
But I have seemingly created a bug in my config in the process of cleaning them 
up.
The axis screen appears for a fraction of a second and then disappears.

Did you “export DEBUG=5” before the /var/log/linuxcnc.log?


--
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] Startup error messages in Axis

2019-02-21 Thread schoone...@gmail.com


  
  
They are not errors or warnings, they are telling you what is
happening with the pru.

Make sure your DEBUG= setting in your ini file is 0

The lines are coming from hal_pru_generic.c using rtapi_print() and
would not normally show up without debugging set to something

Either way, if they were errors, they would start 'ERROR:'


On 21/02/19 01:00, mugginsac wrote:


  
I am running Stretch 9.8 (testing) on a BBB with Xylotex
  DB25 cape.
I am getting the following errors or warnings when Axis
  starts up:

prussdrv_init
  prussdrv_open
  prussdrv_pruintc_init
  prussdrv_map_prumem
  PRU data ram mapped
  num_pwmgens : 1
  num_stepgens: 4
  num_encoders: 0
  Init pwm
  hpg_pwm_init
  Init stepgen
  hpg_stepgen_init
  Init encoder



If I clear them then everything seems to run fine. So the
  question is what do they mean and why am I getting them?
Is there anyway to not get them?

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

Re: [Machinekit] How does machinekit test to see if it is running on a rt-preempt kernel?

2019-02-19 Thread schoone...@gmail.com



On 2/20/2019 12:09 AM, Condit Alan wrote:

OK here are the test results:

machinekit@beaglebone:~$ cat /sys/kernel/realtime
1
machinekit@beaglebone:~$ cat /boot/config-4.19.23-bone-rt-r23  | grep 
CONFIG_PREEMPT_RT_FULL=y

CONFIG_PREEMPT_RT_FULL=y
machinekit@beaglebone:~$ uname -a
Linux beaglebone 4.19.23-bone-rt-r23 #1stretch PREEMPT RT Tue Feb 19 
17:12:46 UTC 2019 armv7l GNU/Linux

machinekit@beaglebone:~$

I am getting some errors on the Axis screen but I am running inside 
without a controller attached.
However, that said, it boots with no problem and starts machinekit. So 
I guess the next step is to take the

BBB back out to the shop and try running the machine!

Schooner, you said rtapi.c tests for cat 
/boot/config-4.19.23-bone-rt-r23| grep CONFIG_PREEMPT_RT_FULL=yes but 
that test failed, I looked at the config and saw that 
CONFIG_PREEMPT_RT_FULL was set to “y” not “yes”. Did you really 
mean “yes” or is “y” OK?


I didn't say that, I just asked you to do it because I suspected the 
config was not properly set.


The test in rtapi_compat.c is just for /sys/kernel/realtime which is 
always 1 for a rt-preempt kernel


I copied what was in my current kernel config, but I think I have seen 
both, =y and =yes,  =y especially regards modules in a kernel.


Anyway looks like it is sorted now, thanks Robert



Thanks,
Robert and Schooner

On Feb 19, 2019, at 12:43 PM, Robert Nelson > wrote:


On Tue, Feb 19, 2019 at 11:06 AM Robert Nelson 
mailto:robertcnel...@gmail.com>> wrote:


On Tue, Feb 19, 2019 at 10:26 AM Condit Alan > wrote:


Schooner and Robert,

OK, here is what I see when I run those tests. Rather than grep the 
results of uname -r, I just printed out uname -r.


machinekit@beaglebone:~$ cat /sys/kernel/realtime
cat: /sys/kernel/realtime: No such file or directory
machinekit@beaglebone:~$ cat /boot/config-4.19.23-bone-rt-r22 | 
grep CONFIG_PREEMPT_RT_FULL=yes

machinekit@beaglebone:~$
machinekit@beaglebone:~$ uname -a
Linux beaglebone 4.19.23-bone-rt-r22 #1stretch Sat Feb 16 22:07:49 
UTC 2019 armv7l GNU/Linux



Actually looking at /boot/config-4.19.23-bone-rt-r22 here is what I 
found with respect to CONFIG_PREEMPT_*

CONFIG_HAVE_PREEMPT_LAZY=y
CONFIG_PREEMPT_NONE=y
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT__LL is not set
# CONFIG_PREEMPT_RTB is not set
# CONFIG_PREEMPT_RT_FULL is not set


Ah Crap, 22 builds into the v4.19.x branch and we missed that...

https://github.com/RobertCNelson/bb-kernel/commit/b84cdf5a972d5e9f4347a37d6fa486ce92ab0c6b

pushing to build farm right now.


and now available:

sudo /opt/scripts/tools/update_kernel.sh

Regards,

--
Robert Nelson
https://rcn-ee.com/




--
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] How does machinekit test to see if it is running on a rt-preempt kernel?

2019-02-19 Thread schoone...@gmail.com


  
  
Thanks, that is what I suspected.

The main test for rt-preempt in rtapi_compat.c , is getting the
value in /sys/kernel/realtime, which should exist and be '1'
If that does not exist, it is going to default to POSIX, which is
the base fallback.

That is what has been happening.

I would expect a rt-preempt kernel to have a config with the
following set:

CONFIG_PREEMPT=y
CONFIG_PREEMPT_RT_BASE=y
CONFIG_HAVE_PREEMPT_LAZY=y
CONFIG_PREEMPT_LAZY=y
CONFIG_PREEMPT_RT_FULL=y
CONFIG_PREEMPT_COUNT=y
# CONFIG_PREEMPT_NONE is not set
  # CONFIG_PREEMPT_VOLUNTARY is not set
  # CONFIG_PREEMPT__LL is not set
  # CONFIG_PREEMPT_RTB is not set
  
  You can see the differences.
  
  If that kernel works, you can force the flavor detection by
  setting the env var, 
  but without those options set when built, not clear how realtime
  it can be.
  
  On 19/02/19 16:26, Condit Alan wrote:


  
  Schooner and Robert,
  

  OK, here is what I see when I run
  those tests. Rather than grep the results of uname -r, I just printed out
uname -r. 
  

  machinekit@beaglebone:~$ cat /sys/kernel/realtime
  cat:
  /sys/kernel/realtime: No such file or directory
  
  machinekit@beaglebone:~$ cat /boot/config-4.19.23-bone-rt-r22 | grep
  CONFIG_PREEMPT_RT_FULL=yes
  machinekit@beaglebone:~$
  
  machinekit@beaglebone:~$ uname -a
  Linux beaglebone 4.19.23-bone-rt-r22
  #1stretch Sat Feb 16 22:07:49 UTC 2019 armv7l
  GNU/Linux
  



  

  Actually
  looking at /boot/config-4.19.23-bone-rt-r22 here is
what I found with respect to CONFIG_PREEMPT_*
  CONFIG_HAVE_PREEMPT_LAZY=y
  CONFIG_PREEMPT_NONE=y
  #
  CONFIG_PREEMPT_VOLUNTARY is not set
  #
  CONFIG_PREEMPT__LL is not set
  #
  CONFIG_PREEMPT_RTB is not set
  #
  CONFIG_PREEMPT_RT_FULL is not set
  

  Even though machinekit “runs”
  i.e., starts up, it is clear that rt-preempt is not
  configured correctly to run machinekit in realtime. I
  can’t run my linux pc at the moment to look at how that config should be set, but I
believe that at the very least these changes should be made
  
  
  #
CONFIG_HAVE_PREEMPT_LAZY
  #
CONFIG_PREEMPT_NONE
  #
  CONFIG_PREEMPT_VOLUNTARY is not set
  #
  CONFIG_PREEMPT__LL is not set
  #
  CONFIG_PREEMPT_RTB is not set
  CONFIG_PREEMPT_RT_FULL=y 
  
  
  Thanks,
  Alan
  
  

  On Feb 19, 2019, at 1:42 AM, schoone...@gmail.com wrote:
  
  

 That is one
  way to deal with it.
  rtapi_compat.c first checks the env var FLAVOR, before
  trying to determine other ways
  
  Run these tests from a terminal and let us know what
  result you get
  
  cat /sys/kernel/realtime (should return 1)
  cat /boot/config-  | grep
  CONFIG_PREEMPT_RT_FULL=yes  ( should return
  CONFIG_PREEMPT_RT_FULL=yes)
  uname -a | grep 'PREEMPT RT'  ( should  return PREEMPT RT
  - but we already know it won't)
  
  There is something screwy about the 4.19 kernel and rt.  I
  stopped using the Debian rt-amd64 version and reverted to
  4.18 because of problems
  
  
  On 19/02/19 04:44, mugginsac
wrote:
  
  

  Robert just furnished a new test image.
It definitely has an rt-preempt kernel, when I
exported FLAVOR=rt-preempt, it ran machinekit.
  However, before I exported
FLAVOR=rt-preempt, machinekit tried to run the posix
realtime stuff (term of art).
  
  
  So, the question is how does machinekit
try to determine the nature of the kernel that it is
running on?
  
  
  Robert asked if we should just set
FLAVOR=rt-preempt in the environment when we create
the uSD. Is that acceptable?
  
  
  
  

-- 
website: http://www.machinekit.io
blog: http://blog.machinekit.io
g

Re: [Machinekit] How does machinekit test to see if it is running on a rt-preempt kernel?

2019-02-19 Thread schoone...@gmail.com


  
  
That is one way to deal with it.
rtapi_compat.c first checks the env var FLAVOR, before trying to
determine other ways

Run these tests from a terminal and let us know what result you get

cat /sys/kernel/realtime (should return 1)
cat /boot/config-  | grep
CONFIG_PREEMPT_RT_FULL=yes  ( should return
CONFIG_PREEMPT_RT_FULL=yes)
uname -a | grep 'PREEMPT RT'  ( should  return PREEMPT RT - but we
already know it won't)

There is something screwy about the 4.19 kernel and rt.  I stopped
using the Debian rt-amd64 version and reverted to 4.18 because of
problems


On 19/02/19 04:44, mugginsac wrote:


  
Robert just furnished a new test image. It definitely has
  an rt-preempt kernel, when I exported FLAVOR=rt-preempt, it
  ran machinekit.
However, before I exported FLAVOR=rt-preempt, machinekit
  tried to run the posix realtime stuff (term of art).


So, the question is how does machinekit try to determine
  the nature of the kernel that it is running on?


Robert asked if we should just set FLAVOR=rt-preempt in the
  environment when we create the uSD. Is that acceptable?




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

Re: [Machinekit] machinekit.ini and MKUUID

2019-02-18 Thread schoone...@gmail.com


  
  
I have now uninstalled and re-installed several times on a spare
Stretch partition, with and without a mkuuid file existing and
cannot replicate your problem.

It did remind me however of the arcane dpkg behaviour I noted when
originally testing this.

dpkg does not actually check the physical location for configuration
files and assumes their existence unless you have removed the
package
with `apt purge `

So if you remove machinekit, it will leave the /etc/linuxcnc folder
as is and assume it contains what it should do at next re-install.

The safest way to update, if you are doing so frequently, is to
create a 'clean slate' and do `apt purge machinekit*`

It will not touch the /etc/linuxcnc/mkuuid file if you have one,
because that is not part of the install manifest.
However if a particular MKUUID is not important to you, delete that
as well. 

The next re-install will copy machinekit.ini and rtapi.ini to
/etc/linuxcnc and update the MKUUID in machinekit.ini to a unique
one
and then create a mkuuid file containing it so that you can update
and retain the same MKUUID, if that matters.

The sed line which errored is here in the postinst file
https://github.com/machinekit/machinekit/blob/master/debian/machinekit.postinst#L87

The charactor 20 referred to is right on the divider between the
search term and the replacement one, which makes me suspect that
the first var had picked up a spurious char from the grep operation
and it was interpreted as a line ending which terminated the sed
operation prematurely.

Hopefully if you purge and re-install you should have no further
problems.

regards


On 18/02/19 07:39, schoone...@gmail.com
  wrote:


  
  There is nothing wrong with the sed command, can only assume
there is some spurious char in one of the variables causing
premature line termination.
  Go to /etc/linuxcnc and delete the mkuuid file and try again.
  That would have been created the last time you installed and
may be corrupt.
  
  
  
  On 2/18/2019 12:57 AM, Condit Alan
wrote:
  
  

I just did an update for machinekit. It reported an error
involving sed. I suspect the error is in the script that is
supposed to edit mkuuid and machinekit.ini. See the next to the
last line below (separated by ———).



  machinekit@beaglebone:~$ sudo apt-get install machinekit
  Reading package lists... Done
  Building dependency tree       
  Reading state information... Done
  The following additional packages will be
  installed:
    machinekit-rt-preempt
  The following packages will be upgraded:
    machinekit machinekit-rt-preempt
  2 upgraded, 0 newly installed, 0 to remove and 6
  not upgraded.
  Need to get 5,490 kB of archives.
  After this operation, 0 B of additional disk
  space will be used.
  Do you want to continue? [Y/n] y
  Get:1 http://deb.machinekit.io/debian
  stretch/main armhf machinekit-rt-preempt armhf
  0.1.1550234988.git6b4bdbf-1~stretch [1,044 kB]
  Get:2 http://deb.machinekit.io/debian
  stretch/main armhf machinekit armhf
  0.1.1550234988.git6b4bdbf-1~stretch [4,446 kB]
  Fetched 5,490 kB in 4s (1,259 kB/s)     
  (Reading database ... 51500 files and directories
  currently installed.)
  Preparing to unpack
  .../machinekit-rt-preempt_0.1.1550234988.git6b4bdbf-1~stretch_armhf.deb
  ...
  Unpacking machinekit-rt-preempt
  (0.1.1550234988.git6b4bdbf-1~stretch) over
  (0.1.1548236839.git1dfa004-1~stretch) ...
  Preparing to unpack
  .../machinekit_0.1.1550234988.git6b4bdbf-1~stretch_armhf.deb
  ...
  Unpacking machinekit
  (0.1.1550234988.git6b4bdbf-1~stretch) over
  (0.1.1548236839.git1dfa004-1~stretch) ...
  Processing triggers for mime-support (3.60) ...
  Processing triggers for libc-bin (2.24-11+deb9u3)
  ...
  Processing triggers for shared-mime-info
  (1.8-1+deb9u1) ...
  Processing triggers for rsyslog (8.24.0-1) ...
  Setting up machinekit-rt-preempt
  (0.1.1550234988.git6b4bdbf-1~stretch) ...
  Setting up machinekit
  (0.1.1550234988.git6b4bdbf-1~stretch) ...
  Installing new version of config file
  /etc/linuxcnc/rtapi.ini ...
  [ ok ] Restarting udev (via systemctl): udev.service.
  Valid MKUUID in mkuuid 
  538c1a6c-1b80-44c4-a11d-f85b171aef60 -

Re: [Machinekit] machinekit.ini and MKUUID

2019-02-17 Thread schoone...@gmail.com

There is nothing wrong with the sed command, can only assume there is 
some spurious char in one of the variables causing premature line 
termination.


Go to /etc/linuxcnc and delete the mkuuid file and try again.

That would have been created the last time you installed and may be corrupt.


On 2/18/2019 12:57 AM, Condit Alan wrote:
I just did an update for machinekit. It reported an error involving 
sed. I suspect the error is in the script that is supposed to edit 
mkuuid and machinekit.ini. See the next to the last line below 
(separated by ———).


machinekit@beaglebone:~$ sudo apt-get install machinekit
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  machinekit-rt-preempt
The following packages will be upgraded:
  machinekit machinekit-rt-preempt
2 upgraded, 0 newly installed, 0 to remove and 6 not upgraded.
Need to get 5,490 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://deb.machinekit.io/debian stretch/main armhf 
machinekit-rt-preempt armhf 0.1.1550234988.git6b4bdbf-1~stretch [1,044 kB]
Get:2 http://deb.machinekit.io/debian stretch/main armhf machinekit 
armhf 0.1.1550234988.git6b4bdbf-1~stretch [4,446 kB]

Fetched 5,490 kB in 4s (1,259 kB/s)
(Reading database ... 51500 files and directories currently installed.)
Preparing to unpack 
.../machinekit-rt-preempt_0.1.1550234988.git6b4bdbf-1~stretch_armhf.deb 
...
Unpacking machinekit-rt-preempt (0.1.1550234988.git6b4bdbf-1~stretch) 
over (0.1.1548236839.git1dfa004-1~stretch) ...
Preparing to unpack 
.../machinekit_0.1.1550234988.git6b4bdbf-1~stretch_armhf.deb ...
Unpacking machinekit (0.1.1550234988.git6b4bdbf-1~stretch) over 
(0.1.1548236839.git1dfa004-1~stretch) ...

Processing triggers for mime-support (3.60) ...
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Processing triggers for shared-mime-info (1.8-1+deb9u1) ...
Processing triggers for rsyslog (8.24.0-1) ...
Setting up machinekit-rt-preempt (0.1.1550234988.git6b4bdbf-1~stretch) ...
Setting up machinekit (0.1.1550234988.git6b4bdbf-1~stretch) ...
Installing new version of config file /etc/linuxcnc/rtapi.ini ...
[ ok ] Restarting udev (via systemctl): udev.service.
Valid MKUUID in mkuuid
538c1a6c-1b80-44c4-a11d-f85b171aef60 - using that
Value in mkuuid and ini files differ - using mkuuid
538c1a6c-1b80-44c4-a11d-f85b171aef60
--
sed: -e expression #1, char 20: unterminated `s’ command
--
Processing triggers for libc-bin (2.24-11+deb9u3) ...


Thanks,
Alan


On Feb 15, 2019, at 4:51 AM, Bas de Bruijn <mailto:b...@basdebruijn.com>> wrote:



On 15 Feb 2019, at 13:23, "schoone...@gmail.com 
<mailto:schoone...@gmail.com>" <mailto:schoone...@gmail.com>> wrote:



OK, found that problem.

The dependency was missed for Stretch because it uses another 
control file.

Should be built and in the repo by the end of the day.


PR’s have been merged.
So it should be available soon.



Thanks for persisting, only with that info was I able to look in the 
right place.


On 15/02/19 11:36, Ryan Press wrote:


On Fri, Feb 15, 2019 at 5:56 amschoone...@gmail.com 
<mailto:schoone...@gmail.com><mailto:schoone...@gmail.com>> wrote:



On 15/02/19 10:02, Ryan Press wrote:

I had the same problem with a fresh Debian Stretch install,
just a few days ago.

Ryan

On Thu, Feb 14, 2019, 1:57 PM mugginsac mailto:muggin...@gmail.com>wrote:

I just built a fresh uSD from one of Robert Nelson's
images. It does not include uuid-runtime.
Since machinekit now has to have a uuid generated the
first time it is run, shouldn't uuid-runtime be part of
the Machinekit requirements.



It is, but we have no control over what other people put, or
don't put, in their images.


I didn't use an image.  I installed Debian from a netinstall ISO, 
set up the machinekit repo, and installed the machinekit package.  
I did not notice the error message when it installed because apt 
continued on. Afterward I needed to figure out what packaged I 
needed to install (uuid-runtime) to fix the errors when running 
Machinekit.


Ryan




--
website:http://www.machinekit.io 
<http://www.machinekit.io/>blog:http://blog.machinekit.io 
<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 tomachinekit+unsubscr...@googlegroups.com 
<mailto:machinekit+unsubscr...@googlegroups.com>.

Visit this group athttps://groups.google.com/group/machinekit.
For more options, visithttps://groups.google.com/d/optout.


--
website:http://www.machinekit.io 
<http://www.machinekit.io/>blog:http://blog.mach

Re: [Machinekit] oneshot component with reset file

2019-02-17 Thread schoone...@gmail.com


  
  
This would add a functionality without affecting existing usage.

Why don't you submit a PR adding this change to the existing
oneshot.icomp?

On 16/02/19 23:31,
  johannes.fasso...@gmail.com wrote:


  A while back (08/17/2018) I needed to add a reset
function to the oneshot component that is available in
machinekit that was used in a .hal file being converted from a
linuxcnc version. With my recent work with machine kit I found
this file on one of my old hard drives and posted here. The wr
on the end stands for "with reset"
  
  -- 
  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.

Re: [Machinekit] Re: machinekit.ini and MKUUID

2019-02-15 Thread schoone...@gmail.com


  
  
OK, found that problem.

The dependency was missed for Stretch because it uses another
control file.
Should be built and in the repo by the end of the day.

Thanks for persisting, only with that info was I able to look in the
right place.

On 15/02/19 11:36, Ryan Press wrote:


  

  On Fri, Feb 15, 2019 at 5:56
AM schoone...@gmail.com
<schoone...@gmail.com>
wrote:
  
  
 
  On
15/02/19 10:02, Ryan Press wrote:
  
  

  I had the same problem with a fresh Debian
Stretch install, just a few days ago.
  
  
  Ryan


  On Thu, Feb 14, 2019, 1:57 PM
mugginsac <muggin...@gmail.com wrote:
  
  

  I just built a fresh uSD from one of
Robert Nelson's images. It does not include
uuid-runtime.
  Since machinekit now has to have a uuid
generated the first time it is run,
shouldn't uuid-runtime be part of the
Machinekit requirements.

  

  

  
  
  It is, but we have no control over what other people put,
  or don't put, in their images.

  
  
  
  I didn't use an image.  I installed Debian from a
netinstall ISO, set up the machinekit repo, and installed
the machinekit package.  I did not notice the error message
when it installed because apt continued on.  Afterward I
needed to figure out what packaged I needed to install
(uuid-runtime) to fix the errors when running Machinekit.
  
  
  Ryan
  
  

  


  




-- 
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] Machinekit on BBB - long boot times with PREEMPT kernel

2019-02-15 Thread schoone...@gmail.com


  
  
If you added the new kernel to a working image and had this problem,
then tried the new image with the new kernel and had the same
problem,
it tends to point squarely at the new kernel.

Either it is not a rt-preempt kernel, or it does not give off the
right signals.

The second line in your dmesg is way short of what would be expected
from an x86_64 rt-preempt kernel
You just have SMP
I would expect SMP RT PREEMPT

The kernel name having 'rt' in it irrelevant, as the kernel builder
can attach `-giraffe` prefix, but that does not make it one.

If you want to look in src/rtapi/ and grep 'flavor' you will see
where the determination is done.

The MKUUID issue was probably caused by using a new version of
machinekit on an old image base which did not contain 'genuuid'

The root cause is that the new kernel is not recognised as
rt-preempt and flavour defaults to posix.

Since you only have rt-preempt binaries etc. it errors.


On 14/02/19 22:37, Condit Alan wrote:


  
  I built another fresh uSD from the image I got from Robert Nelson,
  I installed ssh, xorg, openbox, and uuid-runtime. I tried running
  Machinekit again. And it is back to trying to
  load rtapi_app_posix.
  
  
  Where does machinekit find “flavor”?
  
  
  Here is a link to the
output from the attempt to start Machinekit, the output from
linuxcnc.log, linuxcnc_debug.txt, linuxcnc_print.txt,
machinekit.ini and mkuuid. And yes, I know the the output from
/var/log/linuxcnc.log is only one line long.
  
  
  Here is a link to output from dmesg:
  https://pastebin.com/UFveVH2f


Alan

  

  On Feb 14, 2019, at 10:00 AM, schoone...@gmail.com
wrote:
  
  

 I don't
  know why this would fail, unless new packages were
  somehow installed on a system that does not have
  `uuidgen` installed.
  
  Just generate a new MKUUID with uuidgen (if you don't
  have it, that is your problem right there, you need to
  install `uuid-runtime`) 
  and put it in your /etc/linuxcnc/machinekit.ini
  
  Then try again.
  
  (Need a link to the whole linuxcnc.log for the failed
  run next time, not just the line you think is
  important.  There is no context otherwise)
  
  On 14/02/19 16:44, Condit
Alan wrote:
  
  

after first startup and fail there was
  a 0 length file mkuuid in /etc/linuxcnc
and "MKUUID=" in machinekit.ini


on subsequent attempts to run it it
  tries to load rtapi_app_posix


Is there a simple way to reset
  machinekit to its initial state (like it has never
  been run yet)???




machinekit@beaglebone:~$ cat
  linuxcnc_debug.txt
2081
  PID TTY      STAT   TIME COMMAND
Stopping realtime threads
Unloading hal components


machinekit@beaglebone:~$ cat
  linuxcnc_print.txt
RUN_IN_PLACE=no
LINUXCNC_DIR=
LINUXCNC_BIN_DIR=/usr/bin
LINUXCNC_TCL_DIR=/usr/lib/tcltk/linuxcnc
LINUXCNC_SCRIPT_DIR=
LINUXCNC_RTLIB_DIR=/usr/lib/linuxcnc
LINUXCNC_CONFIG_DIR=
LINUXCNC_LANG_DIR=/usr/share/linuxcnc/tcl/msgs
INIVAR=/usr/libexec/linuxcnc/inivar
HALCMD=halcmd
LINUXCNC_EMCSH=/usr/bin/wish8.6
INIFILE=/home/machinekit/machinekit/configs/ARM.BeagleBone.Xylotex/Xylotex.ini
PARAMETER_FILE=pru-stepper.var
TASK=milltask
HALUI=halui
DISPLAY=axis
Starting Machinekit server program:
  linuxcncsvr
Loading Real Time OS, RTAPI, and
  HAL_LIB modules
Starting Machinekit IO program: io
Starting HAL U

Re: [Machinekit] Re: machinekit.ini and MKUUID

2019-02-15 Thread schoone...@gmail.com


  
  

On 15/02/19 10:02, Ryan Press wrote:


  
I had the same problem with a fresh Debian Stretch install,
  just a few days ago.


Ryan
  
  
On Thu, Feb 14, 2019, 1:57 PM mugginsac

Re: [Machinekit] Machinekit on BBB - long boot times with PREEMPT kernel

2019-02-13 Thread schoone...@gmail.com

You are going to have to do what it says at the end of the printout to 
narrow it down.


At least it is now a new error:-P

On 2/14/2019 5:21 AM, mugginsac wrote:

I buily a new uSD using the image that Robert sent me the link for.
I ran uname -r and it reports 4.19.15-ti-rt-r8.
I am guessing that the rt stands for rt-preempt???

I ran machinekit:
machinekit@beaglebone:~$ machinekit
MACHINEKIT - 0.1
Machine configuration directory is 
'/home/machinekit/machinekit/configs/ARM.BeagleBone.Xylotex'

Machine configuration file is 'Xylotex.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

rtapi: no service UUID (-R  or environment MKUUID) present
rtapi_app startup failed; aborting
halcmd: no service UUID (-R  or MACHINEKIT_INI [GLOBAL]MKUUID) 
present

io started
halcmd: no service UUID (-R  or MACHINEKIT_INI [GLOBAL]MKUUID) 
present

halcmd loadusr io started
halcmd: no service UUID (-R  or MACHINEKIT_INI [GLOBAL]MKUUID) 
present
halcmd: no service UUID (-R  or MACHINEKIT_INI [GLOBAL]MKUUID) 
present

Shutting down and cleaning up Machinekit...
halcmd: no service UUID (-R  or MACHINEKIT_INI [GLOBAL]MKUUID) 
present
halcmd: no service UUID (-R  or MACHINEKIT_INI [GLOBAL]MKUUID) 
present
halcmd: no service UUID (-R  or MACHINEKIT_INI [GLOBAL]MKUUID) 
present
halcmd: no service UUID (-R  or MACHINEKIT_INI [GLOBAL]MKUUID) 
present
halcmd: no service UUID (-R  or MACHINEKIT_INI [GLOBAL]MKUUID) 
present
halcmd: no service UUID (-R  or MACHINEKIT_INI [GLOBAL]MKUUID) 
present
halcmd: no service UUID (-R  or MACHINEKIT_INI [GLOBAL]MKUUID) 
present
halcmd: no service UUID (-R  or MACHINEKIT_INI [GLOBAL]MKUUID) 
present
halcmd: no service UUID (-R  or MACHINEKIT_INI [GLOBAL]MKUUID) 
present
halcmd: no service UUID (-R  or MACHINEKIT_INI [GLOBAL]MKUUID) 
present
halcmd: no service UUID (-R  or MACHINEKIT_INI [GLOBAL]MKUUID) 
present
halcmd: no service UUID (-R  or MACHINEKIT_INI [GLOBAL]MKUUID) 
present

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/


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

Re: [Machinekit] Machinekit on BBB - long boot times with PREEMPT kernel

2019-02-13 Thread schoone...@gmail.com


  
  
I know nothing about the BBB images generally and this one in
particular.
I don't know if the script you ran, even looks in the right place
for the new kernel.

I think you need to actually test Robert's new image, not hope you
can update your old one.

What I do know, is that the most common cause of this error, is
running a posix kernel with only rt-preempt packages installed.

The 'rtapi_app_posix not setuid' in this case means it tested if it
was setuid and that failed, 
but that was because it did not exist at all, as per the later
error.

If you have /usr/libexec/linuxcnc/rtapi_app_rt-preempt on your
system and were running what was recognised as a
rt-preempt kernel, it would try to use that.


On 13/02/19 16:26, Condit Alan wrote:


  
  Schooner,
  
  
  That was running an image from Robert C Nelson to
test out the fixes in a new kernel.
  I have an image that has been running OK except for
horrendous boot times. I updated the kernel with
  
4.19.19-bone-rt-r21
and now I get this:

machinekit@beaglebone:~$ machinekit
MACHINEKIT - 0.1
Machine configuration
directory is
'/home/machinekit/machinekit/configs/ARM.BeagleBone.Xylotex'
Machine configuration file
is 'Xylotex.ini'
Starting Machinekit...
Warning -
/usr/libexec/linuxcnc/rtapi_app_posix not setuid
'sudo make setuid'
missing?
rtapi_msgd command: 
/usr/libexec/linuxcnc/rtapi_msgd --instance=0
--rtmsglevel=1 --usrmsglevel=1 --halsize=524288
rtapi_app command: 
/usr/libexec/linuxcnc/rtapi_app_posix --instance=0
/usr/bin/realtime: line
237: /usr/libexec/linuxcnc/rtapi_app_posix: No such file
or directory
rtapi_app startup failed;
aborting
halcmd: cant connect to
rtapi_app: -1 (uri=
uuid=a42c8c6b-4025-4f83-ba28-dad21114744a): rtapi_rpc():
reply timeout

  
So can you tell did I
choose the wrong kernel???

  
I used this from elinux:

4.19.x All BeagleBone Variants + RT
sudo /opt/scripts/tools/update_kernel.sh --bone-rt-kernel --lts-4_19
  

  
Alan
  

      
    On Feb 12, 2019, at 11:11 PM, schoone...@gmail.com
  wrote:


  
  
Check what is installed.
The error re not setuuid is
  misleading, the main question is why are you trying to
  use rtapi_app_posix, it should be
  rt-preempt

On 2/13/2019 12:19 AM,
  Condit Alan wrote:


  
  Robert,
  
  
  I tried updating the kernel first on my
other image, but when I tried to start machinekit I
got a message unable to setuid need sudo makesetuid.
So I am trying the image that you gave me the link
to.
  
  
  I can invoke "ssh -Y machinekit@beaglebone.local”
but when I try to start machinekit I see this:
  
machinekit@beaglebone:~$ machinekit
MACHINEKIT - 0.1
application-specific

initialization failed: no display name and no
$DISPLAY environment variable
Error in startup
script: invalid command name "image"
    while
executing
"image create
photo -file $f/$i.gif"
    invoked from
within
"if [file exists
$f/$i.gif] {
            return
[image create photo -file $f/$i.gif]
        }"
    (procedure
"linuxcnc::image_search" line 7)
    invoked from
within
"linuxcnc::image_search

machinekit-wizard"
    invoked from
within
&q

Re: [Machinekit] Machinekit on BBB - long boot times with PREEMPT kernel

2019-02-12 Thread schoone...@gmail.com


Check what is installed.

The error re /not setuuid /is misleading, the main question is why are 
you trying to use *rtapi_app_posix, *it should be rt-preempt


On 2/13/2019 12:19 AM, Condit Alan wrote:

Robert,

I tried updating the kernel first on my other image, but when I tried 
to start machinekit I got a message unable to setuid need sudo 
makesetuid. So I am trying the image that you gave me the link to.


I can invoke "ssh -Y machinekit@beaglebone.local 
” but when I try to start 
machinekit I see this:

machinekit@beaglebone:~$ machinekit
MACHINEKIT - 0.1
application-specific initialization failed: no display name and no 
$DISPLAY environment variable

Error in startup script: invalid command name "image"
  while executing
"image create photo -file $f/$i.gif"
  invoked from within
"if [file exists $f/$i.gif] {
          return [image create photo -file $f/$i.gif]
      }"
  (procedure "linuxcnc::image_search" line 7)
  invoked from within
"linuxcnc::image_search machinekit-wizard"
  invoked from within
"set logo [linuxcnc::image_search machinekit-wizard]"
  (file "/usr/lib/tcltk/linuxcnc/bin/pickconfig.tcl" line 31)

So I did "sudo apt-get install xorg openbox”, and reboot.
Now I get:
machinekit@beaglebone:~$ machinekit
MACHINEKIT - 0.1
Machine configuration directory is 
'/home/machinekit/machinekit/configs/ARM.BeagleBone.Xylotex'

Machine configuration file is 'Xylotex.ini'
Starting Machinekit...
Warning - /usr/libexec/linuxcnc/rtapi_app_posix not setuid
'sudo make setuid' missing?
rtapi_msgd command: /usr/libexec/linuxcnc/rtapi_msgd --instance=0 
--rtmsglevel=1 --usrmsglevel=1 --halsize=524288

rtapi_app command: /usr/libexec/linuxcnc/rtapi_app_posix --instance=0
/usr/bin/realtime: line 237: /usr/libexec/linuxcnc/rtapi_app_posix: No 
such file or directory

rtapi_app startup failed; aborting
halcmd: no service UUID (-R  or MACHINEKIT_INI [GLOBAL]MKUUID) 
present

io started
halcmd: no service UUID (-R  or MACHINEKIT_INI [GLOBAL]MKUUID) 
present

halcmd loadusr io started
halcmd: no service UUID (-R  or MACHINEKIT_INI [GLOBAL]MKUUID) 
present
halcmd: no service UUID (-R  or MACHINEKIT_INI [GLOBAL]MKUUID) 
present

Shutting down and cleaning up Machinekit...
halcmd: no service UUID (-R  or MACHINEKIT_INI [GLOBAL]MKUUID) 
present
halcmd: no service UUID (-R  or MACHINEKIT_INI [GLOBAL]MKUUID) 
present
halcmd: no service UUID (-R  or MACHINEKIT_INI [GLOBAL]MKUUID) 
present
halcmd: no service UUID (-R  or MACHINEKIT_INI [GLOBAL]MKUUID) 
present
halcmd: no service UUID (-R  or MACHINEKIT_INI [GLOBAL]MKUUID) 
present
halcmd: no service UUID (-R  or MACHINEKIT_INI [GLOBAL]MKUUID) 
present
halcmd: no service UUID (-R  or MACHINEKIT_INI [GLOBAL]MKUUID) 
present
halcmd: no service UUID (-R  or MACHINEKIT_INI [GLOBAL]MKUUID) 
present
halcmd: no service UUID (-R  or MACHINEKIT_INI [GLOBAL]MKUUID) 
present
halcmd: no service UUID (-R  or MACHINEKIT_INI [GLOBAL]MKUUID) 
present
halcmd: no service UUID (-R  or MACHINEKIT_INI [GLOBAL]MKUUID) 
present
halcmd: no service UUID (-R  or MACHINEKIT_INI [GLOBAL]MKUUID) 
present

Warning - /usr/libexec/linuxcnc/rtapi_app_posix not setuid
'sudo make setuid' missing?
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/ 




Alan

On Feb 12, 2019, at 6:57 AM, Robert Nelson > wrote:


On Mon, Feb 11, 2019 at 4:39 PM mugginsac > wrote:


So, does that mean there will be a new Stretch-Machinekit image, or 
is it just the new kernel for the moment?


Please give this a shot:

https://rcn-ee.net/rootfs/bb.org/testing/2019-02-11/stretch-machinekit/

ps, let me know what else you want installed in it by default.

Regards,

--
Robert Nelson
https://rcn-ee.com/


--
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 blo

Re: [Machinekit] Sharing information / howto - Blog?

Malte, it is up there. http://blog.machinekit.io/

I have hopefully proof read it properly and corrected any spelling etc.
Let me know if there are any howlers.

Thanks for your contribution

On 07/02/19 14:52, Charles Steinkuehler wrote:

I can still get in. I removed you from the user list and sent you a
new invitation to the same gmail address.

Hopefully that will fix it.

On 2/7/2019 3:32 AM, schoone...@gmail.com wrote:

Hi Malte

Unfortunately, I seem unable to log into the machinekit blog any more.

Seems to have something to do with being required to use a Google+
account
originally and now those are defunct.
The login recognises my normal google log in but not that I am a
member of that
blog.

Hopefully someone else who still has access will be able to help.

If not we shall have to transfer all the blogs elsewhere
AFAIR the blog.machinekit.io is just a redirection to the blogger page

regards
On 05/02/19 07:16, schoone...@gmail.com wrote:

Hi Malte

Thanks for that it looks comprehensive.

I'll leave a couple of days for 'peer reviews by people who
actually know
about the BBB,

in case they have an input.

Then I will 'cut and paste' with a suitable header etc into the
machinekit blog

(If I can remember how :-))

regards

On 2/4/2019 7:54 PM, Malte Schmidt wrote:

Dear all,

first of all I would like to say a big THANK YOU to all the
contributors of
machinekit and linuxcnc. I do really value the effort you all put
into this !

When setting up my machine I realized that, while all needed
information was
available somewhere, the information was somewhat scattered
around and it
took some time to figure out what was relevant and what was not.
I therefore collected some notes and thought about posting this
somewhere
(blog) to help others. I have some background in Linux and
Linuxcnc (PC) as
user and did therefore not note down line for line but rather
tried to
capture the overall process of getting machinekit to work on a BBB.

My notes are below and I wonder if this would be good content for
the
machinekit blog. If yes, how can I post this there?

BR,
Malte

This document was written in December 2018/Januar 2019

The challenge:
Automate a lathe with 2 steppers, limit switches
Allow for manual turning using encoder input for x, z
Provide glass scales input for manual turning (this may be
considered
gold plating but my initial plan was to use this lathe in CNC or
manual mode)
Obviously have spindle feedback and control the lathe motor
Ideally controlled via touchscreen.

My leanings:

I considered the following approaches:
With the amount of inputs required a
- parallel port solution would only be feasible if multiple
parallel
ports are used. -> decided against it
- MESA card solution requires two cards -> expensive,
decided against it
- A beagle bone based solution with GPIO and PRUs -> my
tentatively
selected approach. Downside of this is the poor graphic performance

Linux on the Beagle Bone Black:
Three different options exist for Realtime in the Linux Kernel
- RTAI
- RT_PREEMPT
- Xenomai

All are patches to the vanilla Linux kernel.
- RTAI is old and seems to be superseded by...
- RT_PREEMPT which will be adapted by main Linux kernel
- Xenomai is commercial

My takeaway is that RT_PREEMPT would be ideal but Xenomai is
a possible
option.
Two different Debian Linux distributions have been considered:
- Strech
- Jessie

To get a Debian distribution and one of the realtime kernels
on the
beagle board three approaches have been explored:
1) Putting it toggelter by hand
(https://machinekoder.com/machinekit-debian-stretch-beaglebone-black/)

2) Getting Strech + RT_PREEMPT from eLinux
(http://www.machinekit.io/docs/getting-started/machinekit-images/
and
https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#BBW.2FBBB_.28All_Revs.29_Machinekit)

3) Getting Jessie + Xenomai from eLinux (see links above)

Findings
- Current RT_PREEMPT + Strech combinations 1) and 2) above
have long boot
times of 2-4 minutes.
- The blog post in 1) is a good read in any case to perform
some steps to
get the system up to date and further improve boot times
Flashing
- I was not able to flash using the procedures described in
most online
places. I booted from SD and than used the approach outlined
(https://stackoverflow.com/questions/33930747/how-to-flash-beaglebone-black-emmc-with-debian-8-2-image)

cd /opt/scripts/tools/eMMC/
sudo ./init-eMMC-flasher-v3.sh

I'm currently using Jessie and Preempt_RT because I'm lazy.
There is some
background here on the boot time issue which will hopefully be
resolved in
the future:
https://groups.google.com/forum/#!topic/machinekit/sOWj5I7fVpo
Cape support
- No commercially available cape was suitable to be used
with my
requireme

Re: [Machinekit] Usespace component with C++?


  
  
I have attached a tar.gz of a simple demo I wrote for someone a
while back.

It shows the basic calls required to register, create pins etc. and
then do something in a loop in Qt5.

The paths in the .pro file will need editing.
I used to keep a copy of all the machinekit includes and libs under
/usr/local, so that I didn't need
to have a copy of Machinekit built, to build Qt stuff.

I personally do not use QtCreator much, except for occasional
Android programs, where it makes things easier.
I just use a terminal based file editor / file management program
and run qmake etc from the command line.
You can just import these files and build / run etc under QtCreator
however.

I tend to use Qt, even for terminal programs, because I am familiar
with it and have a lot of libraries written
in it for Machinekit.
For any kind of UI, it comes into its own and just makes life
simpler ( for me at least ).

But if std:: C++ is what you prefer, go with that.

regards

On 07/02/19 11:20, 'Boris Skegin' via
  Machinekit wrote:


  

On Thursday, February 7, 2019 at 10:13:25 AM UTC+1, Schooner
wrote:

  
I do it all the time with Qt.

  



That may be the way around.


So do you use a Qt project file  and QtCreator to build
  userspace componets?
I ask, as one can buidl pure C++ (non Qt) apps with
  QtCreator too. 
  
  -- 
  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.


QtDemo2.tar.gz
Description: Unix tar archive

Re: [Machinekit] Sharing information / howto - Blog?


  
  
Hi Malte

Unfortunately, I seem unable to log into the machinekit blog any
more.

Seems to have something to do with being required to use a Google+
account originally and now those are defunct.
The login recognises my normal google log in but not that I am a
member of that blog.

Hopefully someone else who still has access will be able to help.

If not we shall have to transfer all the blogs elsewhere
AFAIR the blog.machinekit.io is just a redirection to the blogger
page

regards
On 05/02/19 07:16, schoone...@gmail.com
  wrote:


  
  Hi Malte
  Thanks for that it looks comprehensive.
  I'll leave a couple of days for 'peer reviews by people who
actually know about the BBB,
  in case they have an input.
  Then I will 'cut and paste'  with a suitable header etc into
the machinekit blog
  (If I can remember how :-))
  regards
  
  
  
  On 2/4/2019 7:54 PM, Malte Schmidt
wrote:
  
  


  Dear all,
  
  
  first of all I would like to say a big THANK YOU to all
the contributors of machinekit and linuxcnc. I do really
value the effort you all put into this !
  
  
  When setting up my machine  I realized that, while all
needed information was available somewhere, the information
was somewhat scattered around and it took some time to
figure out what was relevant and what was not.
  I therefore collected some notes and thought about
posting this somewhere (blog) to help others. I have some
background in Linux and Linuxcnc (PC) as user and did
therefore not note down line for line but rather tried to
capture the overall process of getting machinekit to work on
a BBB. 
  
  
  My notes are below and I wonder if this would be good
content for the machinekit blog. If yes, how can I post this
there?
  
  
  BR,
  Malte
  
  
  
  
  


This document was written in December 2018/Januar 2019


The challenge:
    Automate a lathe with 2 steppers, limit switches
    Allow for manual turning using encoder input for x,
  z
    Provide glass scales input for manual turning (this
  may be considered gold plating but my initial plan was to
  use this lathe in CNC or manual mode)
    Obviously have spindle feedback and control the
  lathe motor
    Ideally controlled via touchscreen.


My leanings:


I considered the following approaches:
    With the amount of inputs required a 
    - parallel port solution would only be feasible if
  multiple parallel ports are used. -> decided against it
    - MESA card solution requires two cards ->
  expensive, decided against it
    - A beagle bone based solution with GPIO and PRUs
  -> my tentatively selected approach. Downside of this
  is the poor graphic performance


Linux on the Beagle Bone Black:
    Three different options exist for Realtime in the
  Linux Kernel
    - RTAI
    - RT_PREEMPT
    - Xenomai


    All are patches to the vanilla Linux kernel. 
    - RTAI is old and seems to be superseded by...
    - RT_PREEMPT which will be adapted by main Linux
  kernel
    - Xenomai is commercial


    My takeaway is that RT_PREEMPT would be ideal but
  Xenomai is a possible option.
    
    Two different Debian Linux distributions have been
  considered:
    - Strech
    - Jessie


    To get a Debian distribution and one of the
  realtime kernels on the beagle board three approaches have
  been explored:
    1) Putting it toggelter by hand (https://machinekoder.com/machinekit-debian-stretch-beaglebone-black/)
    2) Getting Strech + RT_PREEMPT from eLinux (http://www.machinekit.io/docs/getting-started/machinekit-images/
  and
  https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#BBW.2FBBB_.28All_Revs.29_Machinekit)
    3) Getting Jessie + Xenomai from eLinux (see links
  above)

Re: [Machinekit] Usespace component with C++?


  
  
Hi Boris,

There is nothing to prevent the use of C++ in userspace components,

I do it all the time with Qt.

When we were writing the multicore changes and instantiated
components, 
I originally wrote C++ instantiated components, which worked.

When we re-visited them recently, I could not remember the build and
linkage options
I used and was unable to get them built.  Can't remember the exact
details.
Others tried too with the same result, so maybe something changed in
the interim?

C++ for a RT component is at best psuedo C++, because several
functions have to be
declared as static to get the callback references to work
and you have to use 'extern "C"' to link to rtapi_app_main()' and
'rtapi_app_exit()'.

There would be no compelling reason to use C++ in RT components, but
userspace ones allow 
the full use of GUIs and other useerspace libs and are very useful.

regards

On 07/02/19 08:51, 'Boris Skegin' via
  Machinekit wrote:


  Hallo.


I remember there wew some plans to let C++ be used for
  userspace components.


Did I miss any updates on this theme?


Thanks.


Regards,
boris
  
  -- 
  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.

Re: [Machinekit] Sharing information / howto - Blog?

2019-02-04 Thread schoone...@gmail.com


Hi Malte

Thanks for that it looks comprehensive.

I'll leave a couple of days for 'peer reviews by people who actually 
know about the BBB,


in case they have an input.

Then I will 'cut and paste'  with a suitable header etc into the 
machinekit blog


(If I can remember how :-))

regards


On 2/4/2019 7:54 PM, Malte Schmidt wrote:

Dear all,

first of all I would like to say a big THANK YOU to all the 
contributors of machinekit and linuxcnc. I do really value the effort 
you all put into this !


When setting up my machine  I realized that, while all needed 
information was available somewhere, the information was somewhat 
scattered around and it took some time to figure out what was relevant 
and what was not.
I therefore collected some notes and thought about posting this 
somewhere (blog) to help others. I have some background in Linux and 
Linuxcnc (PC) as user and did therefore not note down line for line 
but rather tried to capture the overall process of getting machinekit 
to work on a BBB.


My notes are below and I wonder if this would be good content for the 
machinekit blog. If yes, how can I post this there?


BR,
Malte



This document was written in December 2018/Januar 2019

The challenge:
    Automate a lathe with 2 steppers, limit switches
    Allow for manual turning using encoder input for x, z
    Provide glass scales input for manual turning (this may be 
considered gold plating but my initial plan was to use this lathe in 
CNC or manual mode)

    Obviously have spindle feedback and control the lathe motor
    Ideally controlled via touchscreen.

My leanings:

I considered the following approaches:
    With the amount of inputs required a
    - parallel port solution would only be feasible if multiple 
parallel ports are used. -> decided against it
    - MESA card solution requires two cards -> expensive, decided 
against it
    - A beagle bone based solution with GPIO and PRUs -> my 
tentatively selected approach. Downside of this is the poor graphic 
performance


Linux on the Beagle Bone Black:
    Three different options exist for Realtime in the Linux Kernel
    - RTAI
    - RT_PREEMPT
    - Xenomai

    All are patches to the vanilla Linux kernel.
    - RTAI is old and seems to be superseded by...
    - RT_PREEMPT which will be adapted by main Linux kernel
    - Xenomai is commercial

    My takeaway is that RT_PREEMPT would be ideal but Xenomai is a 
possible option.

    Two different Debian Linux distributions have been considered:
    - Strech
    - Jessie

    To get a Debian distribution and one of the realtime kernels on 
the beagle board three approaches have been explored:
    1) Putting it toggelter by hand 
(https://machinekoder.com/machinekit-debian-stretch-beaglebone-black/)
    2) Getting Strech + RT_PREEMPT from eLinux 
(http://www.machinekit.io/docs/getting-started/machinekit-images/ and 
https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#BBW.2FBBB_.28All_Revs.29_Machinekit)

    3) Getting Jessie + Xenomai from eLinux (see links above)

    Findings
    - Current RT_PREEMPT + Strech combinations 1) and 2) above have 
long boot times of 2-4 minutes.
    - The blog post in 1) is a good read in any case to perform some 
steps to get the system up to date and further improve boot times

    Flashing
    - I was not able to flash using the procedures described in most 
online places. I booted from SD and than used the approach outlined 
(https://stackoverflow.com/questions/33930747/how-to-flash-beaglebone-black-emmc-with-debian-8-2-image)

        cd /opt/scripts/tools/eMMC/
        sudo ./init-eMMC-flasher-v3.sh

    I'm currently using Jessie and Preempt_RT because I'm lazy. There 
is some background here on the boot time issue which will hopefully be 
resolved in the future:

https://groups.google.com/forum/#!topic/machinekit/sOWj5I7fVpo
Cape support
    - No commercially available cape was suitable to be used with my 
requirements. So I decided to go with a Sparkfun prototype cape and 
wire up things from there.
    The name of the board coded in the EEPROM will tell which device 
tree overlay file to load. The device tree overlay file declares the 
pins we can use with this cape.

    (cf https://github.com/jbdatko/eeprom_tutorial/blob/master/eeprom.md)
    With different Linux versions different approaches exist how this 
is achieved.

    Linux 3.8 / Xenomai + Jessie uses capemanager
    Linux 4.4 / Preempt_RT + Strech uses U-boot overlays

    Most resources in the internet are about capemanager.
    We need two things for loading the cape during boot:
    -- EEPROM
    -- Device Tree overlay file

    - The easiest way to get through this is using existing device 
tree overlay files. 
(https://github.com/cdsteinkuehler/beaglebone-universal-io)
    - This means that the eeprom needs to be coded such that those are 
loaded.
      Use https://github.com/picoflamingo/BBCape_EEPROM to write e.g. 
cape-universal in both the board name and revision field

[Machinekit] machinekit.ini and MKUUID

2019-01-16 Thread schoone...@gmail.com


  
  
Hi All,

Just an advisory, which may or may not affect you.

Since inception, /etc/linuxcnc has contained a hard coded UUID under
the 'MKUUID=' field

This despite the text above it stating that all machines should have
a unique MKUUID to enable the
zeroconf browsing for particular instances to work.

This has now actually caused problems, with some users exploring the
networked communications aspect
of machinekit, as perhaps it was originally envisaged.

So, from today for RIP builds and as of machinekit package serial 'machinekit_0.1.1547649222.gitc44e93e-1'
onwards,
there are a couple of wrinkles to be aware of, if you actually
intend using the MKUUID for anything.

RIP builds
A fresh clone will generate a new UUID when built.
If you want to use a particular UUID, keep it in a separate system
file called /etc/linuxcnc/mkuuid [1] and manually edit
RIP/etc/linuxcnc/machinekit.ini to use it.
When you rebuild the machinekit.ini UUID will be preserved, however
be aware doing a complete ' git clean -xdf && ./autogen.sh
&& ./configure' will wipe it.

([1] For RIPs, this file is just a suggested failsafe storage option
for now, it will actually be used by package installs)

Package installs
A package install onto a blank system will generate a new UUID.

If you are updating and do not purge your configs:

  If the package finds an /etc/linuxcnc/mkuuid file [1], it will
use the MKUUID within if valid, over any other option.


  If machinekit.ini exists with a valid UUID, it will use that. 
Otherwise it will update with the generated UUID.


  If machinekit.ini is missing even though the previous package
was not purged, it will generate one with a valid UUID.


For the vast majority of users, this change will have no impact,
their configs just use whatever UUID is in machinekit.ini, if at
all,
without consequence.

regards
  




-- 
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] Moving while limit asserted

2019-01-16 Thread schoone...@gmail.com


Sorry a bit of a delay, missed this.

You have not said what GUI you are using, machinekit is not the interface.

Under Axis, you simply click the override tick box and switch the 
machine button to on again.


Under Cetus... who knows.

To do it in machinekit directly, you need to do the same as the python 
lib used by Axis does, issue an EMC_AXIS_OVERRIDE_LIMITS instruction

src/emc/usr_intf/axis/extensions/emcmodule.cc


On 12/01/19 03:45, Scott Nortman wrote:

Is there a way to configure machinekit to allow movement when a limit is 
asserted, in the opposite direction?  For example, if my machine starts with 
the min limit asserted, how can I permit motion in the positive direction?



--
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] Machinekit not loading after upgrade

2019-01-11 Thread schoone...@gmail.com


  
  
The log snippets tell you the error is on line 14 of your hal file

The line is 
loadrt hm2_pci config=" num_encoders=0 num_pwmgens=1 num_3pwmgens=0
num_stepgens=5 sserial_port_0= "

Unless hm2_pci does not exist, looks like it does not like the
config string.

It appears you have a 5i25, so the firmware is flashed.  It looks
quite non standard

http://www.machinekit.io/docs/man/man9/hostmot2/ :
The 5i25 / 6i25 come pre-programmed with firmware and no "firmware="
string
should be used with these cards. 
To change the firmware on a 5i25 or 6i25 the
"mesaflash" utility should be used (available from Mesa). 
It is perfectly
  valid and reasonable to load these cards with no config string at
  all.

Try removing the config string and see what happens

If not fixed, follow the procedure at 

http://www.machinekit.io/docs/getting-help/#how-to-report-an-error

and DEBUG=5 should result in messages to show exactly why it failed


On 09/01/19 17:36, mac44mag wrote:


  
Problem:  After doing a system upgrade Machinekit will not
  load.  When run from either the Applications menu or Terminal,
  program fails to run after selecting user defined WorkBee CNC
  router.  Supplied sim machine (axis) loads normally.  Router
  via Machinekit was running normally before upgrade.  I
  (personally) changed nothing after upgrading.  After the
  upgrade, I shut down, rebooted and attempted to load
  Machinekit.  Nada...zilch...zero point...


Computer:  Linux Stretch kernel: 4.9.0-8-rt-amd64, AMD
  Phenom II x4 in 64 bit, 24 GB RAM (I know, but it was free),
  Mesa 5i25 card pushing a Gecko G540 controller.  Please see
  attached file for detailed processor specs.



Background:  Project (CNC router) begun apprx. 17 months
  ago as a learning exercise with the purpose of supporting my
  radio control plane building hobby.  I'm well versed in the
  Windows world, but I'm a newcomer to Linux.  I can normally
  follow simple instructions, but sometimes the vocabulary
  iswell, you know.


I have attached a text file with the contents of: 
  linuxcnc.log, linuxcnc_debug.txt, linuxcnc_print.txt, along
  with the output from lscpu and uname -r.  In addition, I've
  attached my .hal and .ini files.  If there is anything else
  that I can do to help, please do not hesitate to let me know.


Thank you in advance for any help you might be able to give
  me.


Leonard





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

Re: [Machinekit] Unable to launch project ported from linuxcnc under binaries or built from source

2019-01-04 Thread schoone...@gmail.com


  
  

On 04/01/19 12:54, Ross Lloyd wrote:


  Thank you for your help. I am running into some new
issues, but I will keep endeavouring to find a solution to them
before creating a new post. 


As a side note, I have now read the getting help
  instruction. My apologies if this initial query was
  inconsistent with the submission requirements.
  


No problem, most of them are :)

The DEBUG=5 export will put loads of stuff into the linuxcnc.log,
which usually pinpoints where an error is originating, so is very
useful


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

Re: [Machinekit] Unable to launch project ported from linuxcnc under binaries or built from source

2019-01-03 Thread schoone...@gmail.com

No, what you hit is the 'biggie', most other changes are in things not 
available in linuxcnc or where legacy options are still operational.


eg. all components (nearly) are instantiable, but the old loadrt still 
works.


I would sort out that section and retry.  If you hit more problems, the 
site has advice on seeking help, which includes the debug options


to get the required info to help you


On 1/3/2019 8:02 PM, Ross Lloyd wrote:
Thank you, I will work through my files and identify where the MK 
format differs.


Out of curiosity, I've not seen one from a quick google and search of 
the MK site, but do you have a linuxcnc to machinekit porting guide 
available?

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

Re: [Machinekit] Unable to launch project ported from linuxcnc under binaries or built from source

2019-01-03 Thread schoone...@gmail.com


  
  
You need to look at what runs on machinekit, not just try to run a
linuxcnc config without any adaption

https://github.com/machinekit/machinekit/blob/master/configs/stepper/mah_stepper.hal
is an example

You will then see that your line


  loadrt [EMCMOT]EMCMOT servo_period_nsec=[EMCMOT]SERVO_PERIOD  traj_period_nsec=[EMCMOT]TRAJ_PERIOD num_joints=[KINS]JOINTS



  is different and that is where THAT error is coming from.

ie. no 'tp=tp kins=trivkins' 
(and possibly no 'loadrt tp' beforehand, because you have
snipped the file so can't tell)

  
  

On 03/01/19 17:20, Ross Lloyd wrote:


  Hi


I have a project that works under linuxcnc, and due to the
  ROS capability of machinekit am trying to get it set up with
  the latter. It is a 6DOF robot arm being run by STMBL drives.
  These are driven by Mesa 7i74 motion control card through a
  7i92m I/O Anything card. Firmware was installed and working
  with linuxcnc. On Debian wheezy it ran with kernel
3.4-9-rtai-686-pae.


Under MK I am able to ping the card from the host PC, which
  is an old Intel Core 2 Duo E7400 based machine.



My starting point with machinekit was to build from source,
  but I switched to binary install as I was unable to get any
  flavor working. If details on the separate set of issues
  encountered there are helpful, I will post those. For now for
  the sake of clarity here are there errors encountered with the
  binary install. The behaviour is induced by running MK
  from menu or terminal and selecting my project from the gui.


From linuxcnc.log:



  
  
Jan  3 14:36:44 home msgd:0: startup pid=10774 flavor=rt-preempt rtlevel=1 usrlevel=1 halsize=524288 shm=Posix cc=gcc 4.9.2  version=v0.1~-detached~57e93bf

Jan  3 14:36:44 home msgd:0: Ã˜MQ=4.0.5 czmq=4.0.2 protobuf=2.6.1 atomics=gcc intrinsics    libwebsockets=

Jan  3 14:36:44 home msgd:0: configured: sha=57e93bf

Jan  3 14:36:44 home msgd:0: built:      Jan  2 2019 16:19:23 sha=57e93bf

Jan  3 14:36:44 home msgd:0: register_stuff: actual hostname as announced by avahi='home.local'

Jan  3 14:36:44 home msgd:0: zeroconf: registering: 'Log service on home.local pid 10774'

Jan  3 14:36:44 home rtapi:0: rtapi_app_main(motmod): -1 Operation not permitted

Jan  3 14:36:45 home msgd:0: zeroconf: registered 'Log service on home.local pid 10774' _machinekit._tcp 0 TXT "uuid=a42c8c6b-4025-4f83-ba28-dad21114744a" "instance=fe02fdf2-0f64-11e9-9c5a-0023ae8fd383" "service=log" "dsn=ipc://
/tmp/0.log.a42c8c6b-4025-4f83-ba28-dad21114744a"

Jan  3 14:36:47 home rtapi:0: unload: 'genserkins' not loaded

Jan  3 14:36:47 home msgd:0: rtapi_app exit detected - scheduled shutdown

Jan  3 14:36:49 home msgd:0: msgd shutting down

Jan  3 14:36:49 home msgd:0: zeroconf: unregistering 'Log service on home.local pid 10774'

Jan  3 14:36:49 home msgd:0: log buffer hwm: 0% (0 msgs, 0 bytes out of 524288)

Jan  3 14:36:49 home msgd:0: normal shutdown - global segment detached
  

  
  And from the terminal:



  
  
machine-user@home:~$ machinekit

MACHINEKIT - 0.1

Machine configuration directory is '/home/machine-user/machinekit/configs/rx60'

Machine configuration file is 'rx60.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

hm2-stepper.hal:5: insmod failed, returned -1:

rtapi_app_main(motmod): -1 Operation not permitted
  

  
  linuxcnc_print.txt



  
  
RUN_IN_PLACE=no

LINUXCNC_DIR=

LINUXCNC_BIN_DIR=/usr/bin

LINUXCNC_TCL_DIR=/usr/lib/tcltk/linuxcnc

LINUXCNC_SCRIPT_DIR=

LINUXCNC_RTLIB_DIR=/usr/lib/linuxcnc

LINUXCNC_CONFIG_DIR=

LINUXCNC_LANG_DIR=/usr/share/linuxcnc/tcl/msgs

INIVAR=/usr/libexec/linuxcnc/inivar

HALCMD=halcmd

LINUXCNC_EMCSH=/usr/bin/wish8.6

INIFILE=/home/machine-user/machinekit/configs/rx60/rx60.ini

PARAMETER_FILE=hm2-stepper.var

TASK=milltask

HALUI=

DISPLAY=axis

Starting Machinekit server program: linuxcncsvr

Loading Real Time OS, RTAPI, and HAL_LIB modules

Starting Machinekit IO program: io

Killing task linuxcncsvr, PID=14341

Removing HAL_LIB, RTAPI, and Real Time OS modules

Removing NML shared memory segments
  

  
  
  Relevant entries from my hal file

Re: [Machinekit] Adding tool 7 and 8 to other position than the real turret for lathe (more clear video link)

2019-01-03 Thread schoone...@gmail.com


  
  

On 01/01/19 21:46, Aurelien wrote:


  Hi


I like if you can help me to start understanding the
  possibility to add other tool to my changer.


I have same lathe as this video but without the moutning
  plate for toll 7 and 8 but from the start i like to add
  secondary tool turret for Drill.


The Michael Stolt solution is easy to do, so i like to
  start coding for add this purpose to my toolchanger.

  https://www.youtube.com/watch?v=EPbJZPpPJlg




For now i think i need only to bypass all move from TC if
  tool is 7 or 8 and do 


net tool-changed iocontrol.0.tool-changed <=
  toolchanger.toolchanged
  


Unfortunately not.
If you already have a tool changer component, it will be connected
to the iocontrol.0.tool-changed pin already

More importantly it will be connected to the iocontrol.0.tool-change
and iocontrol.0.tool-number pins, so the toolchanger component
will receive the signal to change tool and which tool to change to.

Any differential logic regards what to do based upon tool number,
will have to happen there.

If you are drilling at workpiece dead centre, this only involves
moving the slide mounted tooling rack to an offset
which equates to that X position, as all  the other moves will be on
the Z axis.

If you share your toolchanger component, may be able to help.

If you have not written one, then see my info page on writing them.
It covers 3 different types of toolchanger components that I have
written, 2 for similar ATCs.
http://www.machinekit.io/docs/developing/toolchangers/


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

Re: [Machinekit] Machinekit on BBB - long boot times with PREEMPT kernel

2018-12-31 Thread schoone...@gmail.com


  
  
OK, it was just a thought.

The 4.14 kernel seems to be problematic.
There are quite a few references to problems on RPi forums as well
as some on this forum, where
users went back to the 4.4 or 4.9.

On 31/12/18 08:17, Malte Schmidt wrote:


  

  
I changed fstab to contain UUID and uncommented uuid in
  uEnv.txt. I don't think this is it. 
Kernel boots with the commmandline containing the UUID
  for root. UUID set in fstab but still no improvement :-(


machinekit@beaglebone:~$ uname -a
Linux beaglebone 4.14.79-ti-rt-r84 #1 SMP PREEMPT RT
  Tue Nov 13 20:33:45 UTC 2018 armv7l GNU/Linux
  
  
  
  machinekit@beaglebone:~$ cat /proc/cmdline
  console=ttyO0,115200n8
bone_capemgr.uboot_capemgr_enabled=1
root=UUID=94daacb3-de67-41a5-8087-c68a02c7e893 ro
rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0
quiet
  
  
  machinekit@beaglebone:~$ cat /etc/fstab
  UUID=94daacb3-de67-41a5-8087-c68a02c7e893 /  ext4 
noatime,errors=remount-ro  0  1
  
  debugfs  /sys/kernel/debug  debugfs  defaults  0  0
  
  
  machinekit@beaglebone:~$ systemd-analyze blame
       1min 4.570s generic-board-startup.service
           20.171s dev-mmcblk0p1.device
            5.046s systemd-udev-trigger.service
  
  


  machinekit@beaglebone:~$ blkid
  /dev/mmcblk0p1: LABEL="rootfs"
UUID="94daacb3-de67-41a5-8087-c68a02c7e893" TYPE="ext4"
PARTUUID="e086444d-01"
  /dev/mmcblk1p1: LABEL="rootfs"
UUID="ab7cd6a9-12eb-434d-b05b-3a51654aec76" TYPE="ext4"





Am Sonntag, 30. Dezember 2018 22:46:23 UTC+1 schrieb Malte
Schmidt:

  Thanks all. I will give that a try

Am Samstag, 29. Dezember 2018 09:44:08 UTC+1 schrieb Bas de
Bruijn:

  



  On 29 Dec 2018, at 09:31, "schoo...@gmail.com" 
  wrote:
  


   I don't know if this is related  and know
nothing specifically about BBB, but the line
1min 30.559s
dev-mmcblk1p1.device
raises some suspicions.

The newer linux kernels are prone to hanging for
1min 30 secs where there are problems with a 'start
job'
which usually relates to mounting a drive.

What usually happens is often related to the 'resume
/ suspend to disk' capability of the kernel, whether
you use it or not.

Take this scenario:
You install a distro on a spare partition.
The Debian install program will format the partition
you have chosen plus the swap partition.
However the reformatting of the swap partition also
changes the UUID

Next boot of your original partition, the UUID in
/etc/fstab for the swap partition is wrong and you
get a 90 sec wait with the 'A start job for
dev-disk-by-uuid-xxx' message
  



I got the exact situation a few months ago when
  installing Buster along side Stretch on my laptop.
  When booting Stretch again it was looking for the
  ‘newer’ UUID of the swap partition.
Changed that uuid in fstab file and problem was
  solved.



   So now you adjust your fstab file to point to
the right UUID and reboot

On booting there is another wait whilst the kernel
repeatedly tries to access the UUID it holds for
Resume (which is the old swap partition UUID)

You then need to go to /etc/initramfs-tools/conf.d/resume
and change the UUID in that file for the new one for
the swap partition
Then you need to run 'makeinitramfs' for each
bootable kernel, to create a new ram image which has
the correct UUID for swap in it

Re: [Machinekit] Machinekit on BBB - long boot times with PREEMPT kernel

2018-12-29 Thread schoone...@gmail.com


  
  
I don't know if this is related  and know nothing specifically about
BBB, but the line
1min 30.559s
dev-mmcblk1p1.device
raises some suspicions.

The newer linux kernels are prone to hanging for 1min 30 secs where
there are problems with a 'start job'
which usually relates to mounting a drive.

What usually happens is often related to the 'resume / suspend to
disk' capability of the kernel, whether you use it or not.

Take this scenario:
You install a distro on a spare partition.
The Debian install program will format the partition you have chosen
plus the swap partition.
However the reformatting of the swap partition also changes the UUID

Next boot of your original partition, the UUID in /etc/fstab for the
swap partition is wrong and you
get a 90 sec wait with the 'A start job for dev-disk-by-uuid-xxx'
message

So now you adjust your fstab file to point to the right UUID and
reboot

On booting there is another wait whilst the kernel repeatedly tries
to access the UUID it holds for Resume (which is the old swap
partition UUID)

You then need to go to /etc/initramfs-tools/conf.d/resume and change
the UUID in that file for the new one for the swap partition
Then you need to run 'makeinitramfs' for each bootable kernel, to
create a new ram image which has the correct UUID for swap in it

THEN your original partition will boot quickly.

I would study the elements described above to make sure that the
device designation matches the UUID held in fstab /
initramfs- etc etc

If you have introduced a new kernel whose initramfs is not matched
to your system, that is a possible cause.

Either way, would be interested to hear the answer when you find it

regards


On 26/12/18 19:18, Malte Schmidt wrote:


  Dear all,


this may be the wrong forum but my questions seem to fit
  neither perfectly the Machinekit nor Beaglebone forums


I've been following this manual to setup Machinekit with
  Preempt_RT on a BBB. 
https://machinekoder.com/machinekit-debian-stretch-beaglebone-black/



Resulting in a Strech installation with preempt_rt kernel
  v4.4. With this kernel I'm getting long-long boot times of
  ~2-3 minutes. In the "default" installation this seems to be
  related to generic board startup service:
The output of systemd-analyze blame with 

           51.582s
  dev-mmcblk1p1.device
           47.793s
  generic-board-startup.service
            8.600s
  NetworkManager-wait-online.service
            4.290s
  systemd-udev-trigger.service
            ...
  



When I disable this serivce I'm getting thisd-analyze
blame

      1min 30.559s
  dev-mmcblk1p1.device
            9.837s
  NetworkManager-wait-online.service
            4.739s
  systemd-udev-trigger.service
            ...



And I can't make something out of the critical path
  analysis which shows:

  graphical.target
  @55.127s
  └─multi-user.target
  @55.121s
    └─getty.target
  @54.807s
     
  └─serial-getty@ttyGS0.service @54.785s
       
  └─dev-ttyGS0.device @54.762s





This issue does not seem to exist with v4.14 or v4.19 but
  for these kernels I'm not able to get the additional firmware
  images. i.e. 
(sudo apt install
  linux-firmware-image-`uname -r`)
fails. 

So I went back to v4.4


My var log messages shows this (excerpt, full messages
  attached)



  Dec 26 18:43:30
  beaglebone kernel: [    1.876960] of_cfs_init: OK
  Dec 26 18:43:30
  beaglebone kernel: [    1.882563]  remoteproc0: remote
  processor wkup_m3 is now up
  Dec 26 18:43:30
  beaglebone kernel: [    1.882629] wkup_m3_ipc
  44e11324.wkup_m3_ipc: CM3 Firmware Version = 0x193
  Dec 26 18:43:30
  beaglebone kernel: [    1.890647] Freeing unused kernel
  memory: 744K
  Dec 26 18:43:30
  beaglebone kernel: [    2.382866] random: systemd-udevd:
  uninitialized urandom read (16 bytes read, 2 bits of
  entropy ava
  
  Dec 26 18:43:30
  beaglebone kernel: [    2.409655] random: udevadm:
  uninitialize

Re: [Machinekit] Re: bone-debian-9.6-machinekit-armhf-2018-12-10-4gb.img machinekit not starting

2018-12-26 Thread schoone...@gmail.com


  
  
The other define I could not remember for getting your local machine
to do the work is
export LIBGL_ALWAYS_INDIRECT=1

but it is much easier to set up rendering on the remote machine as per previous


On 26/12/18 08:46, schoone...@gmail.com
  wrote:


  
  libGL error: No matching fbConfigs or visuals
found
  libGL error: failed to load driver: swrast
  
  The problem is still X forwarding, now specifically GL
  
  The axis GUI uses a libGL derivative opengl.
  Either your BBB or the accessing computer must provide that.
  
  You can get the forwarding to use the accessing computers
  libraries  using something like
  export LIBGL_ALWAYS_SOFTWARE=1
  but it is far easier to install the required libs on the remote
  computer.
  Since your BBB did not have an X server, it will not have had
  libgl installed
  
  apt-get update && apt-get install libgl1-mesa-dev libglu1-mesa-dev freeglut3-dev


  should pull all the required libs, try
  that, beyond that search engines are your friend, this is a common
  problem
  using remote access and nothing to do with machinekit
  
   
  On 26/12/18 07:51, Bas de Bruijn
wrote:
  
  



  
  



  On 25 Dec 2018, at 23:59, mugginsac <muggin...@gmail.com>

  wrote:
  


  

  So when I run "machinekit Xylotex.ini"  I see the
machinekit logo and then it displays the axis window
but immediately hides it (it is so fast that I can't
even tell if it is fully drawing the contents. The
axis window shows up in the XWindow windows list but
I can't get it to re-display. The console looks like
it is just waiting for the load process to finish
but the only thing I can do is ^C to abort.
  
  
  
  Here is a link to my console_output

  



Last 2 lines talk of an error. There’s your starting
  point.
Looks like your setup is finished and started to unload
  when you pressed CTRL+C


Bas


  

  Here is a link to my /var/log/linuxcnc.log

  (It is front trucated because it is too long for
  my console's scrollback).
  And here is a link to my dmesg_output

  

  

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

Re: [Machinekit] Re: bone-debian-9.6-machinekit-armhf-2018-12-10-4gb.img machinekit not starting

2018-12-26 Thread schoone...@gmail.com


  
  
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast

The problem is still X forwarding, now specifically GL

The axis GUI uses a libGL derivative opengl.
Either your BBB or the accessing computer must provide that.

You can get the forwarding to use the accessing computers libraries 
using something like
export LIBGL_ALWAYS_SOFTWARE=1
but it is far easier to install the required libs on the remote
computer.
Since your BBB did not have an X server, it will not have had libgl
installed

apt-get update && apt-get install libgl1-mesa-dev libglu1-mesa-dev freeglut3-dev


should pull all the required libs, try that,
beyond that search engines are your friend, this is a common problem
using remote access and nothing to do with machinekit

 
On 26/12/18 07:51, Bas de Bruijn wrote:


  
  
  


  
  
  
On 25 Dec 2018, at 23:59, mugginsac 
wrote:

  
  

  
So when I run "machinekit Xylotex.ini"  I see the
  machinekit logo and then it displays the axis window
  but
  immediately hides it (it is so fast that I can't even
  tell if it is fully drawing the contents. The axis
  window shows up in the XWindow windows list but I
  can't get it to re-display. The console looks like it
  is just waiting for the load process to finish but the
  only thing I can do is ^C to abort.



Here is a link to my console_output
  

  
  
  
  Last 2 lines talk of an error. There’s your starting
point.
  Looks like your setup is finished and started to unload
when you pressed CTRL+C
  
  
  Bas
  
  

  
Here is a link to my /var/log/linuxcnc.log
(It is front trucated because it is too long for my
console's scrollback).
And here is a link to my dmesg_output
  

  

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

Re: [Machinekit] Machinekit Advanced HAL Tutorial

2018-12-15 Thread schoone...@gmail.com


  
  
Also, params are deprecated and have been done away with in some
cases and eventually all.

They originate from a time when it was not possible to set pins to a
default value in code for components.
Therefore params were used and set after the component was
instantiated but before attaching it to a thread and starting it.

They are still retained in some components, so there is a bit of a
mix currently.

Pins can either be set and read, or just read depending upon the
requirement and type.

If you run these lines, you will see the component and a signal, but
you have to create it first

$ DEBUG=5 realtime restart
$ halcmd loadrt siggen
$ halcmd net mysig siggen.0.sawtooth
  $ halcmd show all
  $ halrun -U

Obviously you need to create a thread, attach siggen and start the
thread before you see any meaningful values in the pins or signal

regards

On 15/12/18 06:53, Bas de Bruijn wrote:


  
  Hi Scott,
  
On 15 Dec 2018, at 02:09, Scott Nortman 
wrote:

  
  

  Hi,


Just installed Machinekit to a rpi3b+ via apt-get and I
  am running through the tutorial here:


http://www.machinekit.io/docs/hal/tutorial/#introduction-a-id-sec-tutorial-intro-a



The strange issue:


When I instantiate the siggen component, all of the
  pins, signals, and parameters for the component appear as
  'Pins'.  For example, after instantiation, when I type



  halcmd: show pin
  Component Pins:
    Comp   Inst
  Type  Dir         Value  Name                         
                    Epsilon Flags  linked to:
      78       
  float IN              5  siggen.0.amplitude           
             0.10 --l-
      78       
  bit   OUT          TRUE  siggen.0.clock               
             --l-
      78       
  float OUT     0.8441676  siggen.0.cosine             
              0.10 --l-
      78       
  float IN              1  siggen.0.frequency           
             0.10 --l-
      78       
  float IN              0  siggen.0.offset             
              0.10 --l-
      78       
  float OUT          2.78  siggen.0.sawtooth           
              0.10 --l-
      78       
  float OUT     -4.922822  siggen.0.sine               
              0.10 --l-
      78       
  float OUT             5  siggen.0.square             
              0.10 --l-
      78       
  float OUT          0.56  siggen.0.triangle           
              0.10 --l-
      78       
  s32   OUT          5261  siggen.0.update.time         
             
      78       
  s32   I/O         65155  siggen.0.update.tmax         
             
      78       
  bit   OUT         FALSE  siggen.0.update.tmax-inc     
             
      66       
  s32   OUT        999411  test-thread.curr-period     
              
      66       
  s32   OUT          5261  test-thread.time             
             
      66       
  s32   I/O         65155  test-thread.tmax             
             
  

  halcmd: 


  
And when I attempt
to see the parameters, nothing shows up:

  

  halcmd:
  show param
  Parameters:
   Comp   
  Inst Type   Dir         Value  Name
  

  halcmd: 
  
  
  Also, when I
run the halmeter, all items show up under the 'Pins' tab
and no items show up under the Signals or Parameters tab
(see image)
  
  
  
  
  Any thoughts?

  

  
  
  
  This has to do with the fact that that component has no

Re: [Machinekit] Beaglebone stepper motor as spindle

2018-12-03 Thread schoone...@gmail.com

As Bas says they are not suitable for spindle motors, unless you have 
some sort of hybrid spindle requirement

that involves positional placement (indexing etc.)

You can use the step generator to drive a 'speed board' which controls a 
spindle.
Set the stepgen to velocity mode and the speed board converts the step 
frequency into an analogue

signal to drive the VFD or similar.

On 03/12/18 13:21, Bas de Bruijn wrote:



On 3 Dec 2018, at 13:44, Gediminas Dirma  wrote:

Hello

Has anyone tried setting up stepper motor as spindle with machinekit. Maybe you 
have some example configs or examples.

Thanks for help.

My guess is that a stepper motor is not suitable for a spindle. Mostly because 
speed is limited wrt other motor types.

Apart from that, if you set the stepper up in velocity mode instead of position 
mode, then that should work.

There are beaglebone configs in the repo which show how to set stepgens in 
velocity mode.



--
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] Machinekit with openpnp

2018-12-02 Thread schoone...@gmail.com

There is a single mention of linuxcnc, no details of any driver etc on 
the page you linked to.


The bottom line is that if you can control the pnp machine through 
gcode, you can use machinekit

in exactly the same way as you could use linuxcnc.

For some reason you don't want to go along the recommended and supported 
openpnp route of using a smoothie board,
I suspect the only reason you want to use machinekit is because you want 
to use a BBB.


They are not cheap, (twice the price of a chinese knock off 
smoothieboard)  are difficult to set up for a beginner
and you will be on your own getting it to work with pnp, unless someone 
else chimes in to say they are already doing it.


I would suggest you go onto the linuxcnc forum and try to get a working 
configuration from one of the people
using it for pick and place (there were some last I knew) as a starting 
point and worry about getting it to run satisfactorily on a PC first,
before buying hardware and then trying to engineer a solution to fit the 
hardware.



On 01/12/18 21:26, alaa momen wrote:

in openpnp wiki there is option to use linuxcnc as motioncontroller through 
talnet connection

https://github.com/openpnp/openpnp/wiki/Motion-Controllers



--
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] Machinekit with openpnp

2018-12-01 Thread schoone...@gmail.com




On 30/11/18 19:29, alaa momen wrote:

can I use openpnp project on beaglebone black
using linuxcnc sub driver !?

The BBB is just a hardware board, nothing to do with Machinekit.

The question is will this driver work with machinekit.

If you explain what this driver is and where it can be found, we might 
be able to answer

Is there is difference between machinekit and linuxcnc !!?


Yes in some respects, no in others.

--
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] Re: Debian package related problem

2018-11-29 Thread schoone...@gmail.com


  
  
OK, a one off Quick Guide to install on i386
It really is not difficult, so long as you have some idea what you
are trying to do.

Install Debian Stretch i386 net install distro from USB or CD

During installation:
Create root and user with same password (so you don't forget it)
Under software selections:
Select LXDE desktop and ssh server, remove print server

Near the end, install grub to MBR.

Reboot, login as normal user and open menu (Ctrl Esc) > System
> Root_Terminal
(# indicates the root command line prompt)

# apt update
(should be fully up to date if using net install)
# apt install firmware-linux-non-free firmware-realtek (if you have
a RTL NIC) dirmngr
#apt install linux-image-rt-686-pae

Reboot and sign in as your normal user

From root terminal (Ctrl Esc > System > Root_Terminal)
# uname -a
check you have booted the rt kernel

# apt-key adv --keyserver
hkp://keyserver.ubuntu.com:80 --recv 43DDF224

# echo 'deb http://deb.machinekit.io/debian
stretch main' >
/etc/apt/sources.list.d/machinekit.list

# apt update

# apt install machinekit machinekit-rt-preempt

# leafpad /etc/ssh/sshd.conf &
Then uncomment the line beginning '#AllowRootLogin' and edit so
it reads
' AllowRootLogin yes'
save file and close leafpad

# service sshd reload
Now you will be able to ssh into the machine with root permissions
for maintenance

Now close root terminal and (Ctrl Esc > System > LXDE_Terminal)
for user terminal
Alt Spacebar X - to maximise
# machinekit

Then you are running, select the axis sim to test.

>> Start controlling things like LinuxCNC never could.

I do have some concerns as to what you think you can do on an i386
with Machinekit, that you can't on linuxcnc.

You do realise that a rt-preempt kernel will probably not give good
enough latency to run from a parport?
You need a rtai kernel for that and Machinekit does not support rtai
any more.

The things it can control that linuxcnc can't, are largely based on
various armhf boards and soc_fpga boards etc. not PCs

regards



On 27/11/18 19:13,
  cncbuilder...@gmail.com wrote:


  


Thanks for the suggestions. I have no idea how to use them.


This what I thought was going to happen(a week ago).



Install debian stretch.
install Machinekit rt-reempt for stretch.
Start controlling things like LinuxCNC never could.


If you can show me how to get this going.
I'm sure others will find it help full. 

Maybe a step by step guide for Dummies.
 


I want this to work... 





On Tuesday, November 27, 2018 at 3:14:06 AM UTC-7, Schooner
wrote:

   This is nothing to do
with the initial problem reported by ce...@tuta.io

It is caused by your not setting up the system properly

You have a posix kernel running
Linux version 4.9.0-8-686-pae (debian...@lists.debian.org)
(gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1) ) #1
SMP Debian 4.9.130-2 (2018-10-27)

You have installed a rt-preempt kernel package
sudo dpkg -i machinekit_0.1.1543248182.gite5f547c-1~stretch_i386.deb

machinekit-rt-preempt_0.1.1543248182.gite5f547c-1~stretch_i386.deb

(BTW you don't need to use dpkg, the new packages are in the
repo, just need to do 'apt update' and they will be
available.)

As a result it tries to find the posix binaries and fails
Warning - /usr/libexec/linuxcnc/rtapi_app_posix
  not setuid
  
  (That error is a bit misleading, because the binary could
  not be opened it assumes things,
  does not consider that it might not exist!)
  
  So, as per the documentation
  http://www.machinekit.io/docs/getting-started/install-rt-kernel-i386/
  
  install a rt-preempt kernel and BOOT THAT.
  
  If you already have and are just letting the system boot
  unwatched, it is obviously defaulting to posix,
  so you need to manually select the rt kernel or change the
  boot order in /boot/grub/grub.cfg
  
  
  On 27/11/18 09:10, cncbui...@gmail.com
  wrote:


  


   New downl

Re: [Machinekit] Debian package related problem

2018-11-28 Thread schoone...@gmail.com


  
  
Hi Cern,

Now solved the error and new PR made.

Original removal of hard thread refs had inadvertently removed a
line which added
kernel LD_FLAGS in Makefile.inc.in

However rather than produce a build or packaging error, or even a
runtime error in amd64 or armhf, this only produced a runtime error
in i386.
Because very few people use it, was not notified for quite some
while until you updated.

Can only speculate that the amd64 and armhf builds have the linkages
satisfied consequentially through other linkages, but i386 does not
and failed on thread creation. 

Package built from this new PR branch tested on i386 as well as
local build on amd64 and all fine.

Thanks for the report and 'mucking in' and doing some debugging.
Made things much quicker knowing I needed to zero in on anything
related to threads

New final packages will be in the repo in due course.
In the interim the current packages work fine on i386 too.

regards

On 28/11/18 07:23, schoone...@gmail.com
  wrote:


  
  Thanks for looking at the coredump.  Debugging with real time
in Linux is certainly different to msvs!
  
  Possibly line:539, but thanks that is very helpfull
  
  My main spur to build a i386 machine was to be able to debug
the original commits, which I now can begin.
  The alternative to trying to debug the failure of the complete
set of merged commits, is to reintroduce them 
  
  one by one until it fails and narrow down what specifically
caused it. I think I will go that route, now that I can build
RIP
  builds and do that more easily (and now have an idea where the
fault is likely to occur)
  regards
  
  On 11/28/2018 1:38 AM, c...@tuta.io wrote:
  
  


  And am I understanding it correctly that it is dying on
line 384 of file src/rtapi/rt-preempt.c, right?
  
  
  Cern
  
  
  Dne středa 28. listopadu 2018 2:13:54 UTC+1 ce...@tuta.io napsal(a):
  

  Hello,
  
  
  OK, I am used to Visual Studio, so gdb (and others)
are interesting experience. Was able to experiment, that
problem is caused (minimally) by creating new thread
(halcmd newthread ...) and if I am not mistaken by call
to pthread_create(params).
  
  
  Commands from terminal:
  
  
  machinekit@machinekit:~$ DEBUG=5 realtime start
rtapi_msgd command:  /usr/libexec/linuxcnc/rtapi_msgd

--instance=0 --rtmsglevel=5 --usrmsglevel=5
--halsize=524288
warning: removing unused HAL shm segment
/linuxcnc-0-00414c32
rtapi_app command:  /usr/libexec/linuxcnc/rtapi_app_rt-preempt

--instance=0
machinekit@machinekit:~$ halcmd newthread fff 500 fp
:0: rc=-1: rtapi_rpc(): reply timeout

machinekit@machinekit:~$ pidof rtapi:0
24452
machinekit@machinekit:~$ sudo gdb -p 24452
[sudo] heslo pro machinekit: 
GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and
redistribute it.
There is NO WARRANTY, to the extent permitted by law. 
Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources
online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to
"word".
Attaching to process 24452
[New LWP 24456]
[New LWP 24457]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
0xb77afcf9 in __kernel_vsyscall ()
(gdb) c
Continuing.

Thread 1 "rtapi:0&

Re: [Machinekit] Debian package related problem

2018-11-27 Thread schoone...@gmail.com

Thanks for looking at the coredump.  Debugging with real time in Linux 
is certainly different to msvs!


Possibly line:539, but thanks that is very helpfull

My main spur to build a i386 machine was to be able to debug the 
original commits, which I now can begin.


The alternative to trying to debug the failure of the complete set of 
merged commits, is to reintroduce them


one by one until it fails and narrow down what specifically caused it. I 
think I will go that route, now that I can build RIP


builds and do that more easily (and now have an idea where the fault is 
likely to occur)


regards

On 11/28/2018 1:38 AM, c...@tuta.io wrote:
And am I understanding it correctly that it is dying on line 384 of 
file src/rtapi/rt-preempt.c, right?


Cern

Dne středa 28. listopadu 2018 2:13:54 UTC+1 ce...@tuta.io napsal(a):


Hello,

OK, I am used to Visual Studio, so gdb (and others) are
interesting experience. Was able to experiment, that problem is
caused (minimally) by creating new thread (halcmd newthread ...)
and if I am not mistaken by call to pthread_create(params).

Commands from terminal:

machinekit@machinekit:~$ DEBUG=5 realtime start
rtapi_msgd command:  /usr/libexec/linuxcnc/rtapi_msgd --instance=0
--rtmsglevel=5 --usrmsglevel=5 --halsize=524288
warning: removing unused HAL shm segment /linuxcnc-0-00414c32
rtapi_app command:  /usr/libexec/linuxcnc/rtapi_app_rt-preempt
--instance=0
machinekit@machinekit:~$ halcmd newthread fff 500 fp
:0: rc=-1: rtapi_rpc(): reply timeout

machinekit@machinekit:~$ pidof rtapi:0
24452
machinekit@machinekit:~$ sudo gdb -p 24452
[sudo] heslo pro machinekit:
GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show
copying"
and "show warranty" for details.
This GDB was configured as "i686-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
>.
Find the GDB manual and other documentation resources online at:
>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
Attaching to process 24452
[New LWP 24456]
[New LWP 24457]
[Thread debugging using libthread_db enabled]
Using host libthread_db library
"/lib/i386-linux-gnu/libthread_db.so.1".
0xb77afcf9 in __kernel_vsyscall ()
(gdb) c
Continuing.

Thread 1 "rtapi:0" received signal SIGSEGV, Segmentation fault.
0xb7366b18 in allocate_stack (stack=,
    pdp=, attr=0xbf9b1560) at allocatestack.c:414
414    allocatestack.c: Adresář nebo soubor neexistuje.
(gdb) backtrace
#0  0xb7366b18 in allocate_stack (stack=,
    pdp=, attr=0xbf9b1560) at allocatestack.c:414
#1  __pthread_create_2_1 (newthread=0xb69e302c, attr=0xbf9b1560,
    start_routine=0xb69d1978, arg=0xb69e03ec) at pthread_create.c:539
#2  0xb7367230 in __pthread_create_2_0 (newthread=0xb69e302c,
    attr=0xbf9b1560, start_routine=0xb69d1978, arg=0xb69e03ec)
    at pthread_create.c:765
#3  0xb69d1d53 in ?? () from /usr/lib/linuxcnc/rt-preempt/rtapi.so
#4  0xb69cf4f1 in ?? () from /usr/lib/linuxcnc/rt-preempt/rtapi.so
#5  0xb68c1416 in hal_create_xthread ()
   from /usr/lib/linuxcnc/rt-preempt/hal_lib.so
#6  0x0047af27 in ?? ()
#7  0xb730dd9c in zloop_start () from
/usr/lib/i386-linux-gnu/libczmq.so.4
#8  0x00479166 in ?? ()
#9  0x004720a5 in main ()
(gdb)

Nov 28 02:08:15 machinekit msgd:0: startup pid=24447
flavor=rt-preempt rtlevel=5 usrlevel=5 halsize=524288 shm=Posix
cc=gcc 6.3.0 20170516 version=v0.1~-~9c3423c
Nov 28 02:08:15 machinekit msgd:0: ØMQ=4.2.1 czmq=4.0.2
protobuf=3.0.0 atomics=gcc intrinsics libwebsockets=2.0.3
Nov 28 02:08:15 machinekit msgd:0: configured: sha=9c3423c
Nov 28 02:08:15 machinekit msgd:0: built:  Nov 14 2018
12:37:25 sha=9c3423c
Nov 28 02:08:15 machinekit msgd:0: register_stuff: actual hostname
as announced by avahi='machinekit.local'
Nov 28 02:08:15 machinekit msgd:0: zeroconf: registering: 'Log
service on machinekit.local pid 24447'
Nov 28 02:08:15 machinekit rtapi:0: 2:rtapi_app:24452:user
rtapi:0: cannot create core dumps - /proc/sys/fs/suid_dumpable
contains 0
Nov 28 02:08:15 machinekit rtapi:0: 2:rtapi_app:24452:user you
might have to run 'echo 1 > /proc/sys/fs/suid_dumpable' as root to
enable rtapi_app core dumps
Nov 28 02:08:15 machinekit rtapi:0:

Re: [Machinekit] Re: Debian package related problem

2018-11-27 Thread schoone...@gmail.com


  
  
I have now managed to put together a working P4 i386 computer
from old parts in my loft.

Installed from Debian Stretch i386 netinst and then installed
rt-preempt kernel and machinekit & machinekit-rt-preempt

Worked first time running the axis_mm sim.

The latest packages therefore work on i386

regards

On 26/11/18 17:35, schoone...@gmail.com
  wrote:


  
  There are now a new set of packages in the repo with the serial 
  0.1.1543248182.gite5f547c


  Please test on your i386 machines and confirm they
  work.
  
  
  On 26/11/18 16:16, schoone...@gmail.com
wrote:
  
  

I have now reverted a series of commits, which look to be the
cause.
(what exactly can build and package for all architectures
without errors,
but cause failure when running on i386 only, remains to be
seen!)

A local package build from this tests OK in the i386 VM, so
hopefully cured.

The repo is rebuilding packages and they will be available in a
couple of hours.

I will update when they are in the repo and can be pulled for
testing.

On 26/11/18 13:01, schoone...@gmail.com
  wrote:


  
  I have now created a Debian Stretch i386 VM and installed
  machinekit dependencies.
  
  It does not run properly because of other issues, but I can
  see that i386 packages
  start to fail at 0.1.1538832043git84c94e8-1-stretch
  
  For now just use packages prior to this
  
  To do this, for those not that familiar with linux
  
  Download 
  http://deb.machinekit.io/debian/pool/main/m/machinekit/machinekit_0.1.1538495763.git1d57feb-1~stretch_i386.deb
  or earlier
  and the corresponding flavour package, for instance 
  http://deb.machinekit.io/debian/pool/main/m/machinekit/machinekit-rt-preempt_0.1.1538495763.git1d57feb-1~stretch_i386.deb
  
  cd to the directory they were downloaded to.
  (instructions assume rt-preempt kernel)
  
  $ sudo apt remove machinekit machinekit-rt-preempt
  $ sudo dpkg -i
  machinekit_0.1.1538495763.git1d57feb-1~stretch_i386.deb
  machinekit-rt-preempt_0.1.1538495763.git1d57feb-1~stretch_i386.deb
  
  If there is a missing dependency error, 
  $ sudo apt install 
  then re-run the dpkg line
  
  I will update when the source of the problem is identified and
  fixed
  
  
  On 26/11/18 07:06, schoone...@gmail.com
wrote:
  
  



On 11/25/2018 11:43 PM, cncbuilder...@gmail.com
  wrote:


  
  

On Wednesday, November 21, 2018 at 5:59:07 PM UTC-7, ce...@tuta.io wrote:

  Hello,
isn't the newest Machinekit Debian package broken? I
upgraded my test system installation with apt-get
upgrade (Debian 9 Stretch: Linux machinekit
4.9.0-8-rt-686-pae #1 SMP PREEMPT RT Debian
4.9.130-2 (2018-10-27) i686 GNU/Linux) to the newest
package (0.1.1542196491.git9c3423c-1~stretch),
however trying to start machinekit with
sim.axis/axis.ini I got the error

  



   I'm having  the same issue.  same install on a
  P4 64bit 3.0Ghz  4G ram 

This system has been running Linuxcnc for more than
  4 years.
Also upgraded to 2.7 last summer. I have 4 machines
  in total running on P4s Linuxcnc.
  

There is no 2.7
Are you running linuxcnc or machinekit?




  


Can't find . 'machinekit_0.1.1537365199.
gitf63b8a2-1~stretch_i386' you
  suggested. 

  



It is in the repo, where you might expect it to be.
http://deb.machinekit.io/debian/pool/main/m/machinekit/machinekit_0.1.1537365199.gitf63b8a2-1~stretch_i386.deb


If you can help confirm definitely at which package
  version number this problem begins, we might be able to
  start tracking it down.
I don't have any i386

Re: [Machinekit] Re: Debian package related problem

2018-11-27 Thread schoone...@gmail.com


  
  
This is nothing to do with the initial problem reported by
c...@tuta.io

It is caused by your not setting up the system properly

You have a posix kernel running
Linux version 4.9.0-8-686-pae (debian-ker...@lists.debian.org) (gcc
version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP Debian
4.9.130-2 (2018-10-27)

You have installed a rt-preempt kernel package
sudo dpkg -i machinekit_0.1.1543248182.gite5f547c-1~stretch_i386.deb
machinekit-rt-preempt_0.1.1543248182.gite5f547c-1~stretch_i386.deb

(BTW you don't need to use dpkg, the new packages are in the repo,
just need to do 'apt update' and they will be available.)

As a result it tries to find the posix binaries and fails
Warning -
  /usr/libexec/linuxcnc/rtapi_app_posix not setuid
  
  (That error is a bit misleading, because the binary could not be
  opened it assumes things,
  does not consider that it might not exist!)
  
  So, as per the documentation
http://www.machinekit.io/docs/getting-started/install-rt-kernel-i386/
  
  install a rt-preempt kernel and BOOT THAT.
  
  If you already have and are just letting the system boot
  unwatched, it is obviously defaulting to posix,
  so you need to manually select the rt kernel or change the boot
  order in /boot/grub/grub.cfg
  
  
  On 27/11/18 09:10, cncbuilder...@gmail.com wrote:


  


   New download/install debian 9.6.0 machinekit failed to
  run.
See files attached. I will do the same for the amd64
  rt-reempt install.
If there is anything else you would like include let me
  know.
I will keep this P4 on the bench for testing. I hope you
  find this 

helpful.


On Monday, November 26, 2018 at 10:35:11 AM UTC-7, Schooner
wrote:

   There are now a new set
of packages in the repo with the serial 
0.1.1543248182.gite5f547c


Please test on your i386 machines and confirm
they work.


On 26/11/18 16:16, schoo...@gmail.com
  wrote:

 I have now reverted a series of
  commits, which look to be the cause.
  (what exactly can build and package for all architectures
  without errors,
  but cause failure when running on i386 only, remains to be
  seen!)
  
  A local package build from this tests OK in the i386 VM,
  so hopefully cured.
  
  The repo is rebuilding packages and they will be available
  in a couple of hours.
  
  I will update when they are in the repo and can be pulled
  for testing.
  
  On 26/11/18 13:01, schoo...@gmail.com
wrote:
  
   I have now created a Debian
Stretch i386 VM and installed machinekit dependencies.

It does not run properly because of other issues, but I
can see that i386 packages
start to fail at 0.1.1538832043git84c94e8-1-stretch

For now just use packages prior to this

To do this, for those not that familiar with linux

Download 
http://deb.machinekit.io/debian/pool/main/m/machinekit/machinekit_0.1.1538495763.git1d57feb-1~stretch_i386.deb
or earlier
and the corresponding flavour package, for instance 
http://deb.machinekit.io/debian/pool/main/m/machinekit/machinekit-rt-preempt_0.1.1538495763.git1d57feb-1~stretch_i386.deb

cd to the directory they were downloaded to.
(instructions assume rt-preempt kernel)

$ sudo apt remove machinekit machinekit-rt-preempt
$ sudo dpkg -i machinekit_0.1.1538495763.git1d57feb-1~stretch_i386.deb

machinekit-rt-preempt_0.1.1538495763.git1d57feb-1~stretch_i386.deb

If there is a missing dependency error, 
$ sudo apt install 
then re-run the dpkg line

I will update when the source of the problem is
identified and fixed


On 26/11/18 07:06, schoo...@gmail.com
  wrote:


  
  
  On 11/25/2018 11:43 PM, cncbui...@gmail.com
wrote:
  
  

  
  On Wednesday, November 21, 2018 at 5:59:07 P

Re: [Machinekit] Re: Debian package related problem


  
  
There are now a new set of packages in the repo with the serial 
0.1.1543248182.gite5f547c


Please test on your i386 machines and confirm they work.


On 26/11/18 16:16, schoone...@gmail.com
  wrote:


  
  I have now reverted a series of commits, which look to be the
  cause.
  (what exactly can build and package for all architectures without
  errors,
  but cause failure when running on i386 only, remains to be seen!)
  
  A local package build from this tests OK in the i386 VM, so
  hopefully cured.
  
  The repo is rebuilding packages and they will be available in a
  couple of hours.
  
  I will update when they are in the repo and can be pulled for
  testing.
  
  On 26/11/18 13:01, schoone...@gmail.com
wrote:
  
  

I have now created a Debian Stretch i386 VM and installed
machinekit dependencies.

It does not run properly because of other issues, but I can see
that i386 packages
start to fail at 0.1.1538832043git84c94e8-1-stretch

For now just use packages prior to this

To do this, for those not that familiar with linux

Download 
http://deb.machinekit.io/debian/pool/main/m/machinekit/machinekit_0.1.1538495763.git1d57feb-1~stretch_i386.deb
or earlier
and the corresponding flavour package, for instance 
http://deb.machinekit.io/debian/pool/main/m/machinekit/machinekit-rt-preempt_0.1.1538495763.git1d57feb-1~stretch_i386.deb

cd to the directory they were downloaded to.
(instructions assume rt-preempt kernel)

$ sudo apt remove machinekit machinekit-rt-preempt
$ sudo dpkg -i
machinekit_0.1.1538495763.git1d57feb-1~stretch_i386.deb
machinekit-rt-preempt_0.1.1538495763.git1d57feb-1~stretch_i386.deb

If there is a missing dependency error, 
$ sudo apt install 
then re-run the dpkg line

I will update when the source of the problem is identified and
fixed


On 26/11/18 07:06, schoone...@gmail.com
  wrote:


  
  
  
  On 11/25/2018 11:43 PM, cncbuilder...@gmail.com
wrote:
  
  


  
  On Wednesday, November 21, 2018 at 5:59:07 PM UTC-7, ce...@tuta.io wrote:
  
Hello,
  isn't the newest Machinekit Debian package broken? I
  upgraded my test system installation with apt-get
  upgrade (Debian 9 Stretch: Linux machinekit
  4.9.0-8-rt-686-pae #1 SMP PREEMPT RT Debian 4.9.130-2
  (2018-10-27) i686 GNU/Linux) to the newest package
  (0.1.1542196491.git9c3423c-1~stretch), however
  trying to start machinekit with sim.axis/axis.ini I
  got the error
  

  
  
  
     I'm having  the same issue.  same install on a P4
64bit 3.0Ghz  4G ram 
  
  This system has been running Linuxcnc for more than 4
years.
  Also upgraded to 2.7 last summer. I have 4 machines
in total running on P4s Linuxcnc.

  
  There is no 2.7
  Are you running linuxcnc or machinekit?
  
  
  
  

  
  
  Can't find . 'machinekit_0.1.1537365199.
  gitf63b8a2-1~stretch_i386' you
suggested. 
  

  
  
  
  It is in the repo, where you might expect it to be.
  http://deb.machinekit.io/debian/pool/main/m/machinekit/machinekit_0.1.1537365199.gitf63b8a2-1~stretch_i386.deb
  
  
  If you can help confirm definitely at which package version
number this problem begins, we might be able to start
tracking it down.
  I don't have any i386 computers any more and there is no
error on amd64.
  
  
  

  
  
  Is Machinekit for programmers only?
  
  
  Scott
  
  
  
  
  
  
  
   

-- 
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 unsubs

Re: [Machinekit] Re: Debian package related problem


  
  
I have now reverted a series of commits, which look to be the cause.
(what exactly can build and package for all architectures without
errors,
but cause failure when running on i386 only, remains to be seen!)

A local package build from this tests OK in the i386 VM, so
hopefully cured.

The repo is rebuilding packages and they will be available in a
couple of hours.

I will update when they are in the repo and can be pulled for
testing.

On 26/11/18 13:01, schoone...@gmail.com
  wrote:


  
  I have now created a Debian Stretch i386 VM and installed
  machinekit dependencies.
  
  It does not run properly because of other issues, but I can see
  that i386 packages
  start to fail at 0.1.1538832043git84c94e8-1-stretch
  
  For now just use packages prior to this
  
  To do this, for those not that familiar with linux
  
  Download 
  http://deb.machinekit.io/debian/pool/main/m/machinekit/machinekit_0.1.1538495763.git1d57feb-1~stretch_i386.deb
  or earlier
  and the corresponding flavour package, for instance 
  http://deb.machinekit.io/debian/pool/main/m/machinekit/machinekit-rt-preempt_0.1.1538495763.git1d57feb-1~stretch_i386.deb
  
  cd to the directory they were downloaded to.
  (instructions assume rt-preempt kernel)
  
  $ sudo apt remove machinekit machinekit-rt-preempt
  $ sudo dpkg -i
  machinekit_0.1.1538495763.git1d57feb-1~stretch_i386.deb
  machinekit-rt-preempt_0.1.1538495763.git1d57feb-1~stretch_i386.deb
  
  If there is a missing dependency error, 
  $ sudo apt install 
  then re-run the dpkg line
  
  I will update when the source of the problem is identified and
  fixed
  
  
  On 26/11/18 07:06, schoone...@gmail.com
wrote:
  
  



On 11/25/2018 11:43 PM, cncbuilder...@gmail.com
  wrote:


  
  

On Wednesday, November 21, 2018 at 5:59:07 PM UTC-7, ce...@tuta.io wrote:

  Hello,
isn't the newest Machinekit Debian package broken? I
upgraded my test system installation with apt-get
upgrade (Debian 9 Stretch: Linux machinekit
4.9.0-8-rt-686-pae #1 SMP PREEMPT RT Debian 4.9.130-2
(2018-10-27) i686 GNU/Linux) to the newest package
(0.1.1542196491.git9c3423c-1~stretch), however
trying to start machinekit with sim.axis/axis.ini I got
the error

  



   I'm having  the same issue.  same install on a P4
  64bit 3.0Ghz  4G ram 

This system has been running Linuxcnc for more than 4
  years.
Also upgraded to 2.7 last summer. I have 4 machines in
  total running on P4s Linuxcnc.
  

There is no 2.7
Are you running linuxcnc or machinekit?




  


Can't find . 'machinekit_0.1.1537365199.
gitf63b8a2-1~stretch_i386' you
  suggested. 

  



It is in the repo, where you might expect it to be.
http://deb.machinekit.io/debian/pool/main/m/machinekit/machinekit_0.1.1537365199.gitf63b8a2-1~stretch_i386.deb


If you can help confirm definitely at which package version
  number this problem begins, we might be able to start tracking
  it down.
I don't have any i386 computers any more and there is no
  error on amd64.



  


Is Machinekit for programmers only?


Scott







 
  
  -- 
  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 grou

Re: [Machinekit] Re: Debian package related problem


  
  

On 26/11/18 13:18,
  cncbuilder...@gmail.com wrote:


  


I started on Machinekit Nov 21 the day I found it. 

Used "Getting Started" on your website for installing.
Fresh downloads installs of debian stretch for every 

install of Machinekit using the terminal. 

Only Machinekit rt-reempt for stretch.
The systems have been both P4 64bit and two amd64 4core. 
On the P4 the linuxcnc.log and terminal output was the same
  as 

the one posted here. I will download and install again and
  attach
the files asap.
  

If it is the same - no need

  
On the amd64 4core I think the problem is that it's not
  using
re-reempt but posix. 
  

What problem, you haven't described one

Either you are running a rt-preempt kernel or you aren't.
'uname -a' will tell you what kernel is running, make sure you are
downloading packages
for that flavour kernel.


  
One post I read said to try flavor, in /usr

/libexec/linuxcnc to find out if re-reempt is installed,
  but all I 

get is command not found.Same result for 'sudo make
  setuid'.
  


Why would you run that command if you are downloading packages?


  
Because of this maybe the website install is not complete.
Tonight I did a fresh download/install of debian stretch
  and 

machinekit rt-reempt on an amd64 4core system with the 

same results as the other amd64 4core. 
  

Which is what?

There is no problem with amd64.
If your video card works with linuxcnc, it will work with
machinekit.

The reason we had no idea there was any problem is because
amd64 and armhf work fine.
Only when someone who uses i386 notified problems did it become
apparent.


  
I will run it again and 

attach the files. I also read that the video card drivers
  can 

effect Machinekit. Is it the drivers or the hardware? I
  booted 

the P4 on the Linuxcnc drive and ran it and moved around 

the axis and loaded/ran a large file with no problem. The
  P4 

has been running my plasma table for at least 4 years 

perfectly so it's solid.


I want this to work... need it... 











  



  

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

Re: [Machinekit] Re: Debian package related problem