Re: [Machinekit] Temporary override of limit switch

[Bas de Bruijn]

I’m mot sure if you can view the state of being “homed” in HAL. If so, you 
could change the HAL so that you’ll have an OR or and AND component (depending 
if the switch is normally open or normally closed) that kind of ignores the 
switch in the beginning.

Or you can solve it with a multiple contact relay if you wire it as a memory 
relay. The bottom switch is wired to one of the contacts, and the coil 
energized if you engage the upper switch. Then the second set of contacts keeps 
the coil energized even if the upper switch disconnects.


> On 11 Aug 2022, at 19:41, Alan Thomason  wrote:
> 
> Hello all...We have one axis that by gravity will always go the limit if the 
> unpowered state.  This is not a problem unless we lose power in the building. 
>  We can manually get the machine started by just holding it into position 
> when firing the machine up, but would prefer to be able to do this remotely.
> 
> For this to work we would need to be able to ignore the bottom limit switch 
> for a brief period of time on startup.  Is there a way to do this?  For 
> instance, you would have to be able to ignore the limit switch at first, 
> then, once homed, arm it again.
> 
> Thanks so much!
> -- 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/machinekit/c3ede903-e3f8-4d06-87b1-1ce7f6afdc3bn%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/CD562D1D-77C1-4E6E-8B98-7CB3B9FAC229%40basdebruijn.com.

RE: [Machinekit] Re: halcmd setp equivalent in python

[bas]

 

 

From: machinekit@googlegroups.com  On Behalf Of 
justin White
Sent: Tuesday, 19 May 2020 17:01
To: Machinekit 
Subject: Re: [Machinekit] Re: halcmd setp equivalent in python

 

 

Yeah, I forgot Machinekit is in a perpetual state of "this might work the way 
it used to".or "maybe not". I've recompiled components to swap parameters 
for pins but I don't think I'd try with a hm2 driver.

 

If all you want to do is set a parameter from an .ini line you don't have to do 
anything with Python whatsoever (unless there's some reason you really want 
to). All you need to do is:

 

In the .ini

 

[SPINDLE]

MAXRPM = 12000

 

In the hal file:

setp hm2_5i25.0.pwmgen.00.scale [SPINDLE]MAXRPM

 

That's the pretty standard usage, or am I missing something?

 

 

 

Yes, we were talking of doing this from python (see subject)

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/029401d62dee%24f3a12920%24dae37b60%24%40basdebruijn.com.

RE: [Machinekit] Re: halcmd setp equivalent in python

[bas]

Snip from a previous project (3 yrs ago) where I used configparser:

 

import Configparser

 

# taken out of a class somewhere, adapt as needed, the config will be loaded in 
self.cfg_hardware

# somewhere setup_ini() is called, which does the actual loading

# in the instance:

self.cfg_hardware = ConfigParser.ConfigParser()

 

def setup_ini(self):

self.read_hardware_config()

for key, (field, joint) in enumerate(self.joints.iteritems()):

for (key, val) in self.cfg_hardware.items(joint.name):

joint.add_hardware_setting(key, val) 

 

def read_hardware_config(self):

os.chdir(os.path.dirname(os.path.realpath(__file__)))

directory = os.getcwd() + '/config'

configfile = directory + '/hardware.ini'

self.cfg_hardware.read(configfile)

 

instead of the for loop for (key, val) in self.cfg_hardware.items(joint.name): 
you would get a value something like so: myval=cfg_hardware[‘SPINDLE’][‘MAXRPM’]

then use myval to set the pin

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/028301d62dee%2457a66f80%2406f34e80%24%40basdebruijn.com.

RE: [Machinekit] Re: halcmd setp equivalent in python

[bas]

Forgot to mention what has cost me a lot of time in the past.

IIRC then in python ‘import hal’ imports the ‘legacy’ LCNC python bindings.

If you use ‘from machinekit import hal’ then you use the Machinekit cython 
generated bindings.

If I’m not right about this I hope to get corrected.

 

From: machinekit@googlegroups.com  On Behalf Of 
b...@basdebruijn.com
Sent: Tuesday, 19 May 2020 09:51
To: 'Michael Brown' ; 'Machinekit' 

Subject: RE: [Machinekit] Re: halcmd setp equivalent in python

 

The Cython bindings do not support Params. I do not know about the original 
python bindings that came from the LCNC fork.

If you have a pin (not param), then you can set it with 
hal.Pin(‘pinname’).set(value)

If the params are needed in a python program, the best way would be to change 
the params to pins in the components source.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/017b01d62db2%24e85b6260%24b9122720%24%40basdebruijn.com.

RE: [Machinekit] Re: halcmd setp equivalent in python

[bas]

The Cython bindings do not support Params. I do not know about the original 
python bindings that came from the LCNC fork.

If you have a pin (not param), then you can set it with 
hal.Pin(‘pinname’).set(value)

If the params are needed in a python program, the best way would be to change 
the params to pins in the components source.

 

From: machinekit@googlegroups.com  On Behalf Of 
Michael Brown
Sent: Tuesday, 19 May 2020 02:38
To: Machinekit 
Subject: [Machinekit] Re: halcmd setp equivalent in python

 

Here are all the combinations I have tried with cossospoding error messages:

 

hal.Param('hm2_5i25.0.gpio.070.is_output').set(true)

AttributeError: 'module' object has no attribute 'Param'

 

hal.set_p("hm2_5i25.0.gpio.070.is_output","true")

AttributeError: 'module' object has no attribute 'set_p'

 

hal.setp("hm2_5i25.0.gpio.070.is_output","true")

AttributeError: 'module' object has no attribute 'setp'

 

hal.Setp("hm2_5i25.0.gpio.070.is_output","true")

AttributeError: 'module' object has no attribute 'Setp'

 

there are 2 python files:

'/home/mib/Developer/the-snowwhite_git/machinekit-hal/lib/python/hal.py' 

'/home/mib/Developer/the-snowwhite_git/machinekit-hal/src/hal/lib/hal.py' 

containing:

 

class Pin(_ItemWrap):

def __init__(self, item):

_ItemWrap.__init__(self, item)

if not item.is_pin():

raise TypeError("Must be constructed from pin object")

 

class Param(_ItemWrap):

def __init__(self, item):

_ItemWrap.__init__(self, item)

if item.is_pin():

raise TypeError("Must be constructed from param object")

 

However it seems like the python library used is in a different location:

 

hal.Pin('hm2_5i25.0.gpio.070.is_output').set(true)

  File "hal/cython/machinekit/hal_pin.pyx", line 23, in 
machinekit.hal._Pin.__cinit__ (hal/cython/machinekit/hal.c:5368)

  File "hal/cython/machinekit/hal_pin.pyx", line 29, in 
machinekit.hal._Pin.__cinit__ (hal/cython/machinekit/hal.c:4935)

 

???

 


On Sunday, May 17, 2020 at 10:09:47 PM UTC+2, justin White wrote:

import hal and:

 

hal.set_p("pinname","value")

 

set_p or "setp" should be universal between pins and parameters. hal.Pin is 
specifying the Pin class, but you are trying to set a parameter. hal.Param may 
also work in the same vein as your original attempt on a parameter.

On Sunday, May 17, 2020 at 2:31:13 PM UTC-4, Michael Brown wrote:

Is it possible to set module parameters directly in python based hal configs 
without using the shell ?

if I attempt doing:



hal.Pin('hm2_5i25.0.gpio.018.invert_output').set(true)

 

I get an error about missing pin.

 

So far below construct is all I can get to work:

 

os.system('halcmd setp hm2_5i25.0.gpio.018.invert_output true')

.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/013a01d62db2%2430924810%2491b6d830%24%40basdebruijn.com.

RE: [Machinekit] C instantiable components and hal_pru_generic

[bas]

That was pretty silly,
Here it is: 
https://github.com/machinekit/machinekit-hal/tree/master/src/hal/icomp-example

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/001601d61ef3%240ac4bc80%24204e3580%24%40basdebruijn.com.

RE: [Machinekit] C instantiable components and hal_pru_generic

[bas]

Hi John,

This is the best place I can find.

Bas

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/00d001d61eec%24773c6450%2465b52cf0%24%40basdebruijn.com.

Re: [Machinekit] Seeed to design and build Machinekit focused Cape for BeagleBone Black/AI

[Bas de Bruijn]

I would use a cape who can drive DC and BLDC motors with encoder feedback. and 
has room for 24V I/O thru screw terminals.

A motor such as these types (just an example, maybe different capes for 
different power ratings) which would make creating tools for industrial 
situations much, much easier. No need to buy a €250 driver per motor.

https://en.nanotec.com/products/2265-internal-rotor-motors/

Such a cape would need to have enough oomph to drive 24V relays, and connect 
24V limit or proximity switches.

Maybe max out on motor+encoder and have a complimentary cape use the rest for 
the io’s.

Having hardware that drives these motors would help enormously in just creating 
a working machine (I’m not looking for 3D printing or CNC myself, but for 
custom machines) It would help me to focus on creating a machine, and not have 
me connect a bare BB to an industrial driver.

Bas

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/C6CCB330-26AC-44BD-A75B-D399EB8E2CB2%40basdebruijn.com.

Re: [Machinekit] Re: DE10 Nano suggested development environment?

[Bas de Bruijn]

> On 26 Feb 2020, at 16:03, justin White  wrote:
> 
> My biggest issue is actually MK itself, it's too far behind linuxcnc in key 
> areas like joints+axis and since you mentioned mesa, well that's rather far 
> behind too. I wouldn't have a problem deploying mksocfpga if I didn't have a 
> problem deploying MK itself.

My personal interest is the HAL part of Machinekit. Over time people have 
focused on that part. The CNC stack is stale, and I personally do not give it 
much hope that it ever will be updated.
Best hope is that somebody will build LCNC with machinekit-hal. Have both of 
best worlds.

PR’s to Mesa drivers are always welcome.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/37D77E7F-2B25-4FFF-8572-AB0E62DB2107%40basdebruijn.com.

Re: [Machinekit] Re: DE10 Nano suggested development environment?

[Bas de Bruijn]

> On 26 Feb 2020, at 01:34, justin White  wrote:
> 
> Its amazing that mksocfpga doesn't get more interest/support, I dont think 
> people realize how powerful the idea is.

Do you mean the reconfigurability? If not, the Mesa FPGA is around already for 
a long time, and it is great that the FPGA runs on such a small platform too.

The reason I think it is not used very much is that for real use, in a 
production/manufacturing  environment, there is no hardware that one can “just 
buy and works”.

If I want to use this in a customer project, from an integrator point of view, 
my concerns are about longtime availability of the hardware. I do not want to 
buy components, solder etc. I just want to open the box, attach wires to 
terminals and configure the machine.

If something breaks or need to make another machine then I want to order the 
_exact_ same hardware, use the same code/version of the original and it should 
just work.

This holds for BBB’s too btw. For customers I only use pc’s with the Mesa 
cards. There are other considerations than just the cost price of the board. 
Development time, hardware availability and support far outweigh the cost of 
the board.

Just my 2 ct.



-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/2FAAD5EE-00AE-4884-974E-AF6041FA96F3%40basdebruijn.com.

Re: [Machinekit] Teknic motors and MachineKit

[Bas de Bruijn]

The google group fell off the reply.
For completeness done manually :)

> On 22 Feb 2020, at 17:44, Bas de Bruijn  wrote:
> 
> 
> 
> 
>>> On 22 Feb 2020, at 15:25, John Allwine  wrote:
>>> 
>> Hi Bas,
>> 
>> Thanks for your suggestion! I’ll definitely look into writing a custom 
>> component rather than a custom MachineKit build.
>> 
>> I’m afraid, though, that I don’t completely follow the rest of your 
>> suggestion. Could you please expand a little? I have used immediate mode 
>> before. Let’s say a user clicks a home button in the Axis GUI. How could I 
>> tie into that event to start the process? Alternatively, if I created my own 
>> button to trigger something in Hal, how would I trigger immediate homing? 
>> How would you recommend setting the position on the rising edge?
> 
> You might not have to do anything. I’m not an expert on the cnc stack.
> If you have wired the enable pin of the motor physically and in HAL to the 
> enable pin of the motion component, then pressing the home button in the GUI 
> should start homing. Thus moving towards the end of your guide/motor.
> Make sure you wire the smart pin to the home Hal pin.
> Would that not work out of the box?
> Does the special pin stay high after homing?
> 
>> 
>> I believe I have a good grasp on how Hal works, but my knowledge of the 
>> built in components is limited.
>> 
>> Thanks again for the help!
>> 
>> John Allwine
>> Owner of Allwine Designs
>> https://www.allwinedesigns.com
>> 
>>>> On Feb 22, 2020, at 1:04 AM, Bas de Bruijn  wrote:
>>>> 
>>> 
>>> 
>>> 
>>>>> On 21 Feb 2020, at 23:30, John Allwine  wrote:
>>>>> 
>>>> 
>>>> I'm looking into using Teknic SDSK servo motors with MachineKit. The SDSK 
>>>> models accept step and direction pulses like a stepper motor, so using 
>>>> hal_pru_generic's stepgen is straight forward. The major issue I see is 
>>>> attempting to use Teknic's precision homing routines, as it doesn't fit 
>>>> into MachineKit's limit switch routines. I'd really like to use their 
>>>> homing routine because it is accurate to less than 1/10,000 of an inch in 
>>>> my setup, which could be difficult to achieve using my own limit switch 
>>>> setup. It seems to me that in order to do so would require either a custom 
>>>> homing routine implemented in C++ (so a custom build of MachineKit). Any 
>>>> thoughts on this would be appreciated!
>>>> 
>>>> The Teknic motors have 3 control pins and 1 feedback pin:
>>>> 
>>>> Control Pins:
>>>> Enable - Used to enable/disable the motor and plays a part in initiating 
>>>> the precision homing (see below).
>>>> Step - Same as for a stepper motor
>>>> Direction - Same as for a stepper motor
>>>> 
>>>> Feedback - They refer to this as the HLFB (high level feedback) pin. Can 
>>>> be set to a number of different options, but the relevant one for homing 
>>>> would be ASG (all systems go) Position, which is high when the motor is in 
>>>> the commanded position, low while moving.
>>>> 
>>>> The precision homing sequence is initiated as follows:
>>>> 
>>>> 1) Put the motor into homing mode by toggling the enable pin on (if it's 
>>>> already on, then turn it off, then back on).
>>>> 2) Command the motor with step and direction to move the joint to a hard 
>>>> stop.
>>>> 3) The motor will detect the hard stop and stop accepting step pulses 
>>>> until it is commanded to go the opposite direction.
>>>> 4) After the hard stop is detected the motor will back off to a precise 
>>>> location a configured number of internal encoder counts away.
>>>> 5) After a configured number of milliseconds (default is 10), the HLFB pin 
>>>> asserts indicating that homing is complete.
>>>> 
>>>> The hard stop detection and precision homing is fantastic. After the first 
>>>> homing sequence, the motor will return to a very precise location as long 
>>>> as the hard stop stays within ~2mm. I can physically put a shim (less than 
>>>> 2mm thick) in front of the hard stop and it still goes to a precise 
>>>> location that properly ignores the shim (so wearing on the hard stop over 
>>>> time doesn't affect the precision of the homing sequence).
>>>> 
>>>> So, does anyone have recommendat

Re: [Machinekit] Teknic motors and MachineKit

[Bas de Bruijn]

> On 21 Feb 2020, at 23:30, John Allwine  wrote:
> 
> 
> I'm looking into using Teknic SDSK servo motors with MachineKit. The SDSK 
> models accept step and direction pulses like a stepper motor, so using 
> hal_pru_generic's stepgen is straight forward. The major issue I see is 
> attempting to use Teknic's precision homing routines, as it doesn't fit into 
> MachineKit's limit switch routines. I'd really like to use their homing 
> routine because it is accurate to less than 1/10,000 of an inch in my setup, 
> which could be difficult to achieve using my own limit switch setup. It seems 
> to me that in order to do so would require either a custom homing routine 
> implemented in C++ (so a custom build of MachineKit). Any thoughts on this 
> would be appreciated!
> 
> The Teknic motors have 3 control pins and 1 feedback pin:
> 
> Control Pins:
> Enable - Used to enable/disable the motor and plays a part in initiating the 
> precision homing (see below).
> Step - Same as for a stepper motor
> Direction - Same as for a stepper motor
> 
> Feedback - They refer to this as the HLFB (high level feedback) pin. Can be 
> set to a number of different options, but the relevant one for homing would 
> be ASG (all systems go) Position, which is high when the motor is in the 
> commanded position, low while moving.
> 
> The precision homing sequence is initiated as follows:
> 
> 1) Put the motor into homing mode by toggling the enable pin on (if it's 
> already on, then turn it off, then back on).
> 2) Command the motor with step and direction to move the joint to a hard stop.
> 3) The motor will detect the hard stop and stop accepting step pulses until 
> it is commanded to go the opposite direction.
> 4) After the hard stop is detected the motor will back off to a precise 
> location a configured number of internal encoder counts away.
> 5) After a configured number of milliseconds (default is 10), the HLFB pin 
> asserts indicating that homing is complete.
> 
> The hard stop detection and precision homing is fantastic. After the first 
> homing sequence, the motor will return to a very precise location as long as 
> the hard stop stays within ~2mm. I can physically put a shim (less than 2mm 
> thick) in front of the hard stop and it still goes to a precise location that 
> properly ignores the shim (so wearing on the hard stop over time doesn't 
> affect the precision of the homing sequence).
> 
> So, does anyone have recommendations for how to perform this sequence 
> properly in MachineKit? Preferably, I'd avoid needing a custom build of 
> MachineKit, but if it's required to make homing a simple click of a button 
> then I'll have to go that route.

Hi John,

So if I understand correctly your homing sequence is started on the rising edge 
of the enable pin.

Then you need to move to your chosen homing side.
Your homing is done when the special pin rises.

Maybe all parts are already there.
Have you tried configuring as ‘immediate’ homing? So rising special pin sets 
the position?
http://www.machinekit.io/docs/config/ini_homing/

Even if you decide you need a special component, you do not have to rebuild MK, 
just write the comp in C and install with instcomp.

http://www.machinekit.io/docs/hal/instcomp/

Best,
Bas


> -- 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/machinekit/6b01a405-251f-4633-af72-abbcd6c78ab0%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/1832BBF6-BE55-41AA-99E5-02DA6FD7ECCB%40basdebruijn.com.

Re: [Machinekit] Machinekit Buster missing dependency (Debian)?

[Bas de Bruijn]

> Any known workaround for this problem?

Try installing the package manually first. `sudo apt install 
`

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/46EDA613-AB52-4DE3-9C3C-5E780A14A64B%40basdebruijn.com.

Re: [Machinekit] Re: side-by-side install linuxcnc and machinekit

[Bas de Bruijn]

On 3 Dec 2019, at 20:44, markus  wrote:

>> I think that the best hope is that someday LCNC can be built on top
>> of Machinekit-HAL. I think chances of ports to Machinekit are
>> nonexistent. Maybe some developers can chime in.
>> 
> 
> Newbie here - what does that mean running LCNC on top of MK HAL ?

Machinekit-HAL is the HAL part without the CNC application. The Machinekit HAL 
differs a lot with the HAL from LinuxCNC. Multicore capabilities, 
instantiatiable components, remote capabilities and whatnot.
So Linuxcnc can potentially reuse Machinekit-HAL.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/E3CF6146-5D42-4E62-B88F-CE244D7BEA8C%40basdebruijn.com.

Re: [Machinekit] Re: side-by-side install linuxcnc and machinekit

[Bas de Bruijn]

> On 2 Dec 2019, at 22:26, sliptonic  wrote:
> 
> I've made some progress on my side-by-side configuration.  I can now 
> selectively start either LinuxCNC or Machinekit in a RIP.
> The linuxCNC config still isn't working since it's at version 2.9 which has 
> the JA branch merge and some part of the configuration is causing following 
> errors.   
> My present configuration not withstanding, the JA changes look really 
> interesting, especially for my Scara robot.What's the outlook for the JA 
> changes to be ported into machinekit?

I think that the best hope is that someday LCNC can be built on top of 
Machinekit-HAL. I think chances of ports to Machinekit are nonexistent.
Maybe some developers can chime in.

> My machinekit install will start and run locally on the mill with the 
> gmoccapy UI.  
> 
> When I try to start with mklauncher, mkwrapper and cetus, however, I get 
> results that I don't understand:  It starts without error on the mill 
> machine.  
> I launch the client on a remote machine and it instantly finds the mill 
> machine.  I browse for remote UI and select cetus.  
> Cetus launches with all controls greyed out for approximately 45 seconds.  
> Then the controls activate for a few seconds before greying out again.  This 
> continues indefinitely.
> 
> Instead of the machinekit client and cetus,  I tried connnecting with 
> mlampert's FreeCAD machinekit workbench and get similar behavior.  It seems 
> to find the mill machine immediately but takes a long time to 
> communicate anything with it.  If initiate homing, the homing sequence 
> actually starts about a minute later.
> 
> I'm not sure how to troubleshoot further so I'm looking for suggestions.

I have no in depth knowledge on the remote stuff so I hope someone with more 
knowledge can chime in. I’d start with Justin’s remark in setting the debug 
level to 5 and digging thu the linuxcnc log.

> 
> Mill machine is running Debian stretch with 4.9.0-11-rt-amd64  kernel.
> 
> 
> 
> 
> 
> 
>> On Saturday, November 23, 2019 at 12:42:48 PM UTC-6, sliptonic wrote:
>> I converted my mill back to linuxcnc a while back because of compatibility 
>> problems with gmoccapy.   
>> However, I'd like to experiment with mlampert's machinekit workbench in 
>> FreeCAD.
>> 
>> Is it possible to install both side-by-side?  (Debian stretch)
>> 
>> Any gotchas to be aware of?
>> 
>> 
> 
> -- 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/machinekit/c039685f-072f-41f3-9df3-af30a1348566%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/E132C861-13BA-442E-A061-4074465438BE%40basdebruijn.com.

