Hello Daren,
Thanks I also know this issue, and I also found an old topic here in the
group but there was no clear answer If it will merged soon or not. I hope
someone fix it because I would like to use it for my delta.
cheers
--
website: http://www.machinekit.io blog: http://blog.machinekit.
Hi
I would look at the commits @MachineKoder made about Nov time regards
the tooltable.
Nov 15, 11,8, 7
That seems the most likely culprit, since you are using the python bindings.
regards
On 30/12/16 22:59, Frederic RIBLE wrote:
Just upgraded one of my BBB based machine with last MK build.
Thanks, I will look at it.
I can see that status update is at least partially ok because
status.motion.feedrate reports well.
Just tried to monitor the flow with Wireshark, and I cannot find packets
related to tool table.
Looks like the tool table is no longer transmitted.
Frederic.
On 31/12/
Hi Mathias,
> On 31 Dec 2016, at 11:01, Mathias Giacomuzzi wrote:
>
> Hello Daren,
>
> Thanks I also know this issue, and I also found an old topic here in the
> group but there was no clear answer If it will merged soon or not. I hope
> someone fix it because I would like to use it for my de
Hi Andrij
> On 30 Dec 2016, at 23:49, Andrij Senyk wrote:
>
> Can you help me, where I can find the default pinout for beaglebone
> machinekit? or where I can change it?
There is no default pinout. It is up to the person making the cape.
Best place to start is to use an already existing confi
Hallo Bas,
just think on a Scara robot , you have 4 joints, how to handle:
G0 X10 Y15 Z-12
I changed a lot of code in gmoccapy to support LinuxCNC 2.8 branch, witch
includes all the joint axis stuff.
Also a Gantry is much easier to handle in Joint Axis mode.
Norbert
--
website: http://www.m
The regression is older.
It comes from
https://github.com/machinekit/machinekit/commit/5db2f31db12165302f0edbb73df507c31bbe9f81
Dated 2 Aug
Now I need to understand if I can find a workaround on QML side, or if
mkwrapper.py should be reverted.
On 31/12/2016 12:05, Frederic RIBLE wrote:
Than
from what I can tell when the temperature is set with machinekit I am
getting a reading
in F not in C when I use my laser temp reader when I set the m104 or m109
to say 100
I get a 100 in the temp display on the screen and if I set my laser to F I
get a reading of 100
I thought it was supposed
I found the bug!
An extra space to be removed in RANDOM_TOOLCHANGER keyword.
Here is a patch
diff --git a/src/machinetalk/mkwrapper/mkwrapper.py
b/src/machinetalk/mkwrapper/mkwrapper.py
index ba01d76..d908f84 100644
--- a/src/machinetalk/mkwrapper/mkwrapper.py
+++ b/src/machinetalk/mkwrapper/mk
Hello,
i added "pwmgen.make-pulses" and "pwmgen.update" and got no error.
i was trying to add pwm frequency to make my spindle quieter and also
adding pwmgen type 1 (PWM/PDM and Direction Pin) for testing but no matter
what i wrote, it always got me an error message.
i have a Beaglebone Black
where i can find guide?
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
Well done, looks like Bas has already merged it.
On 31/12/2016 17:35, Frederic RIBLE wrote:
I found the bug!
An extra space to be removed in RANDOM_TOOLCHANGER keyword.
Here is a patch
diff --git a/src/machinetalk/mkwrapper/mkwrapper.py
b/src/machinetalk/mkwrapper/mkwrapper.py
index ba01d76.
12 matches
Mail list logo