Re: [Machinekit] side-by-side install linuxcnc and machinekit

[Bas de Bruijn]

> On 23 Nov 2019, at 19:42, sliptonic  wrote:
> 
> I converted my mill back to linuxcnc a while back because of compatibility 
> problems with gmoccapy.   
> However, I'd like to experiment with mlampert's machinekit workbench in 
> FreeCAD.
> 
> Is it possible to install both side-by-side?  (Debian stretch)
> 
> Any gotchas to be aware of?

As far as i’m aware of you can install both as a RIP (run in place) built from 
source.
Then running the rip-environment script from one of both allows you to use one 
of both

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/5F657F84-F64B-442A-8268-61055368C351%40basdebruijn.com.

Re: [Machinekit] Re: machinekit configuration crashes

[Bas de Bruijn]

> On 18 Nov 2019, at 15:15, Rolf  wrote:
> 
> Thanks for your help Bas 
> machinekit is now up and running

Glad you got it working.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/C8C65A3E-B84A-4A6B-B73A-9D616E9F9EB2%40basdebruijn.com.

Re: [Machinekit] FreeCAD integration

[Bas de Bruijn]

> On 16 Nov 2019, at 06:10, markus  wrote:
> 
> I don't know how many here use FreeCAD for their CAD and/or CAM work.
> In case you do or are planning to, I started writing a workbench which
> basically is a (simple) Machinekit UI embedded in FreeCAD.
> 
> It is far from complete but it has become quite useful to me.
> Everything I machine is practically a one off, and being able to
> directly push the job, setup/touch off the tool and execute the task
> from FreeCAD has streamlined my workflow. Most of all, I find seeing the
> live feedback of the tool in relation to the model and g-code extremely
> helpful.
> 
> Besides, it was/is a lot of fun to reverse engineer the different
> services and interact with them :)
> 
> In case you're interested, the workbench is on github:
> https://github.com/mlampert/Machinekit-Workbench
> 
> Comments and feedback are welcome.

Hi Markus,
Great project!
That looks like it took a lot of work.

Bas

> 
> Cheers,
> Markus
> 
> -- 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/machinekit/20191115211044.2a59bc57%40yolanda.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/F7A35774-6A89-4EC0-B32E-CBFD6B58568F%40basdebruijn.com.

RE: [Machinekit] Re: machinekit configuration crashes

[bas]

 > Bas 

> I ran the commandline sudo dd if=/dev/zero of=/dev/mmcblk1 count=1 seek=1 
> bs=128k .The good news is that  running config-pin P8.08 gpio no longer gives 
> an error, but now both of the beaglebone boards give the same error message 
> (the one from my previous post).
> the following is written in the log file:

> Nov 12 09:14:40 beaglebone rtapi:0: 1:rtapi_app:5910:user halg_xinitfv:199 
> HAL error: duplicate component name 'hal_lib'
> Nov 12 09:14:40 beaglebone rtapi:0: rtapi_app_main(hal_lib): -16 Device or 
> resource busy
> Nov 12 09:14:40 beaglebone rtapi:0: 1:rtapi_app:5910:user init_actions() 
> failed
> Nov 12 09:14:40 beaglebone msgd:0: rtapi_app exit detected - scheduled 
> shutdown
> Nov 12 09:14:41 beaglebone rtapi:0: 1:rtapi_app:5563:user hal_pru_generic: 
> cant find /usr/lib/linuxcnc/xenomai/pru_generic.bin in /home/machinekit or 
> /lib/firmware/pru/
> Nov 12 09:14:41 beaglebone rtapi:0: 1:rtapi_app:5563:user hpg: ERROR: failed 
> to initialize PRU
> Nov 12 09:14:41 beaglebone rtapi:0: rtapi_app_main(hal_pru_generic): -1 
> Operation not permitted
> Nov 12 09:14:41 beaglebone rtapi:0: 1:rtapi_app:5563:user 
> rtapi_app_main(hal_pru_generic): -1 Operation not permitted
> Nov 12 09:14:42 beaglebone msgd:0: msgd shutting down
> Nov 12 09:14:42 beaglebone rtapi:0: rtapi_msgd went away, exiting

> I attached the comet.hal file, as well as the logfile after I ran export 
> DEBUG=5

The 5th line in linuxcnc.log says exactly what’s happening.
You need to look at your INI file. Have a look at the line that says [PRUBIN]. 
Since you run a (probably) rt-preempt kernel the pru driver cannot find what 
it's looking for (xenomai). It should be like so: 
https://github.com/machinekit/machinekit/blob/master/configs/ARM/BeagleBone/CRAMPS/CRAMPS.ini#L5

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/00dc01d59951%2443e61310%24cbb23930%24%40basdebruijn.com.

Re: [Machinekit] Re: machinekit configuration crashes

[Bas de Bruijn]

> On 12 Nov 2019, at 09:32, Rolf  wrote:
> 
> Thanks for the response Bas
> 
> I tried running grep -c bone_capemgr.uboot_capemgr_enabled=1 /proc/cmdline as 
> you suggested, however this returned 0. 

Then you should probably disable the eMMC bootloader as per the instructions in 
previous mail and the links. Sudo dd if ... etcetera

> It might be worth mentioning that I have a second beaglebone black board and, 
> while none of them will run machinekit, the second one does not get the same 
> error message as the first even when I use the exact same image. it  instead 
> gives the following message:
> 
> MACHINEKIT - 0.1
> Machine configuration directory is 
> '/home/machinekit/machinekit/configs/ARM.BeagleBone.Probotix'
> Machine configuration file is 'Comet_Metric.ini'
> Starting Machinekit...
> rtapi_msgd command:  /usr/libexec/linuxcnc/rtapi_msgd --instance=0 
> --rtmsglevel=1 --usrmsglevel=1 --debug=1 --halsize=524288
> rtapi_app command:  /usr/libexec/linuxcnc/rtapi_app_rt-preempt --instance=0 
> --debug=1
> io started
> Unrecognized line skipped: POC FMS LEN DIAMCOMMENT
> halcmd loadusr io started
> Comet.hal:20: insmod failed, returned -1:
> rtapi_app_main(hal_pru_generic): -1 Operation not permitted

So what does Comet.hal line 20 say?
What does /var/log/linuxcnc.log say?

> Shutting down and cleaning up Machinekit...
> Cleanup done
> Machinekit terminated with an error.  For simple cases more information
> can be found in the following files:
> /home/machinekit/linuxcnc_debug.txt
> /home/machinekit/linuxcnc_print.txt
> 
> For other cases get more meaningfull information by restarting after
> export DEBUG=5
> 
> and look at the output of:
> /var/log/linuxcnc.log
> dmesg
> 
> When looking for errors, specifically look for libraries that fail to load
> by looking for lines with 'insmod failed' as per example below.
> 
> insmod failed, returned -1:
> do_load_cmd: dlopen: nonexistant-component.so: cannot open shared object file:
> No such file or directory
> 
> For getting help, please have a look here: 
> www.machinekit.io/docs/getting-help/
> 
> 
> does this mean there is something wrong with one of the boards?
> 
> -- 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/machinekit/1bce2ca3-764d-4808-883b-3da8956ad418%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/9D6B2869-6F3D-40A8-BAE1-59E3E0154351%40basdebruijn.com.

RE: [Machinekit] Re: machinekit configuration crashes

[bas]

Rolf,

 

I think that your board uses the bootloader on the EMMC, check with:

grep -c bone_capemgr.uboot_capemgr_enabled=1 /proc/cmdline

 

as per this comment and further 
https://github.com/machinekit/Machinekit-HAL/issues/17#issuecomment-324731662

(there’s some other link there too). Then disable the eMMC boot with:

 

sudo dd if=/dev/zero of=/dev/mmcblk1 count=1 seek=1 bs=128k

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/010b01d59596%249f36a810%24dda3f830%24%40basdebruijn.com.

Re: [Machinekit] Re: machinekit configuration crashes

[Bas de Bruijn]

Hi Rolf,
I’m no Beaglebone expert, but I guess that you setup.sh script is the cause of 
your crashes. Iirc there was s somewhat recent pr that fixed permissions on a 
setup.sh script for another board.
Please try to execute the setup.sh script to see if that gives you meaningful 
info on why it crashes.

> On 6 Nov 2019, at 14:16, Rolf  wrote:
> 
> btw: I got my machinekit image 
> from:https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#BBW.2FBBB_.28All_Revs.29_Machinekit,
>  however I also tried to just follow an installation guide 
> (https://machinekoder.com/machinekit-debian-stretch-beaglebone-black/), but 
> both gave me the same result.
> 
> 
> -- 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/machinekit/6ce223d9-f05e-4261-92e3-32c2762af965%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/E7C7AD15-8DEC-48AD-8DC2-D0D89BF12EC0%40basdebruijn.com.

Re: [Machinekit] Re: Problem trying to run with remote=1

[Bas de Bruijn]

> On 17 Oct 2019, at 21:35, auto-mation-assist <867g...@gmail.com> wrote:
> 
> I can try the 4.9 kernel. Right now I have 4.4.190 loaded.
> 
> What I have found is that whenever I enter anything into 'bind' in file 
> /etc/linuxcnc/machinekit.ini I get the errors listed below. If I just leave 
> it blank it runs machinekit with no gui just fine but does not appear to 
> output anything on a tcp connection.
> 
> halcmd: the rtapi:0 RT demon is not running - please investigate 
> /var/log/linuxcnc.log
> halcmd: the msgd:0 logger demon is not running - please investigate 
> /var/log/linuxcnc.log
> halcmd: cant connect to rtapi_app: -1 (uri= 
> uuid=3c6b50af-0fe2-4929-b0bf-0cd4b6b6c327): rtapi_rpc(): reply timeout
> 
> So my problem could be that the below is instructions are not clear to me an 
> that I don't know what to type in there yet. Im trying to bind to my network 
> card with address 10.10.20.2.
> 
> This is the part I'm having trouble with understanding of just what bind is 
> and how to make it happy. These feel that these instructions could be revised 
> to help by giving an example of what is expected and a links to the documents 
> mentioned. 
> 
> "# -- interface and protocol selection -
> #
> # binding zeroMQ sockets and mDNS announcements are conceptually separate,
> # but of course better add up.
> # the default is to bind on in6addr_any (ipv4 and mapped ipv6 on Linux).
> # see the zeromq docs - zmq_tcp(7) and the ZMQ_IPV6 option.
> #
> # The binding algorithm is as follows:
> #
> # Bind any addresses or interfaces in the BIND_IPV4 list (none if empty).
> # if a port number was explicitly specified above, use that port
> # else bind as ephemeral port, retrieve that assigned port number, and use
> # that port in subsequent bind operations."
> 
> So "Bind any addresses'
> 
> BIND_IPV4=10.10.20.2  would seem like it should be ok but its not according 
> to the errors.

I have no specific knowledge about what you should do.
The only thing is that when I used a remote GUI, I only built with the 
configure flag for the RT-PREEMPT kernel; - -with-rt-preempt
And change in machinekit.ini so that REMOTE=1
Never changed anything else.
I can’t help you with more info that this :(

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/38028A1B-14A2-464E-AC1B-A96F9BA97825%40basdebruijn.com.

Re: [Machinekit] Re: Problem trying to run with remote=1

[Bas de Bruijn]

> On 17 Oct 2019, at 05:44, auto-mation-assist <867g...@gmail.com> wrote:
> 
> I think that purge only works for a regular install and not a run as rip 
> configuration. I will always do a make clean before doing a make.  I have 
> done all the normal make requirements which includes the “sudo make setuid”.
> 
> I have tried everything I can think off right now including doing at least 
> five builds done with various options. All come out with the same result. The 
> builds themselves look good but I suspect that the linking to the kernel 
> flavor is the problem. I'm generating a updated kernel now (4.14.146-RT67) to 
> try. As a last resort I can build up a system on a unused computer from 
> scratch to eliminate the possibility of messing up my normal dvelopment 
> system to much.

I’d try installing a 4.9 RT kernel to see if it is indeed the kernel

What happens when you configure only with --with-rt-preempt

> My searched on the internet shows that there have been issues with the same 
> errors in the past by others along with discussions on flavors but I have not 
> run across a clear solution after many hours of searching.
> 
> 
> 
> 
> -- 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/machinekit/0eced7bf-38da-4b59-9817-2efbad66042b%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/A5525B3F-F6AF-4869-81A2-806A60F918C5%40basdebruijn.com.

Re: [Machinekit] Problem trying to run with remote=1

[Bas de Bruijn]

> On 16 Oct 2019, at 07:48, auto-mation-assist <867g...@gmail.com> wrote:
> 
> I had MachineKit running with remote=0 and contrlling my milling maching so I 
> know that my linux computer configuration is good. But I'm working on a 
> remote gui so cleaned out its prior install and started with a clean install 
> using the master zip file. I always run in a rip configuration.

Have you purged all machinekit packages first and executed the “sudo make 
setuid” step last?

> 
> As far as I have been able to determine the problem is related to 
> /libexec/rtapi_msgd and /libexec/rtapi_app_rt-preempt. Possibly the reported 
> installed location.
> 
> It always gives these erros when starting up:
> halcmd: the rtapi:0 RT demon is not running - please investigate 
> /var/log/linuxcnc.log
> halcmd: the msgd:0 logger demon is not running - please investigate 
> /var/log/linuxcnc.log
> E: 19-10-15 20:38:37 [21476]dangling 'DEALER' socket created at 
> hal/utils/halcmd_rtapiapp.cc:284
> cnc@cnc1:~/machinekit-dev$ 
> 
> The log does not give me anymore clues but the number of dots in the first 
> part of file location in the below tests concern me.
> 
> Here is some information on my system and tests that I have completed.
> 
> My uses Linux 19.1 Mint
> cnc@cnc1:~/Desktop$ uname -a
> Linux cnc1 4.14.93-rt53 #1 SMP PREEMPT RT Tue Jan 29 01:00:10 AKST 2019 
> x86_64 x86_64 x86_64 GNU/Linux
> 
> I used this config for the compile:
> ./configure --enable-remote  --with-rt-preempt --enable-drivers 
> --enable-build-documentation
> 
> DEBUG=5 realtime start
> halcmd -f -k
> 
> The above gave:
> cnc@cnc1:~/machinekit-dev$ DEBUG=5 realtime start
> realtime: command not found
> cnc@cnc1:~/machinekit-dev$ . ./scripts/rip-environment
> cnc@cnc1:~/machinekit-dev$ DEBUG=5 realtime start
> rtapi_msgd command:  /home/cnc/machinekit-dev/libexec/rtapi_msgd --instance=0 
> --rtmsglevel=5 --usrmsglevel=5 --debug=5 --halsize=524288
> rtapi_app command:  /home/cnc/machinekit-dev/libexec/rtapi_app_rt-preempt 
> --instance=0 --debug=5
> E: 19-10-15 20:38:32 [21470]dangling 'XPUB' socket created at 
> rtapi/rtapi_msgd.cc:1107
> halcmd: cant connect to rtapi_app: -1 (uri= 
> uuid=cf144c6b-b001-4b4f-a57c-92479003f70d): rtapi_rpc(): reply timeout
> 
> halcmd: the rtapi:0 RT demon is not running - please investigate 
> /var/log/linuxcnc.log
> halcmd: the msgd:0 logger demon is not running - please investigate 
> /var/log/linuxcnc.log
> E: 19-10-15 20:38:37 [21476]dangling 'DEALER' socket created at 
> hal/utils/halcmd_rtapiapp.cc:284
> cnc@cnc1:~/machinekit-dev$ 
> 
> -
> rtapi_msgd indicates its owner is cnc
> If I use: gdb ../libexec/rtapi_msgd
> ../libexec/rtapi_msgd: No such file or directory.
> 
> If I use: gdb ./libexec/rtapi_msgd
> cnc@cnc1:~/machinekit-dev$ gdb ./libexec/rtapi_msgd
> GNU gdb (Ubuntu 8.1-0ubuntu3.1) 8.1.0.20180409-git
> Copyright (C) 2018 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 "x86_64-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"...
> Reading symbols from ./libexec/rtapi_msgd...done.
> (gdb) 
> 
> Then followed up with: r --foreground --stderr
> Starting program: /home/cnc/machinekit-dev/libexec/rtapi_msgd --foreground 
> --stderr
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> warning: removing unused global shm segment /linuxcnc-0-00154711
> [Inferior 1 (process 22034) exited with code 01]
> (gdb) 
> 
> --
> rtapi_app_rt-preempt indicates its owner is root with cnc read-only and then 
> none.
> gdb ../libexec/rtapi_app_rt-preempt
> This gave me:
> 
> gdb ../libexec/rtapi_app_rt-preempt
> cnc@cnc1:~/machinekit-dev$ gdb ../libexec/rtapi_app_rt-preempt
> GNU gdb (Ubuntu 8.1-0ubuntu3.1) 8.1.0.20180409-git
> Copyright (C) 2018 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 "x86_64-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".
> 

RE: [Machinekit] Beaglebone AI

[bas]

Hi Len,

 

I have dabbled a bit, but installing a RT kernel from stock gave me some 
problems ( 
https://groups.google.com/forum/#!category-topic/beagleboard/FOEDBLvmu2c ) and 
I have not gotten around trying to figure out what is happening.

 

I had MK running on the X15 approx a yr ago, so I guess that the BB AI will 
work at the end too.

 

Bas.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/007301d57831%24b52e03c0%241f8a0b40%24%40basdebruijn.com.

Re: [Machinekit] Re: Rotary CNC + Bamboo + BBB + CRAMPS?

[Bas de Bruijn]

> On 28 Sep 2019, at 16:30, jonas hauptman  wrote:
> 
> HI,
> 
> We are curious has anyone experimented with using the BB AI with Machinekit 
> yet? 

I have tried updating to a realtime kernel, but that does not work out of the 
box as of yet. I ran MK on an X15 so I guess there should be no big problems.

> Either way, I was wondering if one was planning to do other operation such as 
> in-browser 3d modeling (onshape, fusion360 or rhinoceros 7) as well as part 
> scanning real-time whether it is yet a good time to try to transition over. 

I would not do that from a beaglebone. But I guess you could if you wanted to.

What do you mean with “part scanning real-time”?

> Our project in general /  non-machining parts level working well.  Charles 
> thanks so much for your help!  But now we're about to size things up for 
> longer axis of movement and more toque so along with moving to all larger 
> NEMA 23 motors we are interested in considering BB AI.   

Why the BB AI? What holds you back in the BBB?

Bas

> Especially if it is a drop-in replacement and still works with the CRAMPS 
> Board and Configuration or if there is a new CRAMPS board that will be paired 
> with it?  Anyway, if anyone has thoughts or insights we are interested to 
> hear them.  Our goal continues to be to develop a sub $1000 (hopefully less) 
> open-source 4 axis CNC for rotary machining bamboo pole stock. To help others 
> to produce precice products and building system components, to democratize 
> high craft for a highly sustainable material system.
> 
> Best regards,
> 
> Jonas Hauptman
> Virginia Tech
> 
> 
> 
> 
> 
>> On Thursday, February 21, 2019 at 10:31:53 PM UTC-5, jonas hauptman wrote:
>> Hi,
>> 
>> We are new to your group and to machine kit but hoping the community might 
>> have some feedback for us.  We are trying to develop a Rotary 4 axis CNC 
>> router to machine bamboo poles into precise joints.  We believe this will 
>> require six motors and also a scanning function as bamboo poles are highly 
>> irregular in size, shape, and straightness.  Our project goal is to 
>> democratize CNC rotary machining with a low-cost high-performance machine 
>> for bamboo.   A material that has a huge environmental and mechanical upside 
>> for both the developed and developing world.  Presently it is difficult to 
>> use it in a high precision fashion and we hope to change that.  Initially, 
>> we planned to use a 3d printer Arduino boards and Marlin to control the 
>> machine but eventually realized we would have trouble independently 
>> controlling six motors and true 4 axis machining.  We have a little 
>> experience with LinuxCNC, I built a CNC Router Parts kit and outfitted it 
>> with a custom electronics bundle that Len from Probotix was kind enough to 
>> create for me around there standard control system (Unity). I am a huge fan 
>> of the Probotix machines and controls but we are trying to develop a machine 
>> that in total costs around $500 to build including computer, scanning 
>> camera, touch display, completely mechanical, electrical and CNC system.  
>> Our earlier prototypes used some open source components designs and still 
>> share some common strategies with the Sienci Mill One Kit V3.  Realizing 
>> that the cost of a full computer and control system even on Linux was too 
>> expensive and that Arduino with GRBL lack the horsepower and software 
>> features we need we are trying to develop our strategy and prototypes around 
>> the Beaglebone with a Cramps Cape.
>> 
>> I am posting hoping to begin to build a community around our project and 
>> looking for insights of any kind especially around our need of a control 
>> system for 4 axis and that can support our scanning needs.  I have attached 
>> a series of schematic and photographic summaries of our progress and look 
>> forward to input from the community.  
>> 
>> Best regards,
>> 
>> Jonas Hauptman
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
> 
> -- 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/machinekit/b70d605d-fbbc-4a2b-9bb1-73b136f0723e%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/48CB3EA5-5514-4830-BB1F-CBA2D5BE166D%40basdebruijn.com.

Re: [Machinekit] Weird idea?

[Bas de Bruijn]

us, what is the state of machinetalk? 
>> >> 
>> >> I am at some point planning on running a remote GUI, pretty much as you 
>> >> described with a de10 nano as the RT pc/FPGA and some ARM or small X86 
>> >> running the interface. I didn’t get too far in depth of what I need to do 
>> >> with remotely controlling it, too busy with hardware but I thought the 
>> >> remote concept of machinekit was solid. 
>> >> 
>> > This is only my view at the situation and as such there is going to be a 
>> > difference of opinions. Mainly what Machinetalk is and what it should do. 
>> > 
>> > The Machinetalk and HALtalk is a joint baby of Michael Haberler and 
>> > Alexander Rössler (for whom I think it was a diploma work). By post-mortem 
>> > investigation, there were a quite big plans for what Machinetalk should be 
>> > able to do. It was intended as a replacement of the NML and also shift 
>> > from current position, when NML sits on top of (for example) motion 
>> > component, nearer the HALayer core. That way it would enable node 
>> > structure of machine system setup. (As a example, imagine two RTAPI 
>> > instances (msgd and rtapi_app daemons) running infinite real-time loop 
>> > tasks like now, but getting the instruction from one separate planner, 
>> > which it itself is controlled from numerous terminals [GUIs].) Instances 
>> > of Machinekit should be also able to communicate with each other, not only 
>> > with current clien-server. As there was intention for direct control of 
>> > rtapi_app created HAL. 
>> > 
>> > But then Michael Haberler performed his exit stage left without finishing 
>> > his work (he even wanted to write documentation) and Alexander Rössler was 
>> > always (and by his online activity still is) interested more in GUI and 
>> > HMI work and replacing AXIS with something remote/running on 
>> > Android/written in modern language. 
>> > 
>> > So, the current situation is that the Machinetalk (and affiliated 
>> > technologies) is deeply ingrained into Machinekit, but not deeply enough 
>> > as too much LinuxCNC ways is still visible. And then it's development 
>> > stalled. And that is the root of my frustration. 
>> > 
>> > So, to @Bas, if you want to use only the UI components, you are fine as it 
>> > works. (But is still only a clutch, as the messages are translated to NML 
>> > to communicate with Machinekit-CNC side.) However, look for example at the 
>> > NOTYET portion of code in rtapi_app and then how HALCMD communicates with  
>> > rtapi_app. It uses the Machinetalk. But then not. It uses the ZeroMQ layer 
>> > and Protobuf serialization. And then it registers itself as a HAL module, 
>> > which I consider a braindead move (OK, I get it why it does that, but it's 
>> > bad architectural design and means that the process needs to run on the 
>> > same system as a rtapi_app). Saner approach would be to enforce the 
>> > rtapi_app only place where access to the HAL shared memory space happen. 
>> > CMDLINE would message rtapi_app socket with command, rtapi_app would 
>> > execute it and send back a status. That way you can milk the great feature 
>> > of ZeroMQ and use HALCMD from everywhere, even Windows Machines. (Typical 
>> > machine programmer monkey cannot use Linux.) 
>> > 
>> > I think the best approach would be to implement what I described here: 
>> > https://github.com/machinekit/machinekit-hal/issues/230 
>> > <https://github.com/machinekit/machinekit-hal/issues/230> with Linux based 
>> > permissions on file access, onto this connect new process which would do 
>> > the Machitalk access (machinetalk_app), which would do all what is done 
>> > now plus manage permissions (which current implementation of Machinetalk 
>> > does not even take into account) based on certificates, protocols and 
>> > interfaces (you can have an interface you consider implicitly safe which 
>> > is direct connection to other parts of the machine and then another which 
>> > is LAN) onto which would be connected the HALCMD and other similar 
>> > applications or remote/nonRT connected rtapi_app (Machinekit-HAL) 
>> > instances. But, as I said, it is only my opinion. 
>> > 
>> > Also, part of Machinekit is the router message pipe (currently not used, I 
>> > think) which is intended for direct messaging between two HAL modules. 
>> > Imagine module which has a ring buffer. This ri

Re: [Machinekit] Weird idea?

[Bas de Bruijn]

> On 19 Sep 2019, at 17:50,   wrote:
> 
> Sep 18, 2019, 20:19 by blazin...@gmail.com:
> 
>> @cern
>> 
>> Curious, what is the state of machinetalk? 
>> 
>> I am at some point planning on running a remote GUI, pretty much as you 
>> described with a de10 nano as the RT pc/FPGA and some ARM or small X86 
>> running the interface. I didn’t get too far in depth of what I need to do 
>> with remotely controlling it, too busy with hardware but I thought the 
>> remote concept of machinekit was solid.
>> 
> This is only my view at the situation and as such there is going to be a 
> difference of opinions. Mainly what Machinetalk is and what it should do.
> 
> The Machinetalk and HALtalk is a joint baby of Michael Haberler and Alexander 
> Rössler (for whom I think it was a diploma work). By post-mortem 
> investigation, there were a quite big plans for what Machinetalk should be 
> able to do. It was intended as a replacement of the NML and also shift from 
> current position, when NML sits on top of (for example) motion component, 
> nearer the HALayer core. That way it would enable node structure of machine 
> system setup. (As a example, imagine two RTAPI instances (msgd and rtapi_app 
> daemons) running infinite real-time loop tasks like now, but getting the 
> instruction from one separate planner, which it itself is controlled from 
> numerous terminals [GUIs].) Instances of Machinekit should be also able to 
> communicate with each other, not only with current clien-server. As there was 
> intention for direct control of rtapi_app created HAL.
> 
> But then Michael Haberler performed his exit stage left without finishing his 
> work (he even wanted to write documentation) and Alexander Rössler was always 
> (and by his online activity still is) interested more in GUI and HMI work and 
> replacing AXIS with something remote/running on Android/written in modern 
> language.
> 
> So, the current situation is that the Machinetalk (and affiliated 
> technologies) is deeply ingrained into Machinekit, but not deeply enough as 
> too much LinuxCNC ways is still visible. And then it's development stalled. 
> And that is the root of my frustration.
> 
> So, to @Bas, if you want to use only the UI components, you are fine as it 
> works. (But is still only a clutch, as the messages are translated to NML to 
> communicate with Machinekit-CNC side.)

I’m afraid you misunderstand. I do not use the CNC stuff. Just the HAL layer. 
Pins, No NML.

The entire “let’s replace nml” has halted because 1: this is hard work and 2: 
it is a lot of work and 3: there’s nobody who wants to do that.

> However, look for example at the NOTYET portion of code in rtapi_app and then 
> how HALCMD communicates with  rtapi_app. It uses the Machinetalk. But then 
> not. It uses the ZeroMQ layer and Protobuf serialization. And then it 
> registers itself as a HAL module, which I consider a braindead move (OK, I 
> get it why it does that, but it's bad architectural design and means that the 
> process needs to run on the same system as a rtapi_app). Saner approach would 
> be to enforce the rtapi_app only place where access to the HAL shared memory 
> space happen. CMDLINE would message rtapi_app socket with command, rtapi_app 
> would execute it and send back a status. That way you can milk the great 
> feature of ZeroMQ and use HALCMD from everywhere, even Windows Machines. 
> (Typical machine programmer monkey cannot use Linux.)
> 
> I think the best approach would be to implement what I described here: 
> https://github.com/machinekit/machinekit-hal/issues/230 
> <https://github.com/machinekit/machinekit-hal/issues/230> with Linux based 
> permissions on file access, onto this connect new process which would do the 
> Machitalk access (machinetalk_app), which would do all what is done now plus 
> manage permissions (which current implementation of Machinetalk does not even 
> take into account) based on certificates, protocols and interfaces (you can 
> have an interface you consider implicitly safe which is direct connection to 
> other parts of the machine and then another which is LAN) onto which would be 
> connected the HALCMD and other similar applications or remote/nonRT connected 
> rtapi_app (Machinekit-HAL) instances. But, as I said, it is only my opinion.
> 
> Also, part of Machinekit is the router message pipe (currently not used, I 
> think) which is intended for direct messaging between two HAL modules. 
> Imagine module which has a ring buffer. This ring buffer is filled from one 
> side by (for example) RT HAL module, then on other end emptied  by this 
> router, send over ZeroMQ to other machine and there the dealer puts this 
> message back into receiving ring buff

Re: [Machinekit] Weird idea?

[Bas de Bruijn]

> On 18 Sep 2019, at 19:34,   wrote:
> 
> Sep 18, 2019, 16:26 by berk...@gmail.com:
> 
>> Thank you Justin and Bas for quick response.
>> 
>> I know about Mesa cards, but it takes too long to have it in my country. 
>> Legal procedures etc. or I need to spend a lot for quick cargo and custom 
>> taxes.. Besides I have two analog and one digital servo motor and drive thus 
>> I need at least two Mesa daughter card and one anything card like the one 
>> for pi or pcie etc. Which is very confusing for me.  So I am trying to find 
>> a solution for that. I am good at python programming and I know that using 
>> NML with machinekit is possible to control motors. I already have a pi3b+ 
>> and a pc :) so I just wanted to know if it's a good idea to spend some time 
>> on it or not.
>> 
>> I have no idea about pic programming nor electronics so I wanted to do 
>> something with what I already have.
>> 
>> About step frequency I have tested linuxcnc with parallel port and I have 
>> got 1500 mm/min speed rate if just two axis runs at the same time. I do 
>> relief machining a lot and when z axis runs with X and y, speed drastically 
>> reduce to 600 mm/min. This is because of the latency issues. Not to have 
>> latency issues I thought it would be good idea if I seperate the GUI and the 
>> step generator.
>> 
>> Since forums is here for brainstorming I just got the idea and shared with 
>> you to learn if it's a good idea or not.
>> 
>> Thank you again for your interest.
>> 
>> Berkdan
>> 
> Hello,
> I can feel your pain. The distribution part of Mesa business is very bad. It 
> is a little bit better that it was but still they could learn a lot from 
> Chinese sellers.
> 
> However, Raspberry Pi with default GPIO configuration for step-gen is not 
> good solution. I have heard some interesting news about the GPIO toggling on 
> Raspberry Pi: https://evlproject.org/pipermail/evl/2019-May/19.html 
> <https://evlproject.org/pipermail/evl/2019-May/19.html> but fo far I 
> didn't play with it.
> 
> About distributed system, to have proper distinction between RT tasks 
> specific hardware and non-RT tasks specific hardware is the way forward, I 
> think. It is clutch from LinuxCNC days to have everything on one PC, from 
> times when electronics, PCs and whatnots were very expensive. Today, there is 
> no need to not have one physical system running the RT kernel and tasks and 
> other taking care of the planning and another taking care of UI. Video frame 
> buffer will always cause unnecessary latencies on RT systems.
> 
> However, Machinetalk in the current form is not going to take us there. 
> Unfortunately.

I’ve used remote UI’s with HAL remote components for a few projects, I was 
happy using the UI on an Android device, while machinekit ran on a PC with mesa 
hardware. What’s wrong with Machinetalk?

> 
> If you want Raspberry Pi with something like Mesa FPGA firmware, try the 
> BeagleBone Black.
> 
> And, if you are up to challenge, you can try to implement simple core on some 
> $10 FPGA developer board from Alibaba. The HostMot2 is nice, but it is 
> universal and so overcomplicated. Look for example at the Pluto code or 
> internet tutorials. Or the LAN9252 + ARM or XMC4800 for Mesa card DYI 
> alternatives.
> 
> Cern.
> 
> -- 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/machinekit/Lp4RDSK--3-1%40tuta.io.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/33BCF627-6E22-4546-9146-C548016DD420%40basdebruijn.com.

Re: [Machinekit] Weird idea?

[Bas de Bruijn]

Hi Berkdan,

Failing to understand why you need what you think you need...

IMO a better setup would be a PC with a mesanet PCI card. This is in fact a 
FPGA. Perhaps you could do a thing like you propose, but i think this is a 
setup involving a lot of components where i fail to see the merit.

What does the machine need to do, why do you need a 500 kHz step rate? I wonder 
which driver/motor would be able to handle that.

You can run Machinekit directly on a raspberry pi, or a beaglebone for that 
matter.

Bas

> On 18 Sep 2019, at 15:05, Berkdan Kara  wrote:
> 
> Hi All.
> 
> I have an idea but it may sound weird at the first place. Since I am not a 
> tech guy I don't know if it's stupid or not, could you please criticize the 
> idea.
> 
> 
> I would like to use raspberry pi3 with machinekit. This is not the weird? 
> idea. 
> 
> The idea; can pi be used as an FPGA?
> 
> I want to use a laptop or PC as the main machine with machinekit and want to 
> connect raspberry pi with ethernet or spi or something else. Raspberry pi 
> will be machinekit installed as well without any gui. What I would like to do 
> is: the main computer will send the commands to the pi as if it is a FPGA 
> board (or not) then pi will get the command and execute it( generate steps 
> follow the error messages from NML etc.) Then will send feedback to main 
> machinekit computer.
> 
> You could think that why pi is needed between computer and step drivers. I 
> did some resourcing and find out with parallel port computers can generate 25 
> khz steps. With the GUI it's about the same for pi. But I read a discussion 
> on linuxcnc forum that without GUI someone could achieve 500 khz step 
> generating on Pi3.
> 
> I know it's been very long to explain what I would like to do but please 
> forgive me since I am not a native English speaker.
> 
> Thank you all in advance if you read this till here.
> 
> Have a good day/night.
> Berkdan
> 
> -- 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/machinekit/148c4e87-3d8a-4785-b435-e091a3f3cd67%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/01D310F6-8DE1-4BCC-B66B-604D3EBEC95E%40basdebruijn.com.

RE: [Machinekit] anyone know of any Machinekit kinematics for hangbots?

[bas]

Hi Doug,

 

As others have said, there seems to be a similar configuration. But if it’s not 
perfect then it’s relatively simple to create your own kinematics for your 
setup.

You also mention encoders, since you seem to want to use a beaglebone, you can 
have a look into the eQEP encoders. There are 3 of them, you seem to need 2. 
http://www.machinekit.io/docs/drivers/hal_arm335xQEP/

Not sure what this means for your hardware connection, going from whatever 
voltage the encoders use to the BeagleBone voltage.

 

You can also look into the driver you’re going to use. If it’s a driver which 
accepts your encoders and can drive your motors, then you could provide the 
driver with pulse/dir signals. This is not a closed loop back towards the 
beaglebone, although with the correct settings you won’t loose pulses.

 

Or if you can do some electronics (power to the motors), you could think about 
driving the motors with 2 PWM outputs and reading the encoders directly back. 
Nice closed loop setup.

 

Bas

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/01cf01d550da%2440a49c40%24c1edd4c0%24%40basdebruijn.com.

Re: [Machinekit] MachineKit Closed loop on X and Y

[Bas de Bruijn]

I think you should Google a bit on backlash and Machinekit / Linuxcnc
http://www.machinekit.io/docs/config/ini_config/#axis_-num-section-a-id-sub-axis-section-a
Please see the Backlash section.
I’ve also seen some topics on the linuxcnc forums.

Personally I’d fix the backlash :) 5 mm seems excessive to me and it seems you 
are trying to solve a problem at the wrong spot.



> On 23 Jul 2019, at 15:53, Edgardo Gho  wrote:
> 
> Hello,
> I have setup a Raspberry PI running machine kit to drive a mill (X,Y,Z axis).
> Each axis has a stepper motor coupled to a really bad screw.
> On X and Y there is a linear scale (5 microns pulses) which I read using a 
> modified Encoder Hal component.
> I setup up the HAL with one encoder for X, one for Y. The encoder position 
> (in machine units) is feed into Motion (Axis.0 and Axis.1) though one of the 
> feedbacks, and its also feed into a PID (one per axis).
> The PID inputs are in position units but the output is on velocity which goes 
> into Stepgen configured as velocity to drive the steppers (the stepper have a 
> driver which receives pulse+direction).
> 
> All of this setup works great IF I move axis independently.. meaning.. if I 
> move X +5mm several times, the PID makes sure it reaches the point.
> The Screws have a lot of backlash, so if I would move X back -5mm on open 
> loop it does not move back 5mm (because of the backlash) but using the PID 
> and the encoder it compensates perfectly and it reaches the point with no 
> issues.
> Same with Y axis.
> 
> The problem I have is when both Axis have to move at the same time, and one 
> of the axis encourters backlash. Imagine doing half a circle.. one of the 
> axis will move at constant speed but the other will reach a 0 speed point and 
> reverse rotation at half of the moment.
> WHile the second axis reverses, there is backlash, but the other axis 
> continue going forward so circle gets distorted.
> 
> I tried reducing increasing the resolution of the arc (doing lots of small 
> arc movements) and adjusting errors.. but what I need is for one axis to stop 
> while the other compensates for backslash.
> I tried adding G61 for exact stop but this had no effect on the backlash.
> 
> Any clues on how can I force the Trajectory planner to compensate for 
> backlash using the encoders?
> 
> Best Regards,
> Edgardo
> -- 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/machinekit/1db75010-6f2b-4f6f-90c0-4183d2e0b52e%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/7BC694E7-BC9C-4AE6-B2B0-2ED0692A9CA6%40basdebruijn.com.

Re: [Machinekit] OT: stall detection DC motor / Stepper

[Bas de Bruijn]

> On 14 Jul 2019, at 02:56, Chris Albertson  wrote:
> 
> For a DC motor, there are two things you can try.
> 
> 1) Measure the current.  Actually, you measure the voltage across a shunt 
> resistor and if the current is above some threshold you may assume the motor 
> is stalled.
> 2) You need to place a shaft encoder on the motor and measure the 
> position/speed and then if it is not what you expect you can assume it is 
> because the motor is stalled. Encoders cost about $10 on eBay and are 
> easy to use.
> 
> For a stepper motor only #2 is possible.  

That’s a great idea too, just some simple low resolution encoder, I just need 
to know if the speed has dropped. Some experimentation if  I can detect this is 
fast enough to not burn the motor.

Thx!

>> On Sat, Jul 13, 2019 at 10:38 AM Bas de Bruijn  wrote:
>> Hi,
>> 
>> I’ve recently been asked about a stall detection, from a DC motor, or a 
>> stepper with one of the trinamics silent stepsticks with stall detection.
>> 
>> The DC motor should be driven by switching an on/off relay and left/right by 
>> switching direction by a relay, and i want to check when the motor stalls 
>> (runs into an endstop). 
>> 
>> For the stepper motor, I’d want to detect missing steps, but other than I 
>> know these drivers are on my prusa, I have no knowledge on these and if 
>> these would be plug and play with for example a cramps board.
>> 
>> Anyone with experience on these 2 applications? The reason I would not use 
>> encoders is that I’d like to have an alternative to “just buy closed loop 
>> driver + motor + encoder”. Most important is that this should be a reliable 
>> setup, where performance may suffer at the expense of cost.
>> 
>> Cheers,
>> Bas
>> 
>> -- 
>> 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.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/machinekit/0770E383-352E-466C-9042-0C6824D40398%40basdebruijn.com.
>> For more options, visit https://groups.google.com/d/optout.
> 
> 
> -- 
> 
> Chris Albertson
> Redondo Beach, California

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/966734A6-41B3-46EE-A9D4-15E905319AA3%40basdebruijn.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Machinekit] OT: stall detection DC motor / Stepper

[Bas de Bruijn]

> On 14 Jul 2019, at 00:06, justin White  wrote:
> 
> How’s the dc motor driven? Straight dc, or a dc drive of some type?

The former, just to move a gripper to a position. No need to have position 
control, no need to be fast, just running into a product making physical 
contact. I prefer to have a signal in my program logic as opposed to working 
with timers to make sure I’m at the right position.

> Assuming it’s just a brushed dc motor you can install a current sensing 
> device like a shunt resistor and feed it back to an analog input. A stalled 
> dc motor will draw high current.

Yes, and I’d like to prevent burning the motor so I’d like to switch off the 
motor when stalled. I’d hoped there was some protocol board, but I guess that I 
need to do some calculations depending on supplies voltage (24 or 12V) and 
motor resistance. I’ll start digging.

> You can use a comparator in Hal to trigger a fault output when the analog 
> input voltage is higher to the setpoint on the other comparator input. Better 
> idea is to use an h-bridge driver that has its own current fault output. Dc 
> motors do a number on relay contacts used for reversing anyway so a simple 
> drive is a better bet.
> 
> I didn’t see good documentation on those step drivers on the website but the 
> only one I see with stall detection is the spi model. There are 1 or 2 
> diagnostic pins, find out how they work. If they output high or low level on 
> a current fault you can use them on a gpio input. Otherwise maybe they do 
> something over spi? If you find out more I could probably help you better.

Yes, I need to dig into spi for those drives. I’m getting a few to test.

Thanks!

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/855E6917-9501-488F-8640-E74573921EA6%40basdebruijn.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Machinekit] Re: DE10 Nano suggested development environment?

[Bas de Bruijn]

> On 11 Jun 2019, at 01:25, justin White  wrote:
> 
> Possibly,
> 
> Need to do some testing once I get the first rev assembled. This Particular 
> board is probably a bit too expensive to make for the open source world to 
> want, and the I/O arrangement is somewhat specific to my needs. That many 
> Phoenix Contact blocks gets pretty expensive.

I would be interested, keep me updated!
I think machinekit can do with some additional hardware between controllers and 
wires.

but imo cheap is a nice to have, function and quality come first. Think about 
how something industrial gets wired. Then you need some contact blocks to 
easily connect wires. In the total a more expensive part here will give you an 
edge somewhere else (manual labor). And indeed when you’re a diy-er labor does 
not come into the equation.

> I'll probably drop some OS version into the wild once I get it sorted, with a 
> more general I/O layout. This board is setup with 6 differential (or single 
> ended) encoder inputs, 6 differential stepgen outputs, 16 5v-30v inputs, 24 
> field voltage outputs up to 500ma, 2 opto-mosfet outputs @2A snubbed. Has a 
> 5A 5v DC-DC regulator that will accept up to 42VDC, power the DE10-nano 
> through GPIO and output the spare 5v up to 3A. My method of stepgen outputs 
> and GP inputs needs some testing.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/AB42AC5E-8278-4975-92FE-F7F10146067F%40basdebruijn.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Machinekit] Settings TB6600 drivers

[Bas de Bruijn]

> On 4 Jun 2019, at 13:32, scalaire  wrote:
> 
> Hi everyone,
> What are the best steplen, stepspace, dirhold and dirsetup settings with 
> TB6600 drivers?

This looks like what you want
https://forum.linuxcnc.org/16-stepconf-wizard/28553-configuring-tb6600

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/640DA7B1-E40B-40F3-A613-E64A45B6CD1B%40basdebruijn.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Machinekit] Velocity Extrusion - Dips in Velocity

[Bas de Bruijn]

> On 3 Jun 2019, at 14:26, Dennis  wrote:
> 
> Dear Machinekit users,
> right now we're facing issues with velocity extrusion. Our test system is 
> installed with Debian Stretch and Machinekit in version 0.1.1543327459.gite7 
> (uname -a output: Linux labor-m2 4.9.0-8-rt-amd64 #1 SMP PREEMPT RT Debian 
> 4.9.144-3.1 (2019-02-19) x86_64 GNU/Linux). We use three axes with one 
> extruder in velocity extrusion mode.
> 
> The attached .ngc-file was created with the ngcwriter-plugin for Cura. 
> Stumbling across another post in this forum 
> (https://groups.google.com/forum/#!searchin/machinekit/m67%7Csort:date/machinekit/mRTcGHU4lUc/hSyyGclIPagJ)
>  I also attached the output of the rs274 standalone interpreter. Maybe this 
> helps.
> 
> The Problem we have is, when we print the file (with and without filament) we 
> are facing issues with the extruder feedrate. For a short period of time the 
> feedrate seems to halt, although there should be continuous filament output. 
> We think the issue may be related to command M67 (perhaps related to this 
> issue here https://sourceforge.net/p/emc/bugs/437/). 

Well, first determine if this is the issue, if so, then my guess is that it had 
nothing to do with the velocity extruding, but with motion.
Remove the M67’s and see if the problem persists.

> Has anyone ever observed such a problem? 

I haven’t, but is has been a few years i printed with machinekit. I’ve lent out 
my self built printer (it was too big) and i now just use a prusa i3.

> 
> Unfortunately I'm not abled right now to post the contents of linuxcnc.log 
> with DEBUG=5 enabled, because our printer has a hardware malfunction.
> 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/machinekit/96b1502a-4408-440c-8ac3-268cd3659957%40googlegroups.com.
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/69E69813-FFD6-4727-9AA9-100979ACEDE0%40basdebruijn.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Machinekit] Machinetalk - quo vadis?

[Bas de Bruijn]

a product and relies on a stable 
branch, it’s up for that person/company to fork and create a stable branch and 
take care of that. We have a build system that will show if packages are 
successfully built, and that’s my (literally) green light for merging. That 
simple. 
If for whatever reason a PR breaks the code, then either the maintainer being 
around fixes it, or if they are gone and nobody can fix it, we revert the PR.

If you want to add functionality, see problems, improve, the way this works 
(best) is:
Create an issue on github for the repository it concerns.
This is the focus point for the problem, and helps keeping the 
information/discussion centered
Explain your case, discuss
Have other people engaged in the discussion. This really helps.
Hopefully this results you end up with likeminded people.
Create PR’s preferably in small bits. Do not break the API.
Smaller bits are easier and less “scarier” than a huge blob that only the 
author of the code understand. It creates progress, traction, increases the 
chance of early testing. Having said that, because the code can be difficult, 
PR's might be bigger if there are a lot of architectural changes needed. But 
either way, make a PR and it will be merged if it does not mess up the existing 
code. 
So long story short, Do not let the “there is no roadmap” fact hold you back.

Bas

>>> 
>>> 
>>> 
>>> --
>>> website: > http://www.machinekit.io <http://www.machinekit.io>>
>>> blog: > http://blog.machinekit.io <http://blog.machinekit.io>>
>>> github: > https://github.com/machinekit
>>> <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
>>> <mailto:machinekit+unsubscr...@googlegroups.com>> . Visit this
>>> group at > https://groups.google.com/group/machinekit
>>> <https://groups.google.com/group/machinekit>> . To view this
>>> discussion on the web visit >
>>> https://groups.google.com/d/msgid/machinekit/6b0977ef-1595-4919-ae1b-faf3b8428670%40googlegroups.com
>>> <https://groups.google.com/d/msgid/machinekit/6b0977ef-1595-4919-ae1b-faf3b8428670%40googlegroups.com?utm_medium=email_source=footer>>
>>>  .
>>> For more options, visit > https://groups.google.com/d/optout
>>> <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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/machinekit/20190527121558.02c13f85%40edeltraud.
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/BF288D1F-0E0B-401E-ACA1-F047619DC4E1%40basdebruijn.com.
For more options, visit https://groups.google.com/d/optout.

[Machinekit] Re: python hal component userspace

[Bas de Bruijn]

On Thursday, May 16, 2019 at 4:53:25 PM UTC+2, mngr wrote:
>
> Hi,
>
> I am trying to build userspace hal components, and I am trying to build 
> them with python.
>
> I can find a lot of examples in the repository calling 
> machinekit.rtapi.loadrt, but I have the vague idea of using 
> machinekit.hal.loadusr
>
> Until now the only solution i have found is something structured like this
> #comp file
> from machinekit import hal
>
> comp=hal.component("name")
> comp.newpin("a", HAL.IN , HAL.BIT)
>
> while 1:
>   comp["a"]=comp["b"]
>   time.sleep(1)
>
>
>
> and loading
>
> hal.loadusr("comp")
>
>
>
> Is this the way it should be used?
>

I think you're mixing concepts.

a python userspace hal component is a component created in Python (in this 
case) which exposes its pins in HAL. It's a userspace component. So you 
initiate setting output pins and read input pins from within your python 
code. So it's not executed in the same rigid RT time like the realtime 
components. You have to take care that you create a loop to do so if you 
plan to do it more than once.
 

>
> I know the hal.addf function, I would like to use it to load function on 
> threads. Is it possible to export function from userspace components? I 
> haven't found any way of exporting functions from python
>

You do not expose a userland function and add it to a HAL thread as with a 
realtime component. You can't, do not want and do not need that. You 
execute your code from python. It's running independent from the realtime 
thread. You read/write your userspace component pins once, twice, many 
times, or not at all. It is not related to the realtime HAL thread..

hal.addf("some_rt_component.funct", "servothread") is the same as using 
`halcmd addf some_rt_component.funct servothread`


> I would like to write something like that
> #comp file
> from machinekit import hal
>
> comp=hal.component("name")
> #comp.newpin...
>
> def foo():
>   comp["a"]=comp["b"]
>
> hal.export(foo)
>
>
> hal.loadusr("comp")
> hal.addf("foo","servo-thread")
>
>
hal.loadusr("something") is used for loading a userspace script/program 
from HAL (you can load halscope for example in this way). In your situation 
this has nothing to do with your python script functionality, other perhaps 
than starting your python script from HAL, and your python script then 
should take care of creating a userspace component with pins, looping and 
whatnot.
 

>
>
> Can you please give me some advice?
>

hope it helped :)


> mngr
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
 

-- 
website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
https://github.com/machinekit
--- 
You received this message because you are subscribed to the Google Groups 
"Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to machinekit+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/machinekit.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/3e56f8ae-e904-4bb3-987b-abc7b4390635%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Machinekit] Re: Mklauncher Problem migrating to MachineKit -hal -cnc packages

[Bas de Bruijn]

Hi Michael,
We’re the Machinekit packages that worked recent ones?
Bas

> On 15 May 2019, at 18:54, Michael Brown  wrote:
> 
> BTW
> I have set
> REMOTE=1
> in /etc/linuxcnc/machinekit.ini
> 
>> On Wednesday, 15 May 2019 18:50:26 UTC+2, Michael Brown wrote:
>> I have a cnc router running on a DE0_Nano_SoC with Machinekit_Client Cetus 
>> gui (mkwrapper).
>> that I'm trying to migrate to the new:
>> machinekit-hal-rt-preempt
>> machinekit-cnc-rt-preempt
>> Packages.
>> 
>> All that happens when I start the config in Machinekit client (after 
>> migration) is that the session terminates after about 15-20 sec.
>> With an option to see an errorfree Machinekit log.
>> 
>> I use this process for the "MK package migration":
>> 
>> sudo apt -y purge machinekit machinekit-rt-preempt
>> sudo apt -y autoremove
>> sudo apt update
>> sudo apt -y install machinekit-hal-rt-preempt machinekit-cnc-rt-preempt
>> sudo nano /etc/linuxcnc/machinekit.ini
>> sudo sh -c 'echo ""> /var/log/linuxcnc.log'
>> sudo reboot now
>> 
>> I run this start script via a systemd service:
>> https://gist.github.com/the-snowwhite/d73c3fd090f98f0e94e6d7f7ed96a1a1
>> 
>> That does this:
>> /usr/bin/mklauncher /home/machinekit/Hm2-soc_FDM/Cramps/PY/OX
>> 
>> the python run file is here:
>> https://github.com/the-snowwhite/Hm2-soc_FDM/blob/ob-ox/Cramps/PY/OX/run.py
>> 
>> Before the logs files below I have noticed this message in 
>> linuxcnc_print.txt:
>> 
>> Starting DISPLAY program: mkwrapper
>> Can't execute DISPLAY program mkwrapper  
>> Shutting down and cleaning up Machinekit...
>> 
>> 
>> So after the below exploration I suspect it has somthing to do with mkwapper 
>> changes in the new -hal -cnc repos ?
>> 
>> Linuxcnc log file after starting the session in Machinekit client (old mk 
>> packages)
>> https://gist.github.com/the-snowwhite/b21f9c3b2473c37831a51876e6c3e941#file-linuxcnc-log-old_mk_repo-ok_session-started-only-txt
>> 
>> Linuxcnc log file after trying to stare the session in Machinekit client 
>> (new mk-hal-cnc packages)
>> https://gist.github.com/the-snowwhite/b21f9c3b2473c37831a51876e6c3e941#file-linuxcnc-log-full_new-mk-hal-cnc_repos-bad-txt
>> 
>> Comparing All I can see here is that all below here (line 2355) is missing 
>> and the session terminates instead:
>> https://gist.github.com/the-snowwhite/b21f9c3b2473c37831a51876e6c3e941#file-linuxcnc-log-old_mk_repo-ok_session-started-only-txt-L2355
>> 
>> https://gist.github.com/the-snowwhite/b21f9c3b2473c37831a51876e6c3e941#file-linuxcnc-log-full_new-mk-hal-cnc_repos-bad-txt-L2356
>> 
>> linuxcnc_debug-txt is here:
>> https://gist.github.com/the-snowwhite/b21f9c3b2473c37831a51876e6c3e941#file-linuxcnc_debug-txt
>> 
>> 
>> linuxcnc_print.txt is here:
>> https://gist.github.com/the-snowwhite/b21f9c3b2473c37831a51876e6c3e941#file-linuxcnc_print-txt
>> 
>> The python based config is here 
>> https://github.com/the-snowwhite/Hm2-soc_FDM/tree/ob-ox/Cramps/PY/OX
>> 
>> Best wishes Michael B.
>> 
> 
> -- 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/machinekit/b216cad8-bead-4d74-b009-9784e2159010%40googlegroups.com.
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/machinekit/A60464F7-35F8-41A3-B960-D3B15A5CCC04%40basdebruijn.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Machinekit] Re: configure touchy

[Bas de Bruijn]

> On 5 May 2019, at 12:39, scalair...@free.fr wrote:
> 
> I have seen this page, the problem is that in my.ini file I change:
> 
> DISPLAY = gmoccapy ==> DISPLAY = touchy
> 
> then machinekit doesn't start anymore
> 
> @++ Jean Claude

I have not used touchy, but reading this:
http://www.machinekit.io/docs/gui/touchy/#hal-connections
Tells us that you need to add to your configuration a touchy.hal file.

First try to find in the current configurations for a touchy.hal file. Or maybe 
there is a simulation which uses touchy.

Bas
> -- 
> 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: configure touchy

[Bas de Bruijn]

> On 5 May 2019, at 11:47, scalair...@free.fr wrote:
> 
> Machinekit works with gmoccapy and this configuration: What are the things I 
> need to change for touchy to work.
> 
> thank you

http://www.machinekit.io/docs/gui/touchy/
I suggest looking at configurations for examples.

> 
> @++ Jean Claude
>  
>> 
> 
> -- 
> 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] scheduling policy

[Bas de Bruijn]

> On 25 Apr 2019, at 09:59, "schoone...@gmail.com"  wrote:
> 
> 
>> On 24/04/19 20:57, mngr wrote:
>> Hi,
>> 
>> I am trying to improve the latency on my Machinekit installation.
>> As hardware I have an ASRock 90-MXB870-A0UAYZ. I have chosen this because I 
>> read about it in the linuxcnc forum.
>> 
>> I am using Debian 9.8, with kernel 4.9 rt
>> 
>> machinekit@debian:~$ uname -a
>> Linux debian 4.9.0-8-rt-amd64 #1 SMP PREEMPT RT Debian 4.9.144-3.1 
>> (2019-02-19) x86_64 GNU/Linux
>> 
>> 
>> 
>> The latency I have is 50 microsecond, and from what I have read it is a bit 
>> too high (it should be between 10 and 30 microsecond)
>> so I started studying about latency in the rt kernel.
> A search of their site failed to find any ref to this MB, it is not in their 
> latency-test list.  Do you have a link?
> 
> All their testing will have been with rtai kernels (and then exaggerated very 
> often).
> 
> What is your aim, to do software stepgen and use a PCI parport board?
> 
> You will need to look at isolcpus, acpi_irq_nobalance, noirqbalance etc.  
> Turn off hyper threading, virtualisation, suspend to RAM, most of power 
> management.
> 
> If that does not get you where you want to be, we have added support for 
> libcgroup, partrt etc which has been tested on Intel processors to bring
> latency down dramatically.
> John Morris did a page in the docs here
> http://www.machinekit.io/docs/hal/threads-and-latency/

I have a setup using a J1900, isolated CPU’s 2 and 3 (they share the L2 cache) 
and the cgroups setup. The max latency I got, running 5 glxgears and a simple 
thread on those isolated CPU’s was approx 9000 ns. (I had it running for 48 
hrs). No other special tweaks done.

> In theory this could be used with rt-preempt kernels for software stepgen.
> You need to read it carefully because the number of cores and how the L2 
> cache is organised are critical, don't know how AMD do it,
> haven't used one for yonks.
> 
> 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.

-- 
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] BBB + Machinekit + 5 Axis Breakout Board axis_0 works fine, others no signal

[Bas de Bruijn]

> On 7 Apr 2019, at 11:55, gang han  wrote:
> 
> I changed Nothing. I just check error message in linuxcnc.log.
> I thought the error in the log file cause the problem, I did not test pins 
> signal.

I don’t understand what you did or did not do at all. An entry in a log file is 
the result of an error, not a cause.
Glad you got it working.


> 
> 1845 is correct.
> 
> Bas de Bruijn  于2019年4月7日周日 下午5:39写道：
>> 
>> 
>> > On 7 Apr 2019, at 11:29, gang han  wrote:
>> > 
>> > Hi
>> > thanks.
>> > i solved the problem by using like 1845 with the error "user hpg: Unknown 
>> > pin: 228"
>> > pin2_28 is the pin of old version beaglebone, maybe there is some wrong 
>> > inside hal_pru_generic.
>> 
>> I don’t think there’s anything wrong with hal_pru_generic
>> 
>> What did you do differently than your previous attempt at using the pin like 
>> 1845? Then it did not work and now it does. What did you change?
>> 
>> 

-- 
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] BBB + Machinekit + 5 Axis Breakout Board axis_0 works fine, others no signal

[Bas de Bruijn]

>On 7 Apr 2019, at 10:46, hanfeizi <mailto:hanfeizi...@gmail.com> wrote:
>I first config pru pin with the pin address , the axis_0 work fine.
>as you mentioned, i reconfig the pin with pin number P8_45 --> 1845 as pruout, 
>but nothing changed .
>i still find this error in linuxcnc.log
>And axis_0 work fine , others no output.

Well, I don’t know your setup, and I’m no expert on the beaglebone.
But try 845 instead of 1845

Also, make sure to read your HAL file and check that you actually assign the 
values to correct pins, like here: 
https://github.com/machinekit/machinekit/blob/master/configs/ARM/BeagleBone/CRAMPS/CRAMPS.hal#L94
 




在 2019年4月7日星期日 UTC+8下午4:15:26，Bas de Bruijn写道：

>From: machi...@googlegroups.com  On Behalf Of 
>hanfeizi 
>Sent: Sunday, 7 April 2019 09:41 
>To: Machinekit  
>Subject: Re: [Machinekit] BBB + Machinekit + 5 Axis Breakout Board axis_0 
>works fine, others no signal 

>thanks for your help 
>here is debug log. 

See these lines: 
Apr  6 17:36:11 beaglebone rtapi:0: 1:rtapi_app:3135:user hpg: Unknown pin: 232 
Apr  6 17:36:11 beaglebone rtapi:0: 1:rtapi_app:3135:user hpg: Unknown pin: 224 
Apr  6 17:36:11 beaglebone rtapi:0: 1:rtapi_app:3135:user hpg: Unknown pin: 236 
Apr  6 17:36:11 beaglebone rtapi:0: 1:rtapi_app:3135:user hpg: Unknown pin: 228 

For an example on how it’s used see this line: 
https://github.com/machinekit/machinekit/blob/master/configs/ARM/BeagleBone/CRAMPS/CRAMPS.hal#L30
 

for how and what, please see the hal_pru_generic component, and specifically 
this section: 
http://www.machinekit.io/docs/man/man9/hal_pru_generic/#i-o-pins 

Bas 
-- 
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 mailto: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] BBB + Machinekit + 5 Axis Breakout Board axis_0 works fine, others no signal

[bas]

>From: machinekit@googlegroups.com  On Behalf Of 
>hanfeizi
>Sent: Sunday, 7 April 2019 09:41
>To: Machinekit 
>Subject: Re: [Machinekit] BBB + Machinekit + 5 Axis Breakout Board axis_0 
>works fine, others no signal

>thanks for your help
>here is debug log.

See these lines:
Apr  6 17:36:11 beaglebone rtapi:0: 1:rtapi_app:3135:user hpg: Unknown pin: 232
Apr  6 17:36:11 beaglebone rtapi:0: 1:rtapi_app:3135:user hpg: Unknown pin: 224
Apr  6 17:36:11 beaglebone rtapi:0: 1:rtapi_app:3135:user hpg: Unknown pin: 236
Apr  6 17:36:11 beaglebone rtapi:0: 1:rtapi_app:3135:user hpg: Unknown pin: 228

For an example on how it’s used see this line:
https://github.com/machinekit/machinekit/blob/master/configs/ARM/BeagleBone/CRAMPS/CRAMPS.hal#L30

for how and what, please see the hal_pru_generic component, and specifically 
this section:
www.machinekit.io/docs/man/man9/hal_pru_generic/#i-o-pins

Bas

-- 
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] BBB + Machinekit + 5 Axis Breakout Board axis_0 works fine, others no signal

[Bas de Bruijn]

> On 7 Apr 2019, at 07:03, hanfeizi  wrote:
> 
> BBB + Machinekit + 5 Axis Breakout Board axis_0 works fine, others no signal 
> 
> HAL and INI Attached.
> 
> shenkacnc.sh used to config pins model.
> 
> I test other Pru Out  , all BBB pru pins works fine.
> 
> can anyone help ?

You do not provide enough info. We can’t guess what’s going on just by looking 
at some configuration files without any error messages.
Please read up on getting help first.
http://www.machinekit.io/docs/getting-help/

Bas

-- 
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 on BBB; not all configurations load

[Bas de Bruijn]

Have you changed the path to setup.bridge.sh as Daren pointed out?

> On 4 Apr 2019, at 15:24, Sardar Vayghannezgad  wrote:
> 
> I read online that starting as ssh -Y user@beaglebone.local may help. I am 
> getting this if I start that way:
> ln: cannot remove '/tmp/linuxcnc.print': Operation not permitted
> ln: cannot remove '/tmp/linuxcnc.debug': Operation not permitted
> 
> 
> 
>> On Wednesday, April 3, 2019 at 11:19:08 PM UTC+3, Sardar Vayghannezgad wrote:
>> Once I start machinekit on my element14 BBB, the configuration window pops 
>> up with an array of configurations. But it looks like my favorite one won't 
>> load. I get the following:
>> 
>> 
>> machinekit@beaglebone:~$ machinekit
>> MACHINEKIT - 0.1
>> Machine configuration directory is 
>> '/home/machinekit/machinekit/configs/ARM.BeagleBone.PocketNC-1'
>> Machine configuration file is 'PocketNC.ini'
>> Starting Machinekit...
>> rtapi_msgd command:  /usr/libexec/linuxcnc/rtapi_msgd --instance=0 
>> --rtmsglevel=1 --usrmsglevel=1 --halsize=524288
>> rtapi_app command:  /usr/libexec/linuxcnc/rtapi_app_rt-preempt --instance=0
>> io started
>> halcmd loadusr io started
>> PocketNC.hal:10: 
>> execv(/home/machinekit/machinekit-dev/configs/ARM/BeagleBone/PocketNC/setup.bridge.sh):
>>  No such file or directory
>> E: 19-04-03 19:38:58 dangling 'DEALER' socket created at 
>> hal/utils/halcmd_rtapiapp.cc:284
>> PocketNC.hal:10: program 
>> '/home/machinekit/machinekit-dev/configs/ARM/BeagleBone/PocketNC/setup.bridge.sh'
>>  failed, returned 1
>> Shutting down and cleaning up Machinekit...
>> Cleanup done
>> Machinekit terminated with an error.  For simple cases more information
>> can be found in the following files:
>> /home/machinekit/linuxcnc_debug.txt
>> /home/machinekit/linuxcnc_print.txt
>> 
>> 
>> For other cases get more meaningfull information by restarting after
>> export DEBUG=5
>> 
>> 
>> and look at the output of:
>> /var/log/linuxcnc.log
>> dmesg
>> 
>> 
>> When looking for errors, specifically look for libraries that fail to load
>> by looking for lines with 'insmod failed' as per example below.
>> 
>> 
>> insmod failed, returned -1:
>> do_load_cmd: dlopen: nonexistant-component.so: cannot open shared object 
>> file:
>> No such file or directory
>> 
>> 
>> For getting help, please have a look here: 
>> www.machinekit.io/docs/getting-help/
>> 
>> I have tried my best to figure this out using the tips in the message above, 
>> but couldn't do much. I ran this command suggested here by someone called 
>> cncbasher, but didn't help with my case. Likewise, I have taken a look here 
>> and there. On the latter, step 9 suggests editing something, but I have no 
>> inkling how to access that or nano what. This latter link seems something, 
>> can anyone please help me edit those lines?
>> 
>> Thanks.
>> 
> 
> -- 
> website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
> https://github.com/machinekit
> --- 
> You received this message because you are subscribed to the Google Groups 
> "Machinekit" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to machinekit+unsubscr...@googlegroups.com.
> Visit this group at https://groups.google.com/group/machinekit.
> For more options, visit https://groups.google.com/d/optout.

-- 
website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
https://github.com/machinekit
--- 
You received this message because you are subscribed to the Google Groups 
"Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to machinekit+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.

[Machinekit] Re: Border between Machinekit-HAL and Machinekit-CNC

[Bas de Bruijn]

On Sunday, March 31, 2019 at 1:45:55 AM UTC+1, cern wrote:
>
> Been looking into the distinction of Machinekit-HAL and Machinekit-CNC 
> repositories and so far what I can tell the Machinekit-HAL is perfectly 
> happy to run on its own but the Machinekit-CNC needs as a prerequisite the 
> Machinekit-HAL. I also see that the majority of work done in Machinekit as 
> a fork of LinuxCNC was about the HAL layer, so it's possible to say that 
> Machinekit is more Machinekit-HAL than Machinekit-CNC. What I would like to 
> know is what's the end game of splitting?
>

Machinekit-HAL is indeed the HAL part of the original LinuxCNC. The 
realtime Hardware Abstraction Layer. Machinekit-CNC is the CNC application 
on top of Machinekit-HAL. Combined they are the original fork of LinuxCNC: 
Machinekit.
The reason that Machinekit forked from LinuxCNC and most work has been put 
into the HAL layer has a few reasons.
tOne of the original reasons of the fork from LinuxCNC was that the 
developers that split of were not satisfied with the development of 
LinuxCNC. They envisioned that you should be able to run the realtime 
environment on multiple kernels instead of being tied to RTAI. Further more 
there were a lot of new boards/platforms, so energy went into running not 
only on a PC, but a BeagleBone board, and other ARM devices. Raspberry Pi, 
De0-NANO, to name a few. Add to that the ability to run threads on multiple 
cores in a realtime safe way.
Apart from that hardware part, The CNC application is a very big codebase, 
having evolved over the years, and improving that needs people that are 
able to understand the application. Technology has moved from a single 
desktop PC with a Parallel port to newer smaller devices.
 

>
> If it is intended for Machinekit-CNC to forever require the Machinekit-HAL 
> or if there is push for these two projects to be independent - i.e. if it's 
> to be possible to install only Machinekit-CNC and talk to Machinekit-HAL on 
> a different machine (or even the same machine) over the application bus? 
> (As opposed by the RT-capable field bus, what I call application bus is the 
> higher level messaging protocols and connected services like Machinetalk, 
> HALtalk, and whatnot.) Application bus which does not care if it's 
> interprocess or off-system.
>

Yes, you can't install machinekit-CNC without machinekit-HAL on the same 
machine.
That was one of the reasons that a lot of work went into remote components 
and machinetalk/haltalk and ringbuffers.

One of the things that can be done is to use machinekit-hal as the realtime 
motion stack, and have planning done by for example ROS (non rt planning). 
You don't need the full CNC stack in a lot of cases.
 

>
> I guess that the motion (and other) component would then need to be split 
> into several parts (but then it is unyielding blob anyway), one RT HAL side 
> and other not-RT. Would the current ring buffer FIFO be enough to 
> facilitate the distinction? (Given one example is given as the 
> streamer-hal_streamer component, it should.)
>

The problem is indeed a clear distinction between what is needed in 
realtime, and what is not.
Hence the ringbuffer. That's a realtime safe scheme for getting info in and 
out of the realtime part. The interpolator component uses such a scheme, as 
well as the jplanner component (both non-RT to RT). For a component like 
delayline, it uses a ringbuffer to delay samples for an amount of cycles 
(RT -> RT). The thing is, you can attach to the same ringbuffer from 
multiple components, RT or non-RT.
This is an example of putting pin values in a ring (RT) and reading these 
from a python script (non-RT).
https://github.com/machinekit/machinekit-hal/tree/master/src/hal/sample_channel
 

>
> The question is not if somebody is going to develop it but what the 
> authors of the split would like IT to be. (Something like these ZeroMQ RFCs 
> which are so popular here.)
>

Personally, I value the HAL part the most. But it all depends on what 
people are interested in.


> (For example, it could be possible to then develop and configure the 
> system so the MACH3/4 would be the Machinekit-CNC and Machinekit-HAL would 
> function as the SmoothStepper or CSMIO/IP-A real-time controller. Not that 
> I am interested in it, just an example of how my thoughts go.)
>

Building LinuxCNC on top of machinekit-HAL would make more sense to me. 
Hope this answers some of your questions.

-- 
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 Client keeps loading with no result

[bas]

You should read up on this:

https://github.com/machinekit/QtQuickVcp#showcase-applications-and-examples

 

QtQuickVCP is a library for making a UI with QtQuick.

Right now, you are starting a machinekit configuration, and having that window 
shown on your windows OS. But the UI is still coming from the BBB.

 

For you to have the remote UI, you need to start a configuration that exposes 
the services that the client need to attach to.

(my terminology might be off). Since you have a CNC setup, this is your 
starting point: https://github.com/machinekit/Cetus

 

In the paragraphs below the first link above, there are examples of 
configurations.

These configurations load the HAL realtime environment, including HAL remote 
components. These remote components then can be “seen” by the remote UI.

 

Bas

 

From: machinekit@googlegroups.com  On Behalf Of 
Sardar Vayghannezgad
Sent: Friday, 29 March 2019 21:09
To: Machinekit 
Subject: Re: [Machinekit] Machinekit Client keeps loading with no result

 

Thanks a million Schooner. I guess you were sort of right. I followed the links 
and from there ended up watching this video 
<https://www.youtube.com/watch?v=aHwv8U3ptvA>  to realize that I actually 
needed to install Xming. So now I can run machinekit on BBB for the machinekit 
configuration windowd (see the attached image please) to pop up. But it looks 
like my knowledge lags behind my practical progress, as I still can't get my 
around what are these MachinekitClient and QtQuickVCP good for in this 
scenario. Can anyone shed some light on this please?  BTW, I'm having the same 
"nonstop loading" issue with the Machinekit Client.


On Friday, March 29, 2019 at 5:21:24 PM UTC+3, Schooner wrote:

 

On 29/03/19 14:11, Sardar Vayghannezgad wrote:

I can't seem to start Machinekit on my BBB because: 

 

 

root@beaglebone:/home/machinekit# 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)

 

 

I tried the following workarounds, but nothing seems to have changed:

 

sudo apt-get install xauth
touch ~/.Xauthority

as suggested by Karl Jacobs here 
<https://groups.google.com/forum/#%21topic/machinekit/nGrU3diWEFA> 

 

 

sudo apt install xorg

as suggested here 
<https://groups.google.com/forum/#%21topic/machinekit/1dkgEgov6Wg> , by a 
person called Schooner.


You are being selective in your reading

Read the whole thread and follow the links
These for example 
https://unix.stackexchange.com/questions/12755/how-to-forward-x-over-ssh-to-run-graphics-applications-remotely
https://unix.stackexchange.com/questions/314862/minimal-no-hassle-debian-install-with-functioning-x11-login-etc




 

but still I'm getting the error.


On Friday, March 29, 2019 at 4:01:42 PM UTC+3, Bas de Bruijn wrote: 

 


On 29 Mar 2019, at 13:47, Sardar Vayghannezgad mailto:sard...@gmail.com> > wrote:

Thanks for reaching out, Bas. 

 

 

According to the first question, which link should I go with on  
<https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fmachinekit%2FQtQuickVcp=D=1=AFQjCNFSHHjDTy575Uy7ujQBViRsMgvGDA>
 this page. 
No idea what you actually link to

 

  

A few lines below are download links to both QtQuickVCP and Machinekit for 
various OS's.

 

I think you mean machinekit-client

Machinekit only runs on Linux.

 

Just pick the one for the os you’re going to run machinekit-client on.





*   Have you got any ideas why my Machinekit Client acts up the way it 
does? I have attached a photo of it in the original post.

Yes, it can’t find machinekit instances. As per my previous remarks, make sure 
there is an actual machinekit (your BBB) started, and that you have enabled it 
to expose itself so a remote UI can connect to it (the machinekit.ini file)

 

 

Thanks



On Friday, March 29, 2019 at 1:17:04 PM UTC+3, Bas de Bruijn wrote: 

 


On 29 Mar 2019, at 09:53, Sardar Vayghannezgad mailto:sard...@gmail.com> > wrote:

I have tried my best to understand the fundamental ins and outs of running 
Machinekit on BBB from my windows desktop, but there are so many technical 
concepts and approaches that I just can't fully understand everything. Although 
it seems I'm towards the end of this, I'm already frustrated, and since working 
for a sort of tight deadline I need some practical help, and need that in 
layman's term

Re: [Machinekit] Machinekit Client keeps loading with no result

[Bas de Bruijn]

> On 29 Mar 2019, at 13:47, Sardar Vayghannezgad  wrote:
> 
> Thanks for reaching out, Bas.
> 
> 
>> According to the first question, which link should I go with on this page. 
>> No idea what you actually link to
> 
>  
> A few lines below are download links to both QtQuickVCP and Machinekit for 
> various OS's.

I think you mean machinekit-client
Machinekit only runs on Linux.

Just pick the one for the os you’re going to run machinekit-client on.

> Have you got any ideas why my Machinekit Client acts up the way it does? I 
> have attached a photo of it in the original post.
Yes, it can’t find machinekit instances. As per my previous remarks, make sure 
there is an actual machinekit (your BBB) started, and that you have enabled it 
to expose itself so a remote UI can connect to it (the machinekit.ini file)

> 
> Thanks
> 
> 
>> On Friday, March 29, 2019 at 1:17:04 PM UTC+3, Bas de Bruijn wrote:
>> 
>> 
>>> On 29 Mar 2019, at 09:53, Sardar Vayghannezgad  wrote:
>>> 
>>> I have tried my best to understand the fundamental ins and outs of running 
>>> Machinekit on BBB from my windows desktop, but there are so many technical 
>>> concepts and approaches that I just can't fully understand everything. 
>>> Although it seems I'm towards the end of this, I'm already frustrated, and 
>>> since working for a sort of tight deadline I need some practical help, and 
>>> need that in layman's terms, into the bargain, please.
>> 
>>> I followed these instructions to run M.K. on BBB from my desktop. But I am 
>>> badly thrown off. I have apparently successfully done everything on that 
>>> instruction page, but just don't know how to start what!! I don't know what 
>>> command to use on the PuTTy. 
>> 
>> You need to start Machinekit when you’ve logged into your BBB. Putty is just 
>> a terminal you log onto your BBB. Everything you type into that terminal, is 
>> as if you would type on a keyboard directly attached to the BBB on s 
>> terminal on a screen directly attached to the BBB.
>> 
>>> (Please, as far as possible, don't direct me to start everything from 
>>> scratch, as I already had Debian Jessie installed on BBB, but decided to 
>>> change it to Stretch.)
>>> 
>>> My newbie questions:
>>> Should Machinekit Client be installed on my Windows OS or on the BBB?!  (I 
>>> already have M.K Client on my Windows OS. but once I start it, it keeps 
>>> loading in no veil, with no available instances.)
>> Machinekit client on your windows OS
>> 
>> Make sure that on your BBB you have set REMOTE = 1 in the file machinekit.ini
>> That file should be here: /etc/linuxcnc/machinekit.ini
>>> According to the first question, which link should I go with on this page.
>> No idea what you actually link to.
>>> AFAIK, I need a U.I on my desktop to give me access to the M.K. Is this UI 
>>> the Machinekit Client? How can I start it from PuTTY?
>> You start machinekit-client from your Windows PC. It’s a remote UI (seen 
>> from the BBB perspective) and you don’t need to start the UI from Putty 
>> (your BBB) but from the pc.
>> 
>> In the putty terminal type: machinekit
>> 
>>> FYI:
>>> Operating System: Debian GNU/Linux 9 (stretch)
>>> Kernel: Linux 4.4.155-ti-rt-r153
>>>   Architecture: arm
>>> 
>>> Thanks in advance
>>> -- 
>>> 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 machi...@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/machinekit.
>>> For more options, visit https://groups.google.com/d/optout.
>>> <2019-03-29_11h36_57.png>
> 
> -- 
> 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 Client keeps loading with no result

[Bas de Bruijn]

> On 29 Mar 2019, at 09:53, Sardar Vayghannezgad  wrote:
> 
> I have tried my best to understand the fundamental ins and outs of running 
> Machinekit on BBB from my windows desktop, but there are so many technical 
> concepts and approaches that I just can't fully understand everything. 
> Although it seems I'm towards the end of this, I'm already frustrated, and 
> since working for a sort of tight deadline I need some practical help, and 
> need that in layman's terms, into the bargain, please.

> I followed these instructions to run M.K. on BBB from my desktop. But I am 
> badly thrown off. I have apparently successfully done everything on that 
> instruction page, but just don't know how to start what!! I don't know what 
> command to use on the PuTTy. 

You need to start Machinekit when you’ve logged into your BBB. Putty is just a 
terminal you log onto your BBB. Everything you type into that terminal, is as 
if you would type on a keyboard directly attached to the BBB on s terminal on a 
screen directly attached to the BBB.

> (Please, as far as possible, don't direct me to start everything from 
> scratch, as I already had Debian Jessie installed on BBB, but decided to 
> change it to Stretch.)
> 
> My newbie questions:
> Should Machinekit Client be installed on my Windows OS or on the BBB?!  (I 
> already have M.K Client on my Windows OS. but once I start it, it keeps 
> loading in no veil, with no available instances.)
Machinekit client on your windows OS

Make sure that on your BBB you have set REMOTE = 1 in the file machinekit.ini
That file should be here: /etc/linuxcnc/machinekit.ini
> According to the first question, which link should I go with on this page.
No idea what you actually link to.
> AFAIK, I need a U.I on my desktop to give me access to the M.K. Is this UI 
> the Machinekit Client? How can I start it from PuTTY?
You start machinekit-client from your Windows PC. It’s a remote UI (seen from 
the BBB perspective) and you don’t need to start the UI from Putty (your BBB) 
but from the pc.

In the putty terminal type: machinekit

> FYI:
> Operating System: Debian GNU/Linux 9 (stretch)
> Kernel: Linux 4.4.155-ti-rt-r153
>   Architecture: arm
> 
> Thanks in advance
> -- 
> 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.
> <2019-03-29_11h36_57.png>

-- 
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: Nvidia Jetson Nano

[Bas de Bruijn]

> On 20 Mar 2019, at 03:57, Daren Schwenke  wrote:
> 
> I guess unless some of you work for Nvidia, someone having one already is 
> pretty unlikely.
> Arrow shows 16 weeks.  Sparkfun doesn't have a date.  SeedStudio shows Apr 
> 12th!
> Here's hoping...
> Anyone figured out what monumental tasks would have to take place to run on 
> Ubuntu 18.04/LTS kernel 4.9 anyway?

I guess that most important task would be how to access the gpio from HAL.
But I’m no authority on how to check/do that :)

> 
>> On Tuesday, March 19, 2019 at 10:08:40 PM UTC-4, Daren Schwenke wrote:
>> I just got a little bit excited as a powerful machine vision platform in a 
>> small and relatively inexpensive form factor just happened.
>> 128 Cuda cores...
>> It even has a Pi camera slot onboard. 
>> Ok... a lot excited..
>> 
>> https://www.nvidia.com/en-us/autonomous-machines/embedded-systems/jetson-nano/
>> 
>> This would be absolutely perfect for running OpenCV with the P1.
>> 
>> Now the question becomes... how would one go about getting Machinekit 
>> running on this?
>> I know it has 40 pins of gpio and onboard ethernet.
>> I will design a daughterboard for it.
>> 
>> Anyone got one already to try it out?  
>> Supposedly it runs a variant of Ubuntu 18.04 LTS with LTS kernel 4.9.
>> 
>> 
> 
> -- 
> 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] cgroups and isolating CPU’s

[Bas de Bruijn]

> On 9 Mar 2019, at 00:02, c...@tuta.io wrote:
> 
> No, no, you misunderstood. I have been thinking about getting myself a new 
> board for software generated stepper pulse signals. I don't have the J5005 
> yet. But I have recently upgraded my notebook from a 1x8GB stick of DDR4 
> memory to 2x16GB sticks and as the notebook only has 2 ports I now have 
> unused DDR4 SO-DIMM stick. So if buying a new toy I would like to utilize it 
> and J1900 systems use DDR3 type, so incompatible. That's the reason I have 
> been thinking about J5005s or J4005s.
> 
> I will try to test it on multicore Desktops which I have on my disposal. (Not 
> the same as I use for my play with Machinekit, these are too electrotrashy.) 
> Do you have any recommendation on how to determine which cores are connected 
> by shared cache? As datasheets are not really that informative about this 
> part.

When you have hyperthreading enabled, then on a 4 core pc the pairs would 0 & 1 
and 2 & 3.

> 
> I cannot say that I am knowledgeable enough about your accident, so I will 
> ask full force: are these POSIX threads in RT kernel behaving the same as in 
> vanilla kernel? Would you be able to reach this result on the vanilla kernel?
> 
> C.
> 
> Dne pátek 8. března 2019 4:18:45 UTC+1 John Morris napsal(a):
>> 
>> I wrote the cgroups stuff, but in fact have very little experience on 
>> different systems (and understand very little the ins-and-outs of shared 
>> cache, memory banks, NUMA architecture, etc.).  I can say that on the J1900, 
>> though, where two L2 caches are each shared by two of the CPU's four cores, 
>> allowing OS processes to run on a core sharing cache with the core running 
>> the RT threads killed our excellent results, and jitter measurements 
>> returned to those for conventional configurations without CPU isolation.
>> Your guess about memory infighting seems to make sense in our tests, but if 
>> it's not too difficult, maybe it's still worth a try since your system isn't 
>> exactly the same?  Also, I don't understand your comment about the DDR4 
>> memory; is that a second stick you'd add to the J5005?  (Our J1900s have 
>> only one SODIMM.)  In any case, I'd appreciate hearing about any results on 
>> any CPU.
>> 
>> OT, we encountered one interesting result entirely by accident:  With CPU 
>> isolation on the same J1900, a misconfiguration caused POSIX thread 
>> selection instead of the intended RT_PREEMPT; however we didn't notice 
>> because we still saw the same excellent sub-7uS jitter!
>> 
>> John
>> 
>> 
>> 
>> From: machi...@googlegroups.com  on behalf of 
>> ce...@tuta.io 
>> Sent: Wednesday, March 6, 2019 9:28 PM
>> To: Machinekit
>> Subject: Re: [Machinekit] cgroups and isolating CPU’s
>> 
>> Yes, thank you. I have been reading this document since before it was merged.
>> 
>> I know that usability for me is currently zero, but I am interested in 
>> technology and development. I have one unused DDR4 stick from notebook 
>> upgrade, but the J5005 seems like no good choice as by datasheet the L2 
>> cache is shared across all cores. (So I guess memory infighting would occur.)
>> 
>> C.
>> 
>> Dne středa 6. března 2019 13:04:06 UTC+1 John Morris napsal(a):
>> Bas is right. Here's the referenced documentation in context.
>> 
>> http://<http://www.machinekit.io/docs/hal/threads-and-latency/>www.machinekit.io<http://www.machinekit.io/docs/hal/threads-and-latency/>/docs/<http://www.machinekit.io/docs/hal/threads-and-latency/>hal<http://www.machinekit.io/docs/hal/threads-and-latency/>/<http://www.machinekit.io/docs/hal/threads-and-latency/>threads-<http://www.machinekit.io/docs/hal/threads-and-latency/>and-latency<http://www.machinekit.io/docs/hal/threads-and-latency/>/<http://www.machinekit.io/docs/hal/threads-and-latency/>
>> 
>> If you have no CPUs to spare, though, this will be of no use to you.
>> 
>> John Morris
>> Dovetail Automata LLC
>> 
>> From: Bas de Bruijn
>> Sent: Thursday, February 28, 13:43
>> Subject: [Machinekit] cgroups and isolating CPU’s
>> To: ce...@tuta.io
>> Cc: Machinekit
>> 
>> 
>> So as not to hijack the thread, a new thread
>> 
>> On 28 Feb 2019, at 19:20, ce...@tuta.io wrote:
>> 
>> BTW, did someone else (than Zultron) try to use the core isolation feature 
>> to "turn on" back the step signal generation in software? My electrotrash 
>> which I use for Machinekitdoes not have cores to spare.
>> 
>> Yes, you’re probably

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

[Bas de Bruijn]

> On 6 Mar 2019, at 12:30, "schoone...@gmail.com"  wrote:
> 
> Well I can see the cause of all this, but the solution without generating a 
> warning somewhere in the package builds is far from simple.
> When this quite low level C was written, warnings were not as numerous as 
> nowadays versions of gcc generate
> and probably not top priority anyway so long as it worked.
> 
> I spent quite a long time trying various ways of removing warnings, but none 
> were satisfactory for all usages of the variable,
> across all architectures.
> 
> It essentially comes down to 32 bit and 64 bit differences in data type size.
> If you then specify a format size in a printf operation, it will always 
> generate a warning under one architecture or another.
> Assigning with a (void*) cast, will do so too, hence the making of L1 and L2 
> void * probably
> 
> The idea of the `address of` reference  was probably to prevent a warning 
> regards printf format %p requiring void **, 
> but I would think it does not return what the function wants.
> 
> In any case I have reverted the commits and removed the -Werror CFLAG for now 
> to enable packages to build.
> 
> Will take a while to filter through, not been able to test on my Mesa carded 
> machine due to other issues,
> hence reverted in its entirety.

If all has gone right, packages with the reverted offending commit should be 
built and in the apt repo.

> Just using a package prior to these commits will keep you going for now.
> 
> Thanks for the report and your testing to quickly narrow it down.
> 
> regards
>  
>> On 05/03/19 19:24, 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

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

[Bas de Bruijn]

> On 5 Mar 2019, at 12:20, destra...@gmail.com wrote:
> 
> Sorry :-)
> 
> You are absolutely right. I'm running Debian stretch with Kernel
> 
> #1 SMP RPEEMPT RT Debian 4.9.144-3.1 (2019-02-19)
> 
> on an conventional PC.
> 
> 1. It worked with Machinekit 0.1.1543327459.gite758f69-1~stretch. It doesn't 
> work with 0.1.1551530147.git6a143ec-1~stretch.
> I tried to launch it without hm2_pci config string, but it doesn't work.
> 
> 2. I started it from the terminal window, with 'export DEBUG=5' (see attached 
> log file), same problems.
> 
> 3. Error text from bash is attached (output.log). Makes no sense for me.
> 
> 4./5. I've search linuxcnc.log for clues. Problems start for me with the 
> above mention permission denied error.

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?

> 
> 6. I've searched the forum again, and I found a similar problem. 
> (https://groups.google.com/forum/#!searchin/machinekit/hm2_pci/machinekit/fahrSvm6b5c/vhK8S_NOEQAJ)
>  with no solution yet as far as I can see. Please excuse for not answering in 
> this topic, I simply didn't find it on my first search iteration.
> 
> 7. I cannot see anything related on the issue tracker.
> 
> Thank you very much
> Best regards
> 
> 
> Am Dienstag, 5. März 2019 11:12:29 UTC+1 schrieb Schooner:
>> 
>> 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, dest...@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+...@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.
> 
> 

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

[Bas de Bruijn]

> On 2 Mar 2019, at 06:14, mugginsac  wrote:
> 
> OK, I got machinekit loading on my BeBoPr-Bridge, my CRAMPS board and my 
> Xylotex-DB25.
> I posted another set of edits of the configs for the three of them. I posted 
> them to machinekit-cnc this time.
> Basically, I think the configs were what I posted previously to machinekit, 
> but somehow either I missed some things
> or they didn't get transferred from machinekit to machinekit-cnc. Either way 
> they are there now (as soon as someone approves the pull request).
> The Xylotex is running my X2 CNC-MiniMill and it now boots in a reasonable 
> time. It also jogs nicely and homes correctly.
> So, thank you Schooner, Bas, Charles, Cern and anyone else I forgot.

Glad you got it working.
PR is being tested and will be merged quickly
Bas

-- 
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: cgroups and isolating CPU’s

[Bas de Bruijn]

> On 28 Feb 2019, at 20:24, c...@tuta.io wrote:
> 
> Yes, sorry for the hijack. It was just an out-of-the-blue idea which popped 
> in my head in reaction to Schooner's post.
> 
> And yes, I meant that commit.
> 
> I remember from my LinuxCNC days that CPU hogging, as you aptly named, used 
> be the thing. (Not so sure now as I don't follow that project closely, only 
> the forum.) And I quite liked the multicore, multi-instance granularity of 
> Machinekit.
> 
> However, isolating one(/more) CPU core for the special process of software 
> step generation doesn't seem so bad.

indeed, as long as you still have cpu’s left for the rest of your system. CPU 
hogging seems really silly, you buy a PC and only use 50% (or 25% depending on 
how many cpu’s you bought)

> Zultron tested it on J1900 (I think) which is board everybody is composing 
> odes about (at least on LinuxCNC forum) but it's little old and harder to 
> get. So it would be interesting to try it on J5005 or J40-something based 
> boards, which are around 100 euros.

hmm, I’m not so sure about that. It’s widely used in industrial setups. I’ve 
used a couple, and although they are not the fastest. I ran a mesa 5i25+7i76 so 
there was not a real issue w.r.t. latency. (this was before the cgroups 
option). I had no bad experiences which ultimately means that it’s a good 
experience :)
https://www.logicsupply.com/catalogsearch/result/?q=J1900 
<https://www.logicsupply.com/catalogsearch/result/?q=J1900>
I think there are other brands/options available.

Personally I prefer to spend some extra money and buy something that (is known 
to) work. When you run into trouble/unexpected then the hours working on it and 
billing that to a customer or chucking up those hours for yourself is not worth 
the “savings”. And generally, if I have something is good enough and works, I 
tend to stick with it. (Just my take)

Bas

> 
> Cern.
> 
> Dne čtvrtek 28. února 2019 19:43:34 UTC+1 Bas de Bruijn napsal(a):
> So as not to hijack the thread, a new thread
> 
> On 28 Feb 2019, at 19:20, ce...@ <>tuta.io <http://tuta.io/> wrote:
> 
>> BTW, did someone else (than Zultron) try to use the core isolation feature 
>> to "turn on" back the step signal generation in software? My electrotrash 
>> which I use for Machinekitdoes not have cores to spare.
> 
> Yes, you’re probably referring to this?
> https://github.com/machinekit/machinekit/pull/1426 
> <https://github.com/machinekit/machinekit/pull/1426>
> 
> Although i dont use software step generation. The latency obtained is very 
> good (6-7 us).
> 
> What was done here is to force the thread to run on designated cpu’s. 
> Because these cpu’s were isolated during startup (isolcpus= kernel parameter) 
> there are no other processes running on these cpu’s.
> These cpu’s must be the pair that share their L2 cache, or hyperthreading 
> should be disabled and that cpu used.
> 
> A setup that was historically used with iolcpus= kernel parameters was to run 
> everything on 1 cpu (disabling all but one), so that the cpu was hogged and 
> that got good latency results.
> 
> This cgroups setup is the other way around, you’ll only run HAL on the 
> isolated cpu’s, the /RT cpuset.
> 
> I’m no expert on this so there might be some more clarification needed from 
> the experts :)
> 
> Bas
> 

-- 
website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
https://github.com/machinekit
--- 
You received this message because you are subscribed to the Google Groups 
"Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to machinekit+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.

[Machinekit] cgroups and isolating CPU’s

[Bas de Bruijn]

So as not to hijack the thread, a new thread

> On 28 Feb 2019, at 19:20, c...@tuta.io wrote:
> 
> BTW, did someone else (than Zultron) try to use the core isolation feature to 
> "turn on" back the step signal generation in software? My electrotrash which 
> I use for Machinekitdoes not have cores to spare.

Yes, you’re probably referring to this?
https://github.com/machinekit/machinekit/pull/1426

Although i dont use software step generation. The latency obtained is very good 
(6-7 us).

What was done here is to force the thread to run on designated cpu’s. 
Because these cpu’s were isolated during startup (isolcpus= kernel parameter) 
there are no other processes running on these cpu’s.
These cpu’s must be the pair that share their L2 cache, or hyperthreading 
should be disabled and that cpu used.

A setup that was historically used with iolcpus= kernel parameters was to run 
everything on 1 cpu (disabling all but one), so that the cpu was hogged and 
that got good latency results.

This cgroups setup is the other way around, you’ll only run HAL on the isolated 
cpu’s, the /RT cpuset.

I’m no expert on this so there might be some more clarification needed from the 
experts :)

Bas

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

[Bas de Bruijn]

> On 28 Feb 2019, at 07:19, bradley.j.wilkin...@student.uts.edu.au wrote:
> 
> Hey Bas, really appreciate your help with this.
> I've looked for man pages on scarakins and hal_gpio and neither seem to have 
> one yet. I suppose because they are still new in the project.

Hi Bradley,
These files are nothing but new. Scarakins if from around 2003, and hal_gpio 
from around 2012. (which dates are in the source files :) )

> So I looked at the .c source files on github to try and find out how they 
> work. Looking at scarakins.c the comments between line 40 and 74 seem to be 
> the important information, while for hal_gpio.c the relevant information 
> about which pins are available is in lines 59 and 60.
> As how to call them for machinekit, the variables that are to be used are 
> created in the .ini file, while any of the variables that will be connected 
> to physical pins will be declared in a .hal file.
> Does this sound like I'm starting to understand things?

Machinekit’s best feature, the HAL, is the realtime environment where you 
create the logic. This you do by “configuring", as opposed to “coding”. You 
load these software pieces and have a function executed. That’s where the 
thread is for, it executes functions you added to that thread, one by one. See 
it as a chain, where each function is a link.

So in theory you can start from an empty HAL, and (un)load pieces in realtime, 
step by step, adding threads, components/instances and signals as you like.
When you load a .hal file, the lines are executed as you would do it manually 
in an empty HAL, thus creating the configuration for you.

The INI files are just configuration data. Meaning that hal/ini files have 
nothing of variables etc.
so for example, sim.ini contains this line: 
https://github.com/machinekit/machinekit/blob/master/configs/sim/axis/axis.ini#L104
 
<https://github.com/machinekit/machinekit/blob/master/configs/sim/axis/axis.ini#L104>
 which tells that it will load core_sim.hal which is found here 
https://github.com/machinekit/machinekit/blob/master/configs/common/core_sim.hal
 
<https://github.com/machinekit/machinekit/blob/master/configs/common/core_sim.hal>

if you look at this line: 
https://github.com/machinekit/machinekit/blob/master/configs/common/core_sim.hal#L9
 
<https://github.com/machinekit/machinekit/blob/master/configs/common/core_sim.hal#L9>
`loadrt [EMCMOT]EMCMOT base_period_nsec=[EMCMOT]BASE_PERIOD 
servo_period_nsec=[EMCMOT]SERVO_PERIOD num_joints=[TRAJ]AXES kins=trivkins 
tp=tp`
would have been exactly the same as this:
`loadrt motmot base_period_nsec=0 servo_period_nsec=100 num_joints=3 
kins=trivkins tp=tp`
which you could have loaded manually
loading the values from the ini file:
https://github.com/machinekit/machinekit/blob/master/configs/sim/axis/axis.ini#L80-L93
 
<https://github.com/machinekit/machinekit/blob/master/configs/sim/axis/axis.ini#L80-L93>
https://github.com/machinekit/machinekit/blob/master/configs/sim/axis/axis.ini#L123
 
<https://github.com/machinekit/machinekit/blob/master/configs/sim/axis/axis.ini#L123>

To get a bit of an understanding what’s happening in HAL (a mini HAL primer), 
try the following:
open a new terminal and open an interactive HAL session by typing
export DEBUG=5
halrun -I
have a look at an example session I recorded for you
https://asciinema.org/a/230495

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

[Bas de Bruijn]

> On 28 Feb 2019, at 01:04, bradley.j.wilkin...@student.uts.edu.au wrote:
> 
> Perhaps I should have loaded that and it would prevent some of the errors 
> generated later in the file.

Yes, load it

> 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.
> Thanks for the reply C.

It applies for the motion component.
So load it. Even a sim configuration has a motion component. Not much to do 
with the chosen hardware.

In your prev mail your output:

> On 28 Feb 2019, at 00:03, bradley.j.wilkin...@student.uts.edu.au wrote:
> 
> hal_add_funct_to_thread:231 HAL error: function 'motion-command-handler' not 
> found

Here’s your problem.
Almost always a problem can be found in the linuxcnc.log output. The rest is 
pretty useless imo.

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

[Bas de Bruijn]

> On 27 Feb 2019, at 18:53, Condit Alan  wrote:
> 
> What is the url for the repository?

https://github.com/machinekit/machinekit

I think we’re talking about the packages :)
That one is here:
http://deb.machinekit.io/debian/pool/main/m/machinekit/


> 
>> On Feb 26, 2019, at 11:14 PM, schoone...@gmail.com wrote:
>> 
>> 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 a topic in the 
>> Google Groups "Machinekit" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/machinekit/twyuwZByyoA/unsubscribe.
>> To unsubscribe from this group and all its topics, 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.

-- 
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] configure for delta printer

[Bas de Bruijn]

> On 27 Feb 2019, at 18:30, mngr  wrote:
> 
> I had a ini and hal file working for this machine. Now I have copied every 
> configuration parameter to the new one, but the machine is behaving 
> differently.
> In particular delta_r and cf_rod, the values that were working in the old 
> configuration doesn't work in the new one.
> Maybe they are interpreted as inches instead of millimiters?

Why would that be?

You should tell what’s happening, describe what’s going on cause we can’t see 
or guess what your situation is.
Try to narrow down first.
Check HAL to see the pins (your offsets rod length and delta radius) and make 
sure they are what you expect.


> 
> 
> 
> Il giorno mercoledì 27 febbraio 2019 15:02:28 UTC+1, mngr ha scritto:
>> 
>> Thank you Bas!
>> 
>> Il giorno mercoledì 27 febbraio 2019 11:30:13 UTC+1, Bas de Bruijn ha 
>> scritto:
>>> 
>>> 
>>> 
>>>> On 27 Feb 2019, at 11:02, mngr  wrote:
>>>> 
>>>> Hi,
>>>> 
>>>> I want to tweak this configuration ( 
>>>> https://github.com/machinekit/machinekit/tree/master/configs/ARM/BeagleBone/Fabrikator-Mini-CRAMPS
>>>>  ) to work for my 3d-printer, which is a delta.
>>>> In normal hal configuration there is
>>>> 
>>>> #loadrt trivkins
>>>> loadrt lineardeltakins
>>>> 
>>>> But I cannot find its equivalent in python hal, can you please help me?
>>> 
>>> from machinekit import rtapi as rt
>>> rt.loadrt(‘lineardeltakins’)
>>> 
>>> You can also have a look at github.com/machinekoder/rostock-cramps to see 
>>> some more examples
>>> 
>>>> mngr
> 
> -- 
> website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
> https://github.com/machinekit
> --- 
> You received this message because you are subscribed to the Google Groups 
> "Machinekit" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to machinekit+unsubscr...@googlegroups.com.
> Visit this group at https://groups.google.com/group/machinekit.
> For more options, visit https://groups.google.com/d/optout.

-- 
website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
https://github.com/machinekit
--- 
You received this message because you are subscribed to the Google Groups 
"Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to machinekit+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.

Re: [Machinekit] configure for delta printer

[Bas de Bruijn]

> On 27 Feb 2019, at 11:02, mngr  wrote:
> 
> Hi,
> 
> I want to tweak this configuration ( 
> https://github.com/machinekit/machinekit/tree/master/configs/ARM/BeagleBone/Fabrikator-Mini-CRAMPS
>  ) to work for my 3d-printer, which is a delta.
> In normal hal configuration there is
> 
> #loadrt trivkins
> loadrt lineardeltakins
> 
> But I cannot find its equivalent in python hal, can you please help me?

from machinekit import rtapi as rt
rt.loadrt(‘lineardeltakins’)

You can also have a look at github.com/machinekoder/rostock-cramps to see some 
more examples

> mngr

-- 
website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
https://github.com/machinekit
--- 
You received this message because you are subscribed to the Google Groups 
"Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to machinekit+unsubscr...@googlegroups.com.
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.

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

[Bas de Bruijn]

> On 27 Feb 2019, at 06:03, bradley.j.wilkin...@student.uts.edu.au wrote:
> 
> So I have been looking into the configuration a bit more. Looking at various 
> config files I have decided that the simplified version of my machine is a 
> SCARA robot on it's side.
> I have subsequently found a .ini file for a SCARA robot at 
> github.com/sliptonic/gypsy/gypsy.ini and gypsy.hal. I have also found 
> information about the hardware driver and configuration for a Raspberry Pi at 
> github.com/machinekit/machinekit/blob/master/src/hal/drivers/hal_gpio_demo.hal
>  and hal_gpio.c. I was trying to configure the required configuration files 
> from these examples but even though I have these examples plus the websites 
> and manuals, I still don't have much of a clue about what each part of the 
> files do.
> From the attached error message it seems that I have not loaded a required 
> part of the rtapi as the calls to rtapi_msgd and rtapi_app are failing.
> Can anyone point me at what I'm doing wrong?

Hi,

The info you provided does not show us what actually happens.
Please do “export DEBUG=5” in the terminal before running machinekit, and then 
first look at /var/log/linuxcnc.log and if you can’t find what’s going on paste 
the content of your session to a github gist, or pastebin.
Have a look at this too: http://www.machinekit.io/docs/getting-help/ 
<http://www.machinekit.io/docs/getting-help/>

Bas

-- 
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] PRU development helper scripts/tools for Machinekit?

[Bas de Bruijn]

> On 25 Feb 2019, at 16:04, Damien Dando  wrote:
> 
> Thanks Charles!
> 
> In the end I did recompile the all Machinekit on BBB, took a while but it 
> eventually worked and I got the dev. env. working now.
> 
>> You may also want to look at the timer/capture modules, both in the 
>> ARM system (with Linux drivers) and there's one module within the PRU 
>> domain.  You can use these to time pulses and you will get several 
>> orders of magnitude better accuracy (~10 nS) vs. trying to monitor the 
>> signal with PRU software (~1-10 uS), but that may or may not be 
>> important depending on the PWM frequency range.
> 10uS is already overkill for my needs ;)
> I'm reading feedback signal from ClearPath motors and the PWM frequency is 
> only 50Hz. Also I'm using regular GPIO inputs because there is too much 
> constraint with dedicated PRU inputs pinout.
> Since I saw quite few video with people using those same ClearPath motors on 
> their CNC, I'm sure many would benefit from having this feature in Machinekit.
> 
> Also I would be happy to contribute to Machinekit project so I was wondering 
> what are requirements/process to add a feature/push request to Machinekit 
> official source code.

Hi Damien,
Have a read thru this:
http://www.machinekit.io/community/contributing/

> 
> In order to integrate it at best into Machinekit source code, that would be 
> great to have feedback on some question:
> @Charles: As it seem you have done a lot of work in the hal_pru_generic 
> driver, your feedback would be valuable :)
> 
> Since I'm not using dedicated PRU inputs, reading a regular GPIO input pin 
> takes ~170ns (~190ns for GPIO bank 0). For this reason, I aim to read GPIO 
> bank(s) not more that once per pru period and only if needed.
> 
> I see 2ways of doing that:
> read GPIO inputs "globally" (in similar way as it is done for GPIO outputs in 
> pru_wait.p). This requires to add some code in pru_wait.p and/or 
> pru_generic.p and therefore extends a bit the overall pru period. The major 
> advantage is that it would allow any others hal pru "modules" to use any GPIO 
> inputs (the hal pru encoder could then be updated to work also with regular 
> GPIO inputs).
> read GPIO inputs "locally" in the PWM reader pru task I'm implementing. The 
> drawback we will need to re-read GPIO input bank in every hal pru "module" 
> that use them and therefore wasting PRU period time.
> I see the first solution as the best one.
> Looking further, I saw that there is no much unused/free space in PRU 
> register (r0-32), there are pretty much all used for something. However, I 
> thought about this solution (using GPIOn_Clr and GPIOn_Set):
> every time a PRU module/task want to read a GPIO pin, it set the 
> corresponding bit both GPIOn_Clr and GPIOn_Set registers. (I believe pru 
> module/task using GPIO as output never set both GPIOn_Clr and GPIOn_Set for 
> the same pin at the same time since that would be a non sense).
> somewhere around pru_wait.p check if the result of logical AND (GPIOn_Clr + 
> GPIOn_Set) differs from 0. If it is then, perform a "long" (~170ns) reading 
> on GPIOn and store the result in GPIOn_Set. To avoid conflict with other GPIO 
> outputs, only store bits/pins where a read was requested. Then the PRU 
> module/task that requested the reading can read the pin state in GPIOn_Set on 
> the next pru period.
> or maybe there is some easier solution allocating/using PRU RAM instead of 
> direct PRU register r0-32 (GPIOn_Clr / GPIOn_Set)...
> What are you thought? Do you have any better implementation idea/suggestion?
> 
> /Damien
> 
> Le dimanche 17 février 2019 16:07:02 UTC+1, Charles Steinkuehler a écrit :
>> 
>> On 2/17/2019 8:31 AM, Damien Dando wrote: 
>> > Hi, 
>> > 
>> > Background: 
>> > I'm building a CNC Lathe (see video here ), 
>> > I 
>> > use ClearPath motors to control Z axis and the spindle. Those motors can 
>> > be configured to give torque feedback by outputting a PWM signal. I want 
>> > to 
>> > be able to read the torque info within Machinekit in real time so I could 
>> > display it but also take actions like trigger emergency stop if the torque 
>> > goes above certain threshold. 
>> > 
>> > I have started digging in the machinekit PRU code to develop some module 
>> > to 
>> > read a PWM signal. 
>> > I'm not stuck and I'm confident I will eventually manage to do all what I 
>> > want but if some have already work with the PRU they might have some 
>> > answer 
>> > to those question that would save me quite some time: 
>> > 
>> >- Is there some (simple) way to test the PRU binary (pru_generic.bin) 
>> >separately before doing the integration in Machinekit? (like 
>> > some 
>> >script that configure the PRU/RAM shared memory the same way as 
>> >the hal_pru_generic driver does?) 
>> 
>> Just start a HAL instance and manually (or use a small HAL file or 
>> script) load the hal_pru_generic driver with "disabled=1".  This will 
>> 

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

[Bas de Bruijn]

> On 26 Feb 2019, at 23:32, 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?

I dont know specifics, but something like 1 to 2 hrs.

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

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

[Bas de Bruijn]

> 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] Re: Issues with new install

[Bas de Bruijn]

> On 16 Feb 2019, at 05:28, johannes.fasso...@gmail.com wrote:
> 
> This turned out to be typo on my own part. But that is not the problem that 
> is preventing using the Mesa 7i80 cards that I have from working with machine 
> kit.
> 
> 

Hi Johannes,

I dont have the 7i80 so i’m not versed in the details.

But first things first.
It seems you don’t build in the same way as in the example in the documentation.
Can you build according these instructions?

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

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

[Bas de Bruijn]

> On 15 Feb 2019, at 13:23, "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 AM 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  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.

-- 
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] testing BBB with Xylotex-DB25 step not changing directions

[Bas de Bruijn]

> On 30 Dec 2018, at 05:53, mugginsac  wrote:
> 
> I have a BBB with a Xylotex-DB25 cape and controller box with a single motor 
> hooked up for testing.
> When I press + or - to jog the motor spins the same direction.
> My control box has 3 Superior SS2000MD4 drives in it (old technology). It 
> requires 25000ns for step, step set up or pause.
> Here are links to my Xylotex.ini and Xylotex.hal
> 
> I have Linuxcnc setup on another computer with the same settings as far as I 
> can tell and it reverses correctly.
> So I have the controller working with Linuxcnc but not with Machinekit.
> 
> Can anyone see anything obvious in the .ini or .hal files?

This sounds similar to a question of last week.
https://groups.google.com/forum/m/#!topic/machinekit/2pLBaJv-rw8
Please check if this is the same problem.

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

[Bas de Bruijn]

> On 29 Dec 2018, at 09:31, "schoone...@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
> 
> 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: 
>> uninitialized urandom read (16 bytes read, 2 bits of entropy available)
>> Dec 26 18:43:30 beaglebone kernel: [   52.999288] EXT4-fs (mmcblk1p1): 
>> mounted filesystem with ordered data mode. Opts: (null)
>> Dec 26 18:43:30 beaglebone kernel: [   53.569319] ip_tables: (C) 2000-2006 
>> Netfilter Core Team
>> Dec 26 18:43:30 beaglebone kernel: [   55.098407] EXT4-fs (mmcblk1p1): 
>> re-mounted. Opts: errors=remount-ro
>> Dec 26 18:43:32 beaglebone kernel: [   62.508226] nf_conntrack version 0.5.0 
>> (7787 buckets, 31148 max)
>> Dec 26 18:43:32 beaglebone kernel: [   62.766767] random: nonblocking pool 
>> is initialized
>> 
>> Which seems 

Re: [Machinekit] Re: Having Issues with Following Errors

[Bas de Bruijn]

> On 28 Dec 2018, at 16:16, Matthew  wrote:
> 
> Yes but which signals should I be watching at what frequency?  The tutorial 
> just goes over basic interface stuff that is mostly obvious playing with the 
> interface.  
> 
> Thanks!

You asked for a tutorial. The links show you how to work with the scope. After 
that it’s depending on what you’re after.

Start like pcwcol said, with one or more following error pins, set a trigger 
level and see if you can get something reproducable.

Bas

-- 
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: Having Issues with Following Errors

[Bas de Bruijn]

> On 28 Dec 2018, at 05:27, Matthew  wrote:
> 
> I increased the P term to 1000 with no change.  I'd like to try to plot the 
> error with halscope... any idea how to do that?  :-)  I looked at halscope 
> and googled a bit... is there a good tutorial somewhere?

Yes there is. One of the very first links that showed up in my Google search.
Remember that you have to click on the link ;)

http://linuxcnc.org/docs/html/hal/tutorial.html#_halscope

Or if you search the machinekit docs
http://www.machinekit.io/docs/index-HAL/

See section “Halscope”
http://www.machinekit.io/docs/hal/tutorial/#halscope-a-id-sec-tutorial-halscope-a

> 
> Thanks!
> 
> 
>> On Thursday, December 27, 2018 at 7:37:17 AM UTC-8, pcwcol wrote:
>> 
>> 
>>> On Tuesday, December 25, 2018 at 4:42:28 PM UTC-8, Matthew wrote:
>>> The error I usually get is: joint 1 following error
>>> 
>>> 
 On Tuesday, December 25, 2018 at 3:14:55 PM UTC-8, Matthew wrote:
 I recently finished putting together my CNC router using the Beaglebone 
 Black, a 5 axis breakout board, HY-268-N6 drivers, and NEMA23 steppers.  
 Since I received assistance with getting my steppers moving in the correct 
 directions (my earlier post on this forum), everything works great for 
 jogs.  I can jog any axis at 120 in/min without problems.  The issues come 
 when I try to run a gcode file through it.  No matter how slow I set the 
 feeds, it seems like I get following errors.  I've googled the issue and 
 tried:
 
 1. Increasing the min_ferror and ferror values (up to 0.5/1).  
 
 2. Decreasing the pru_period to 5000.
 
 3. Increasing or decreasing the DEFAULT_VELOCITY and MAX_LINEAR_VELOCITY 
 values.  Goal is for a max of 120 in/min but plan to run around 25-50% 
 depending on what I'm working on.
 
 4. Increasing or decreasing the MAX_VELOCITY and MAX_ACCELERATION for each 
 axis (although it seems like the y-axis is usually the one giving me 
 errors).  I've been keeping the stepgen values 20-25% higher than the max 
 velocity/acceleration values.
 
 5. I adjusted the microstepping to lower the steps per inch scale value.  
 Didn't seem to make any difference.  I'm currently at 1/2 stepping I 
 believe.
 
 6.  I've played with the driver timings (DIRSTEP, DIRHOLD, STEPLEN, 
 STEPSPACE) but they didn't seem to change much.  The values are high due 
 to the cheap drivers I'm using but they work just fine when jogging...
 
 Any thoughts?  I've still got my configuration files at the following 
 links (ignore the hal_bb_gpio values - I've corrected the pins since 
 posting the files):
 
 Xylotex.hal: https://pastebin.com/UNtgPpyx
 Xylotex-axis.ini: https://pastebin.com/u5Ba6ULH
 Xylotex.postgui.hal: https://pastebin.com/NFHf6Px9
 
 Thanks for looking!
 
 ~Matthew
>> 
>> 
>> You might try increasing the P term to 1000 
>> 
>> The current P term of 50 with a maxerror setting of .001 means the maximum 
>> correction 
>> applied to velocity is .050 IPS which may not be sufficient
>> 
>> Another thing to try is plotting the following error with halscope to see 
>> whats going wrong
> 
> -- 
> 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

[Bas de Bruijn]

> On 26 Dec 2018, at 20:51, mugginsac  wrote:
> 
> Bas and Schooner,
> 
> I had seen those errors and had even googled some of them but hadn't yet 
> figured out whether the problem was on my Mac or the BBB. I got those 3 libs 
> on the BBB and that fixed the problem.

Great to hear it was solved!

> 
> Thank you both so much,
> Alan

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

[Bas de Bruijn]

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

Re: [Machinekit] Machinekit Advanced HAL Tutorial

[Bas de Bruijn]

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:
> 78float IN  5  siggen.0.amplitude 
> 0.10--l-
> 78bit   OUT  TRUE  siggen.0.clock 
> --l-
> 78float OUT 0.8441676  siggen.0.cosine
> 0.10--l-
> 78float IN  1  siggen.0.frequency 
> 0.10--l-
> 78float IN  0  siggen.0.offset
> 0.10--l-
> 78float OUT  2.78  siggen.0.sawtooth  
> 0.10--l-
> 78float OUT -4.922822  siggen.0.sine  
> 0.10--l-
> 78float OUT 5  siggen.0.square
> 0.10--l-
> 78float OUT  0.56  siggen.0.triangle  
> 0.10--l-
> 78s32   OUT  5261  siggen.0.update.time   
> 
> 78s32   I/O 65155  siggen.0.update.tmax   
> 
> 78bit   OUT FALSE  siggen.0.update.tmax-inc   
> 
> 66s32   OUT999411  test-thread.curr-period
> 
> 66s32   OUT  5261  test-thread.time   
> 
> 66s32   I/O 65155  test-thread.tmax   
> 
> 
> halcmd: 
> 
> And when I attempt to see the parameters, nothing shows up:
> 
> halcmd: show param
> Parameters:
>  CompInst 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 parameters, nor are 
there signals in your setup.

The term Signal refers to a type which connects 2 pins. Although you think your 
siggen component creates signals (sine, cosine, square, saw, triangle) these 
are not the hal types we call “signal”

Bas


> 
> Thanks and best regards,
> 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 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] EtherCat / CANopen for lathe retrofit

[Bas de Bruijn]

Hi Frederic,

> On 11 Dec 2018, at 07:43, Frederic Rible  wrote:
> 
> Hello, 
> 
> After having battled with original analog drives, we are considering 
> switching to EtherCat servo drives for our Mori-Seiki SL-0 lathe retrofit. 
> Any information about EtherCat maturity under MK running on a PC? 
> Also, we are studying CANopen alternative, but EtherCat looks more promising: 
> any feedback? 

We’re running the LCEC (LinuxCNC Ethercat Component) in a non-CNC project, and 
Ethercat works fine.
I’d not go towards CANOpen because of the bandwidth and there’s no real driver 
out there.

You could also check out the STMBL project. https://github.com/rene-dev/stmbl 
<https://github.com/rene-dev/stmbl>

Bas

> 
> Thanks. 
> Frederic 
> https://www.electrolab.fr/
> https://wiki.electrolab.fr/Tour:MoriSeiki:SL0
> http://cnc.f1oat.org <http://cnc.f1oat.org/>
> 
> 
> 
> -- 
> website: http://www.machinekit.io <http://www.machinekit.io/> blog: 
> http://blog.machinekit.io <http://blog.machinekit.io/> github: 
> https://github.com/machinekit <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 
> <mailto:machinekit+unsubscr...@googlegroups.com>.
> Visit this group at https://groups.google.com/group/machinekit 
> <https://groups.google.com/group/machinekit>.
> For more options, visit https://groups.google.com/d/optout 
> <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] Beaglebone stepper motor as spindle

[Bas de Bruijn]

> On 3 Dec 2018, at 21:02, Gediminas Dirma  wrote:
> 
> My final goal would be to have threading with lathe. So i am trying to find 
> some way how this could be possible done. Because i didnt find much 
> information about encoders or examples on beaglebone and machinekit how to 
> use them.

I don’t have a lathe, so I can’t help you here.
You should have a search thru the docs at http://www.machinekit.io/docs
http://www.machinekit.io/docs/lathe/lathe-user/
Spindle synchronized motion


> 
> 2018 m. gruodis 3 d., pirmadienis 15:53:44 UTC+2, Bas de Bruijn rašė:
>> 
>> 
>> 
>> > 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.

-- 
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] Beaglebone stepper motor as spindle

[Bas de Bruijn]

> 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] Mesa 6i25 Smart Serial ports work with halcmd HAL-file, but not with python-HAL

[Bas de Bruijn]

> On 28 Nov 2018, at 21:32, destra...@gmail.com wrote:
> 
> Thank you so much Bas,
> indeed we forgot to add the write and watchdog functions to our thread!

Great!

> Best regards
> Dennis
> 
> Am Mittwoch, 28. November 2018 16:19:56 UTC+1 schrieb Bas de Bruijn:
>> 
>> 
>> 
>> On 28 Nov 2018, at 15:01, dest...@gmail.com wrote:
>> 
>>> Hello everyone,
>>> we have the following problem with machinekit (latest version from 
>>> repositories, debian stretch):
>>> 
>>> If we launch machinekit with an original (linuxcn-style) HAL-file:
>>> 
>>> loadrt hostmot2
>>> loadrt hm2_pci config=" num_encoders=1 num_stepgens=4 
>>> sserial_port_0=00xx "
>>> 
>>> we can read out a 7i76-daughterboard digital in pin via halmeter.
>>> 
>>> On the other hand, if we use a python-HAL:
>>> 
>>> rt.loadrt('hostmot2')
>>> rt.loadrt('hm2_pci', config=' num_encoders=1 num_stepgens=4 
>>> sserial_port_0=00xx')
>>> 
>>> halmeter shows the pins, but they show only false, regardless of the actual 
>>> input value.
>> 
>> Which pins are that?
>> 
>> What does `halcmd show pin hm2_5i25.0` say?
>> 
>>> Do you have any ideas?
>> 
>> Have you inspected /var/log/linuxcnc.log after setting `export DEBUG=5` in 
>> the terminal you run your python file?
>> 
>> Have you added the read, write and pet_watchdog functions to your thread?
>> 
>> Have you started the thread?
>> 
>> Bas
>> 
>>> 
>>> 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+...@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.

-- 
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 Smart Serial ports work with halcmd HAL-file, but not with python-HAL

[Bas de Bruijn]

> On 28 Nov 2018, at 15:01, destra...@gmail.com wrote:
> 
> Hello everyone,
> we have the following problem with machinekit (latest version from 
> repositories, debian stretch):
> 
> If we launch machinekit with an original (linuxcn-style) HAL-file:
> 
> loadrt hostmot2
> loadrt hm2_pci config=" num_encoders=1 num_stepgens=4 sserial_port_0=00xx 
> "
> 
> we can read out a 7i76-daughterboard digital in pin via halmeter.
> 
> On the other hand, if we use a python-HAL:
> 
> rt.loadrt('hostmot2')
> rt.loadrt('hm2_pci', config=' num_encoders=1 num_stepgens=4 
> sserial_port_0=00xx')
> 
> halmeter shows the pins, but they show only false, regardless of the actual 
> input value.

Which pins are that?

What does `halcmd show pin hm2_5i25.0` say?

> Do you have any ideas?

Have you inspected /var/log/linuxcnc.log after setting `export DEBUG=5` in the 
terminal you run your python file?

Have you added the read, write and pet_watchdog functions to your thread?

Have you started the thread?

Bas

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

[Bas de Bruijn]

> On 26 Nov 2018, at 00:43, 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:
>> 
>> machinekit
>> MACHINEKIT - 0.1
>> Machine configuration directory is 
>> '/home/machinekit/machinekit/configs/sim.axis'
>> Machine configuration file is 'axis.ini'
>> Starting Machinekit...
>> rtapi_msgd command:  /usr/libexec/linuxcnc/rtapi_msgd --instance=0 
>> --rtmsglevel=5 --usrmsglevel=5 --halsize=524288
>> rtapi_app command:  /usr/libexec/linuxcnc/rtapi_app_rt-preempt --instance=0
>> io started
>> :0: Component 'iocontrol' ready
>> :0: Program 'io' started
>> halcmd loadusr io started
>> :0: Component 'halui' ready
>> :0: Program 'halui' started
>> core_sim.hal:5: Realtime module 'trivkins' loaded
>> core_sim.hal:7: Realtime module 'tp' loaded
>> core_sim.hal:9: insmod failed, returned -1:
>> rtapi_rpc(): reply timeout
>> See /var/log/linuxcnc.log for more information.
>> 
> 
>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.
> 
> Can't find . 'machinekit_0.1.1537365199.
> gitf63b8a2-1~stretch_i386' you suggested. 
> 
> Is Machinekit for programmers only?

Your remark above is not really helpfull nor is it constructive.

Bas

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

[Bas de Bruijn]

> On 22 Nov 2018, at 22:33, c...@tuta.io wrote:
> 
> And just to be through I have just tried to install machinekit from source 
> and gotten the same error. Command sudo make setuid made these warnings:
> 
> 
> 
> Warning:  No rate limit in rsyslogd is set.
> 
>   The 'rsyslogd' daemon drops logs when incoming at
>   higher than the rate configured by
>   'SystemLogRateLimitBurst'.  The default rate is lower
>   than Machinekit requires when running in debug mode.
> 
>   Hint:
> $ sudo cp rtapi/rsyslogd-linuxcnc.conf 
> /etc/rsyslog.d/linuxcnc.conf
> $ sudo service rsyslog restart
> 
> Warning:  no configuration for 'memlock' found
> 
>   Hint:
> $ sudo cp rtapi/shmdrv/limits.d-machinekit.conf 
> /etc/security/limits.d/machinekit.conf
> 
> 

Hi, those hints tell you what to do.
Bas


> Cern
> 
> Dne čtvrtek 22. listopadu 2018 1:59:07 UTC+1 ce...@tuta.io napsal(a):
>> 
>> 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:
>> 
>> machinekit
>> MACHINEKIT - 0.1
>> Machine configuration directory is 
>> '/home/machinekit/machinekit/configs/sim.axis'
>> Machine configuration file is 'axis.ini'
>> Starting Machinekit...
>> rtapi_msgd command:  /usr/libexec/linuxcnc/rtapi_msgd --instance=0 
>> --rtmsglevel=5 --usrmsglevel=5 --halsize=524288
>> rtapi_app command:  /usr/libexec/linuxcnc/rtapi_app_rt-preempt --instance=0
>> io started
>> :0: Component 'iocontrol' ready
>> :0: Program 'io' started
>> halcmd loadusr io started
>> :0: Component 'halui' ready
>> :0: Program 'halui' started
>> core_sim.hal:5: Realtime module 'trivkins' loaded
>> core_sim.hal:7: Realtime module 'tp' loaded
>> core_sim.hal:9: insmod failed, returned -1:
>> rtapi_rpc(): reply timeout
>> See /var/log/linuxcnc.log for more information.
>> 
>> 
>> And in linuxcnc.log
>> 
>> Nov 22 01:44:59 machinekit msgd:0: startup pid=12256 flavor=rt-preempt 
>> rtlevel=5 usrlevel=5 halsize=524288 shm=Posix cc=gcc 6.3.0 20170516  
>> version=v0.1~-~9c3423c
>> Nov 22 01:44:59 machinekit msgd:0: ØMQ=4.2.1 czmq=4.0.2 protobuf=3.0.0 
>> atomics=gcc intrinsicslibwebsockets=2.0.3
>> Nov 22 01:44:59 machinekit msgd:0: configured: sha=9c3423c
>> Nov 22 01:44:59 machinekit msgd:0: built:  Nov 14 2018 12:37:25 
>> sha=9c3423c
>> Nov 22 01:44:59 machinekit msgd:0: register_stuff: actual hostname as 
>> announced by avahi='machinekit.local'
>> Nov 22 01:44:59 machinekit msgd:0: zeroconf: registering: 'Log service on 
>> machinekit.local pid 12256'
>> Nov 22 01:44:59 machinekit rtapi:0: 2:rtapi_app:12261:user rtapi:0: cannot 
>> create core dumps - /proc/sys/fs/suid_dumpable contains 0
>> Nov 22 01:44:59 machinekit rtapi:0: 2:rtapi_app:12261:user you might have to 
>> run 'echo 1 > /proc/sys/fs/suid_dumpable' as root to enable rtapi_app core 
>> dumps
>> Nov 22 01:44:59 machinekit rtapi:0: 4:rtapi_app:12261:user rtapi: loaded 
>> from rtapi.so
>> Nov 22 01:44:59 machinekit rtapi:0: 4:rtapi_app:12261:user hal_lib: loaded 
>> from hal_lib.so
>> Nov 22 01:44:59 machinekit msgd:0: rtapi:12261:rt rtapi_app_main:195 HAL: 
>> initializing RT hal_lib support
>> Nov 22 01:44:59 machinekit msgd:0: hal_lib:12261:rt halg_xinitfv:90 HAL: 
>> initializing component 'hal_lib' type=4 arg1=0 arg2=0/0x0
>> Nov 22 01:44:59 machinekit msgd:0: hal_lib:12261:rt hal_heap_addmem:58 HAL: 
>> extending arena by 262144 bytes
>> Nov 22 01:44:59 machinekit msgd:0: hal_lib:12261:rt halg_export_xfunctfv:85 
>> HAL: exporting function 'newinst' type 2 fp=0 owner=66
>> Nov 22 01:44:59 machinekit msgd:0: hal_lib:12261:rt halg_export_xfunctfv:85 
>> HAL: exporting function 'delinst' type 2 fp=0 owner=66
>> Nov 22 01:44:59 machinekit msgd:0: hal_lib:12261:rt halg_xinitfv:271 HAL: 
>> singleton component 'hal_lib' id=66 initialized
>> Nov 22 01:44:59 machinekit msgd:0: hal_lib:12261:rt rtapi_app_main:199 HAL: 
>> RT hal_lib support initialized rc=66
>> Nov 22 01:44:59 machinekit rtapi:0: 4:rtapi_app:12261:user accepting 
>> commands at ipc:///tmp/0.rtapi.a42c8c6b-4025-4f83-ba28-dad21114744a
>> Nov 22 01:44:59 machinekit rtapi:0: 3:rtapi_app:12261:user rtapi_app:0 rea

Re: [Machinekit] Need an Assist with config

[Bas de Bruijn]

> On 18 Nov 2018, at 12:39, Pierre Auge  wrote:
> 
> Bas,
> 
> My friend, that is what we call a typo.

Yes, that was certainly a high ranking possibility :)

I was wondering (just curious ) why you use an older debian Jessie xenomai 
image, instead of the newer stretch rt-preempt one.

> Thank you, sooo much! It loaded instantly when I made the correction. 
> 
> You just saved me so much work. Now on to testing.
> 
> Pierre

Glad it worked out!

> 
>> On Sunday, November 18, 2018 at 5:38:36 AM UTC-5, Bas de Bruijn wrote:
>> Pierre,
>> 
>>> On 15 nov. 2018, at 06:55, Bas de Bruijn  wrote:
>>> 
>>> 
>>> 
>>>> On 15 Nov 2018, at 00:06, Pierre Auge  wrote:
>>>> 
>>>> https://github.com/PierreAuge/machinekit-config/blob/master/linuxcnc.log
>>>> 
>> 
>> You should look into these lines
>> https://github.com/PierreAuge/machinekit-config/blob/master/linuxcnc.log#l1120
>> 
>> Which say something about this line
>> https://github.com/PierreAuge/machinekit-config/blob/master/CRAMPS.ini#l97
>> 
>> Looks like you want a servo thread of 10kHz and on a bbbw and that's a too 
>> much I think.
>> Normally you run at 1kHz which is more than enough (look at the original)
>> https://github.com/machinekit/machinekit/blob/master/configs/ARM/BeagleBone/CRAMPS/CRAMPS.ini#l105
>> 
>> Bas
>> 
>>>> 
>>>> Bas,
>>>> 
>>>> Apologies about the back and forth. I really do appreciate you taking the 
>>>> time to help me. The linked log file should present something more useful 
>>>> now.
>>>> 
>>>> Pierre
>>> 
>>> Where did you obtain the image from
>>> What’s the output of ‘uname -a’
>>> What’s the output of ‘dmesg’
>>> 
>>>> 
>>>>> On Tuesday, November 13, 2018 at 12:52:52 AM UTC-5, Bas de Bruijn wrote:
>>>>> 
>>>>> 
>>>>> > On 12 Nov 2018, at 22:28, Pierre Auge  wrote: 
>>>>> > 
>>>>> > Now i'm getting some error outputs. and here it is. Finally: 
>>>>> > https://github.com/PierreAuge/machinekit-config/blob/master/linuxcnc.log
>>>>> >  
>>>>> 
>>>>> Looks like these are just normal messages. 
>>>>> Please in a terminal: 
>>>>> export DEBUG=5 
>>>>> 
>>>>> Then start Machinekit from that terminal: 
>>>>> machinekit & 
>>> -- 
>>> 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+...@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.

-- 
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] Need an Assist with config

[Bas de Bruijn]

Pierre,

> On 15 nov. 2018, at 06:55, Bas de Bruijn  wrote:
> 
> 
> 
>> On 15 Nov 2018, at 00:06, Pierre Auge  wrote:
>> 
>> https://github.com/PierreAuge/machinekit-config/blob/master/linuxcnc.log

You should look into these lines
https://github.com/PierreAuge/machinekit-config/blob/master/linuxcnc.log#l1120

Which say something about this line
https://github.com/PierreAuge/machinekit-config/blob/master/CRAMPS.ini#l97

Looks like you want a servo thread of 10kHz and on a bbbw and that's a too much 
I think.
Normally you run at 1kHz which is more than enough (look at the original)
https://github.com/machinekit/machinekit/blob/master/configs/ARM/BeagleBone/CRAMPS/CRAMPS.ini#l105

Bas

>> 
>> Bas,
>> 
>> Apologies about the back and forth. I really do appreciate you taking the 
>> time to help me. The linked log file should present something more useful 
>> now.
>> 
>> Pierre
> 
> Where did you obtain the image from
> What’s the output of ‘uname -a’
> What’s the output of ‘dmesg’
> 
>> 
>>> On Tuesday, November 13, 2018 at 12:52:52 AM UTC-5, Bas de Bruijn wrote:
>>> 
>>> 
>>> > On 12 Nov 2018, at 22:28, Pierre Auge  wrote: 
>>> > 
>>> > Now i'm getting some error outputs. and here it is. Finally: 
>>> > https://github.com/PierreAuge/machinekit-config/blob/master/linuxcnc.log 
>>> 
>>> Looks like these are just normal messages. 
>>> Please in a terminal: 
>>> export DEBUG=5 
>>> 
>>> Then start Machinekit from that terminal: 
>>> machinekit & 
> -- 
> 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] Need an Assist with config

[Bas de Bruijn]

> On 15 Nov 2018, at 00:06, Pierre Auge  wrote:
> 
> https://github.com/PierreAuge/machinekit-config/blob/master/linuxcnc.log
> 
> 
> Bas,
> 
> Apologies about the back and forth. I really do appreciate you taking the 
> time to help me. The linked log file should present something more useful now.
> 
> Pierre

Where did you obtain the image from
What’s the output of ‘uname -a’
What’s the output of ‘dmesg’

> 
>> On Tuesday, November 13, 2018 at 12:52:52 AM UTC-5, Bas de Bruijn wrote:
>> 
>> 
>> > On 12 Nov 2018, at 22:28, Pierre Auge  wrote: 
>> > 
>> > Now i'm getting some error outputs. and here it is. Finally: 
>> > https://github.com/PierreAuge/machinekit-config/blob/master/linuxcnc.log 
>> 
>> Looks like these are just normal messages. 
>> Please in a terminal: 
>> export DEBUG=5 
>> 
>> Then start Machinekit from that terminal: 
>> machinekit & 

-- 
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] Need an Assist with config

[Bas de Bruijn]

> On 12 Nov 2018, at 22:28, Pierre Auge  wrote:
> 
> Now i'm getting some error outputs. and here it is. Finally: 
> https://github.com/PierreAuge/machinekit-config/blob/master/linuxcnc.log

Looks like these are just normal messages.
Please in a terminal:
export DEBUG=5

Then start Machinekit from that terminal:
machinekit &


-- 
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] Need help configuring BeagleBone Black, using Probotix cape

[Bas de Bruijn]

Hi Peter,

> On 12 Nov 2018, at 02:57, peter.huer...@gmail.com wrote:
> 
> 
> I'm having trouble getting my copy of Machinekit configured on the Beaglebone 
> Black.  I am currently getting the below error:
> 
> 
> 
> 
> 
> Any suggestions would be greatly appreciated.  I installed the below build:
> 
> 
> Which was sourced from here:
> 
> https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#BBW.2FBBB_.28All_Revs.29_Machinekit
> 
Is there a reason you’ve taken the (very old) Jessie image? Why not the stretch 
image?

Bas
> If anyone can help me with this I would be eternally thankful.
> 
> 
> -- 
> 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] Need an Assist with config

[Bas de Bruijn]

Hi Pierre,

> On 12 Nov 2018, at 00:03, Pierre Auge  wrote:
> 
> This 3D printer CRAMPS config loads Axis with no errors, but hangs and 
> effectively crashes the BBBW.

And what does it say? What are the error messages?
export DEBUG=5 and start Machinekit. Then pastebin (do not attach) the session 
from /var/log/linuxcnc.log

We cannot start to guess what’s happening without some meaningful information.

> It took me a while to wrap my head around this config but I feel like it 
> should work.

Which config exactly?
Again, we’re not looking over your shoulder so you need to provide more input.

Bas

> It is a dual x/y drive system with parallel motors on the X and Y axis. 2X, 
> 2Y, 1Z, and an extruder. Similar to the MPCNC.
> 
> I've tested the standard cramps configs with the machine running with motors 
> in parallel on a single driver and everything is fine.
> 
> 
> Thanks
> -- 
> 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: GUI Linuxcnc translation

[Bas de Bruijn]

> On 7 Nov 2018, at 13:29, Federico Torresan  
> wrote:
> 
> Hi
> 
> I fallowed the procedure but I have a problem running halrun(rt module)

We can’t guess, please read the getting help section on the machinekit.io 
website

> I read many other had this problem

And what were the solutions?

> Someone know jow fix it? I used the last version of xenomai kernel
> 
> Does it could be a release problem? Maybe i should use an older version
> 
> What do you think

Personally I have not used xenomai in over 3 years. I run RT-preempt kernel 
since it’s a stock RT kernel in recent Debian distro’s. In your case, a BBB 
with a recent SD card image also has stock RT kernels from TI

I think you should take a recent working image (run Machinekit), remove the 
binaries and set up your development environment as per instructions.

> 
> Thanks fede
> 
> -- 
> 
> 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] Beaglebone machinekit stepconig problem

[Bas de Bruijn]

Hi,

Stepconf does not work for making a configuration for the Beaglebone.
It’s easier to take an existing configuration for a Beaglebone setup and modify 
for your situation.

Bas

> On 7 Nov 2018, at 11:36, Gediminas Dirma  wrote:
> 
> Hello
> 
> I am new to machinekit and i have some problems with stepconfig. After i 
> setup my configuration for lathe and i start it, it doesnt work. Then i read 
> why it stopped it says because my_lathe.hal and the line is 'setp 
> parport.0.reset-time 5000'. Than i comment this line i can launch my config. 
> So what does this line mean, can i leave it commented or maybe i should 
> change something.
> 
> Thanks for 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] Re: GUI Linuxcnc translation

[Bas de Bruijn]

> On 4 Nov 2018, at 14:57, Federico Torresan  
> wrote:
> 
> Tanks very much Schooner
> 
> So I should Rebuild the project :-(..
> 
> Is there a clear (and tested) procedure to recompile machinekit and reinstall 
> it on my Beaglebone black?? 

You should remove the packages from the BBB and build from source.

Instructions here:
http://www.machinekit.io/docs/getting-started/getting-started-platform/

You need to follow the instructions on setting up a development platform.

Bas

>  
> 
> Il giorno venerdì 2 novembre 2018 19:34:52 UTC+1, Federico Torresan ha 
> scritto:
>> 
>> Hi Everybody.. 
>> 
>> Im working with Linuxcnc installed in beaglebone black but Id like to 
>> traslate the main interface into italian language.. 
>> 
>> is it possible doing it without recompile the source.. Are there some file 
>> for editing the strings??
>> 
>> 
>> Thanks in advance..  
> 
> -- 
> 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] documentation

[Bas de Bruijn]

> On 25 Oct 2018, at 03:48, "schoone...@gmail.com"  wrote:
> 
> There is a lot of documentation, a lot is generic linuxcnc / machinekit but 
> still valid.
> eg. 
> http://www.machinekit.io/docs/index-user/  will give you block level overview
> 
> http://www.machinekit.io/docs/index-developer/  will give you details 
> including NML
> 
> > I have seen machinetalk with ZMQ and protobuf, and the structure seems 
> > clear.
> 
> Glad you think so, few others do :)
> 
> ringbuffers are just a detail, there is lots of info on the web as to how 
> they work.
> They can be used for passing asynchronous data, no handshake protocols etc.
> The accessing client can retrieve what is important to it, either the whole 
> stream or just the last piece of data for instance.
> 
> The ROS intended jplan uses them
> https://github.com/machinekit/machinekit/tree/master/src/hal/jplanner
> 
> Unfortunately the piece of s**t, google customised search engine for the 
> actual docs, has ceased working again.
> They have undoubtedly changed something in the api again.
> 
> However you just have to use some intelligent searching
> 
> Enter in a google search bar - `site:machinekit.io NML` for instance to get 
> pages of hits where NML is mentioned in machinekit docs.
> 
> The documentation website has been thoroughly harvested by google, because I 
> fed it for weeks to ensure every level was visited
> 
> regards

There are also video’s and talks that Michael Haberler gave. About gcode, 
Canon, NML and a lot of other things.

https://m.youtube.com/watch?v=Bg38894LPPg

https://m.youtube.com/watch?v=xYRNG1Yi1AM

Various subject talks from Machinekit meetups are here:

https://m.youtube.com/channel/UC3FVtrJ8U91iODq5motHMow/videos

Cheers,
Bas

> 
> 
>> On 23/10/18 20:52, mngr wrote:
>> Hi,
>> 
>> I have made a little project developed around Machinekit and now I have to 
>> do a report on the project, I think I will do an introduction to explain 
>> what does Machinekit do, and how it works.
>> That kind of documentation is currently lacking, that can be a good occasion 
>> to write some of it.
>> 
>> In this period I learned something about machinekit and the HAL, but more on 
>> the "how to use" rather than "how it works".
>> I heard often talking about ring-buffer and NML, and it is not really clear 
>> to me what they are and what they are used for. 
>> I have seen machinetalk with ZMQ and protobuf, and the structure seems clear.
>> 
>> I tried to look search in the group, or looking in the code, but it is 
>> hard...
>> I am not expert enough to write that documentation by myself, can you help 
>> me in writing it?
>> First question would be: how do you think it should be structured?
>> 
>> mngr
>> -- 
>> website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
>> https://github.com/machinekit
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "Machinekit" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to machinekit+unsubscr...@googlegroups.com.
>> Visit this group at https://groups.google.com/group/machinekit.
>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
> https://github.com/machinekit
> --- 
> You received this message because you are subscribed to the Google Groups 
> "Machinekit" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to machinekit+unsubscr...@googlegroups.com.
> Visit this group at https://groups.google.com/group/machinekit.
> For more options, visit https://groups.google.com/d/optout.

-- 
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: NGCWriter is now in Cura Plugin Repository

[Bas de Bruijn]

> On 15 Oct 2018, at 09:14, mngr  wrote:
> 
> I don't get it, what is the difference between .ngc and .gcode files?
> I am currently just changing the extension

Only the extension. It’s just a text file.
Bas

> 
> Il giorno domenica 14 ottobre 2018 20:25:18 UTC+2, Michael Brown ha scritto:
>> 
>> I have first gotton around to testing this today and I find that NGCWritet 
>> plugin seema to be missing in the latest Cura v. 3.5 Toolboxmenu --> Browse 
>> packages.
>> Also Installing an older version 3.4.1 or 3.4.0 gices an:
>> Could not connect to the Cura Package Database.
>> ...
>> Whats going on ?
>> 
>>> On Monday, 19 March 2018 20:02:36 UTC+1, Alexander Rössler wrote:
>>> I'm proud to announce that the NGCWriter plugin has made it into the 
>>> Cura plugin repository. From Cura 3.2 onward you can install NGCWriter 
>>> just by adding it via Plugins > Browse Plugins... 
>>> 
>>> The plugin generates Machinekit + Velocity Extrusion compatible ngc 
>>> GCode. 
>>> 
>>> -- 
>>> Alexander 
>>> 
> 
> -- 
> 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] executing from source, pango problems

[Bas de Bruijn]

> On 22 Sep 2018, at 19:11, mngr  wrote:
> 
> Hi everybody,
> I have compiled from source, and now I am trying to execute, machinekit 
> stars, but axis does not:
> 
> 
> MACHINEKIT - 0.1
> Machine configuration directory is '/home/pi/machinekit/configs/CRAMPS'
> Machine configuration file is 'CRAMPS.ini'
> Starting Machinekit...
> rtapi_msgd command:  /home/pi/machinekit/libexec/rtapi_msgd --instance=0 
> --rtmsglevel=1 --usrmsglevel=1 --halsize=524288
> rtapi_app command:  /home/pi/machinekit/libexec/rtapi_app_rt-preempt 
> --instance=0
> io started
> halcmd loadusr io started
> task pid=25915
> emcTaskInit: using builtin interpreter
> Traceback (most recent call last):
>   File "/home/pi/machinekit/bin/axis", line 3362, in 
> get_coordinate_font(vars.dro_large_font.get())
>   File "/home/pi/machinekit/bin/axis", line 3259, in get_coordinate_font
> glnav.use_pango_font(coordinate_font, 0, 128)
>   File "/home/pi/machinekit/lib/python/glnav.py", line 6, in use_pango_font
> import cairo, pango, pangocairo
> ImportError: No module named pango

Looks like you have a missing Python module.

> Shutting down and cleaning up Machinekit...
> Cleanup done
> Machinekit terminated with an error.  You can find more information in the 
> log:
> /home/pi/linuxcnc_debug.txt
> and
> /home/pi/linuxcnc_print.txt
> as well as in the output of the shell command 'dmesg' and in the terminal
> 
> there is some problem with pango... 
> I found this 
> https://github.com/251/shaape/commit/bc8e07fb4235a7cc6401ab4f8159466ec29cdf67
> 
> but gi.repository PangoCairo has some function defined differently from 
> pangocairo
> 
> pi@realtimepi:~/machinekit/configs/CRAMPS $ uname -a
> Linux realtimepi 4.14.66-rt40-v7 #2 SMP PREEMPT RT Mon Sep 17 21:15:46 UTC 
> 2018 armv7l GNU/Linux
> 
> I tryed installing pango, but I have found problem while compiling, and the 
> site is from 2012...
> 
> any opinion about that?
> 
> 
> -- 
> 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] Additional axis outside kinematics?

[Bas de Bruijn]

> On 8 Sep 2018, at 03:40, Daren Schwenke  wrote:
> 
> I'm not sure what that would tell me here, since I'm using tripodkins.  
> I know the additional joints move appropriately when directed to.  It's just 
> that since they are not part of tripodkins, the ABC are not output.

Hmm, well, I know that lineardeltakins work with an A Axis, 
https://github.com/machinekit/machinekit/blob/master/src/emc/kinematics/lineardeltakins-common.h#L89
https://github.com/machinekit/machinekit/blob/master/src/emc/kinematics/lineardeltakins-common.h#L130

So i took a look at the source to see how this would have to work for 
tripodkins.
These 3 lines seem to be the problem:
https://github.com/machinekit/machinekit/blob/master/src/emc/kinematics/tripodkins.c#L170

> 
> I think I'll just setup an M code to feed joint position, assuming that will 
> work.  I just liked the idea of having the 'motion complete' signal of the 
> command returning (after dwell).  
> As it stands with using the M code, I'll have to add the delay myself or add 
> something to wait for the position, at which point modifying tripodkins would 
> probably be faster.
> 
> I saw they use C in openpnp as the rotational axis.  I'm guessing that XYZ 
> normally map to rotation about axis... ABC then?  So C is rotation about Z 
> axis?
>> On Friday, September 7, 2018 at 12:44:01 AM UTC-4, Bas de Bruijn wrote:
>> 
>> 
>>> On 7 Sep 2018, at 01:04, Daren Schwenke  wrote:
>>> 
>>> So am I correct in saying that adding the extra axis to trivkins would 
>>> solve the issue also though?
>> 
>> I’d try out these kind first:
>> https://github.com/machinekit/machinekit/blob/master/src/emc/kinematics/XYZACkins.c
>> 
>> Add the 5th axis but just don’t use it. See of it works.
> 
> -- 
> 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] Additional axis outside kinematics?

[Bas de Bruijn]

> On 7 Sep 2018, at 01:04, Daren Schwenke  wrote:
> 
> So am I correct in saying that adding the extra axis to trivkins would solve 
> the issue also though?

I’d try out these kind first:
https://github.com/machinekit/machinekit/blob/master/src/emc/kinematics/XYZACkins.c

Add the 5th axis but just don’t use it. See of it works.

-- 
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] Additional axis outside kinematics?

[Bas de Bruijn]

> On 6 Sep 2018, at 12:32, Daren Schwenke  wrote:
> 
> No, just respond to G0 A.  It would be better if it wasn't coordinated 
> actually.
> I will not be moving both X Y Z and A in the same command right now.
> For now it will be just G1 X Y Z 
>  
> then G1 A 
> 
> Eventually I would like to be able to G1 X Y Z, and then now wait for it to 
> finish and do G1 A during that move, but I don't need that now.
> Worst case, I can could also just reassign this to some M code, but out of 
> the box it expects A.
> (Openpnp)

In your original question you said: 
>> > But It doesn't work though for G0 A0, G1 A180, etc... 

What exactly does not work?


If you don’t mind an extra step you could set an “analog output” (its a Hal pin 
being set by the g-code command. That hal pin you can wire up to other 
components) in hal with M67 for example. So a script to change (sed) “G1 A” to 
“M67 E0 Q”.

As long as the original G-code file is consistent then that might be the 
fastest result.

Specify the number of analog I/O (end of the line “aio”)
https://github.com/luminize/machinekit/blob/experimental-wire/configs/ARM/BeagleBone/BeBoPr-Bridge/wire-extruding/lineardelta-wire-extr.hal#L29

https://github.com/luminize/machinekit/blob/experimental-wire/configs/ARM/BeagleBone/BeBoPr-Bridge/wire-extruding/lineardelta-wire-extr.hal#L265

> 
>> On Thursday, September 6, 2018 at 6:23:14 AM UTC-4, Bas de Bruijn wrote:
>> 
>> 
>> > On 6 Sep 2018, at 11:31, Daren Schwenke  wrote: 
>> > 
>> > So I have tripod kinematics working well. 
>> > Now I added an A axis for part rotation via an rc servo now, plumbed it up 
>> > with scale and limits and such, and it works in joint mode. 
>> > I added my rotation as an axis so the planner can have a relatively good 
>> > guess as to when it will reach the actual position via setting 
>> > feedrate/max angular velocity. 
>> > 
>> > After homing, world mode works fine for X, Y, Z 
>> > But It doesn't work though for G0 A0, G1 A180, etc... 
>> > My ini has: 
>> > 
>> > AXES = 4 
>> > COORDINATES = X Y Z A 
>> > 
>> > I'm obviously missing something important here. 
>> 
>> Does your 4th Axis need to be coordinated (motion) with the other 3? 
> 
> -- 
> 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.