Here at Pocket NC we locked on an old version of machinekit running the 3.8
kernel when we launched our machine a couple years ago. It runs on the
Beaglebone Black. I only recently came onboard and have been trying to get
up to speed with the configuration while wrangling different pieces of
so
Thanks Bas! I've attached a more verbose log. It looks like it's something
PRU related.
On Thursday, December 14, 2017 at 12:56:20 PM UTC-7, Bas de Bruijn wrote:
>
>
> On 14 Dec 2017, at 20:06, Robert Nelson >
> wrote:
>
> On Thu, Dec 14, 2017 at 12:37 PM, John A
Found this in dmesg:
[ 30.418037] pinctrl-single 44e10800.pinmux: pin PIN103 already requested
by 48038000.mcasp; cannot claim for 4a30.pruss
[ 30.580322] pinctrl-single 44e10800.pinmux: pin-103 (4a30.pruss)
status -22
[ 30.692649] pinctrl-single 44e10800.pinmux: could not request p
Thanks Robert! I was able to start up machinekit. Now I need to track down
some other quirks... What is ktimersoftd and why is it constantly taking up
40% of the CPU? This is on a freshly installed 4.14 image (see attached).
On Thursday, December 14, 2017 at 1:33:27 PM UTC-7, Robert Nelson wrote
I'm flashing the 4.14 TI RT kernel that Robert linked earlier. I'll let you
know how it goes. Where is the image of the 4.4 TI RT kernel that you'd
like me to try? Or is there an easy what to switch out the kernel for the
image I have?
On Friday, December 15, 2017 at 5:17:49 AM UTC-7, Alexander
27;ll let
> you
> > know how it goes. Where is the image of the 4.4 TI RT kernel that you'd
> like
> > me to try? Or is there an easy what to switch out the kernel for the
> image I
> > have?
>
> Hi John,
>
> v4.14-ti-rt:
>
> sudo /opt/sc
Is there a way to switch between kinematics modules using G code in
Machinekit? The desired effect is to be able to switch between trivkins and
a 5 axis inverse kinematics module that allows for TCPC (Haas uses G234 to
enable TCPC, see https://www.youtube.com/watch?v=HxPjH4v5iEg). I've
implemen
Thanks for the advice!
I started implementing this the other day and am running into follow errors
when switching between modes using a hal pin. I found this thread on the
LinuxCNC forums which discusses the same desired behavior and the same
errors I'm encountering. It seems like they were abl
I definitely have to stick with Machinekit as I'm running the machine with
a Beaglebone. What is the nature of the changes made to LinuxCNC that
allowed this to work? Do you think I could get this going on Machinekit?
On Thursday, April 12, 2018 at 8:28:29 AM UTC-6, Schooner wrote:
>
>
> On 12/0
I was able to apply some corrections in the kinematics module after
detecting changes to the mode, the way this module is doing it (found on
the thread previously linked):
https://forum.linuxcnc.org/media/kunena/attachments/16665/xyzbc-trt-kins_2017-12-13.c
I'm having trouble, though, accounting
It looks like comp isn't installed on the latest MachineKit image based on
the 3.8 linux kernel. How can I get comp on it for compiling a kinematics
module?
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You received this message
Hmm, it's there now, so I think updating machinekit using apt-get did the
trick.
sudo apt-get install machinekit
On Thursday, April 19, 2018 at 11:18:52 AM UTC-6, jo...@allwinedesigns.com
wrote:
>
> It looks like comp isn't installed on the latest MachineKit image based on
> the 3.8 linux kern
I took a closer look at the thread I linked earlier and it looks like they
weren't as successful as I previously thought. I'm only able to switch
between modes when the rotary axes are at 0, which is the same issue they
were having in the other thread. Their solution in that thread was to write
I believe I found the culprit. While everything seems to be in order in the
motion controller, I believe the GCode interpreter still believes it's at
the previous position after a kinematics mode change. Manually executing a
g0 to the currently displayed coordinates after a change and then execu
I took a closer look at the thread I linked earlier and it looks like they
weren't as successful as I previously thought. I'm only able to switch
between modes when the rotary axes are at 0, which is the same issue they
were having in the other thread. Their solution in that thread was to write
I took a closer look at the thread I linked earlier and it looks like they
weren't as successful as I previously thought. I'm only able to switch
between modes when the rotary axes are at 0, which is the same issue they
were having in the other thread. Their solution in that thread was to write
I took a closer look at the thread I linked earlier and it looks like they
weren't as successful as I previously thought. I'm only able to switch
between modes when the rotary axes are at 0, which is the same issue they
were having in the other thread. Their solution in that thread was to write
Thanks Schooner! I'll try digging a little deeper to see if it makes sense
to go that route. For now, I think I've got it working using a combination
of custom M code commands to flip the hal pin on the kinematics module, and
remapped G codes bound to a python functions that are executed at read
ng this. Do you know how I
could find where the zero length moves are being added to the trajectory
planner and what normally prevents that from happening?
Yours and Schooner's insights have been helpful so far. Maybe we can work
together to figure out what is going on.
-John
On Satu
Hi Rob,
Thanks for taking a look! Here's some information that hopefully will get
you a predictable test case. I can reliably create the error -7 by setting
my [AXIS_0]HOME_OFFSET to 2.7499, my [AXIS_0]HOME to 2.5 and running a
program that simply moves to X 2.5:
%
G0 X2.5
%
The error that is produced in /var/log/linuxcnc.log:
user line can't have zero length! xyz start =
2.50007435e+00,2.4910e+00,-2.559125863375e-10, end =
2.5000e+00,2.4910e+00,-2.559125863375e-10
-John
On Thursday, January 24, 2019 at 12:33:02 PM UTC-7, Robert
I see in my hal file that a few settings are being pulled from my INI file,
such as:
setp [PRUCONF](DRIVER).stepgen.00.position-scale [AXIS_0]SCALE
I'd like to use halcmd or python to set
[PRUCONF](DRIVER).stepgen.00.position-scale at runtime. Is that possible?
This doesn't work:
$ halcmd setp
Ah, perfect, thank you!
On Tuesday, September 5, 2017 at 10:06:09 AM UTC-6, Bas de Bruijn wrote:
>
>
>
> On 5 Sep 2017, at 17:57, jo...@allwinedesigns.com wrote:
>
> I see in my hal file that a few settings are being pulled from my INI
> file, such as:
> setp [PRUCONF](DRIVER).stepgen.00.positio
HALTalk and remote components?
John
--
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 rec
e currently proposed system.
[1]: https://wiki.debian.org/Python/MultiArch
John
--
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&quo
esn't have any hits for MODIO so I'm
wondering if it's possible to add this device to a Beagle running
MachineKit.
Thanks
John
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You received this message because
Nice price on that MPG. It would work with the bare MODIO.
I have my Y Axis Servo working with the BBB MachineKit, Xylotex DB-25/26
cape and Probotix interface board.
Response from the keyboard arrow keys or the mouse clicking on the jog buts
is abysmal.
MDI commands to move the Y axis work.
I
would
expect: the intermediate value of the combined parallel thermistor and
resistor resistance is called `R_TD`, and the calculation goes on to
find the separate thermistor resistance of `R_T`.
Can anyone help clarify?
[1]: http://reprap.org/mediawiki/images/5/5a/CRAMPS.v2.1.sch.pdf
of my
head that the 4.7k resistor was tied to ground. D'oh!
John
--
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.
at
least compiles. It's installed as shown at the top of the file by
putting it in `/lib/firmware` and adding
`dtb_overlay=/lib/firmware/pb_goldibox-00A0.dtbo` to `/boot/uEnv.txt`.
That doesn't seem to have any effect on the pins in question, however.
Hints appreciated!
On 10/27/2017 01:36 PM, Robert Nelson wrote:
On Fri, Oct 27, 2017 at 1:32 PM, Robert Nelson wrote:
On Fri, Oct 27, 2017 at 1:27 PM, Robert Nelson wrote:
Hi John,
On Fri, Oct 27, 2017 at 1:20 PM, John Morris wrote:
To get Beagle GPIOs configured correctly at boot, is a custom overlay the
hiccups ATM if you do).
I'd highly appreciate help with the GUI, and I welcome your comments
about the project.
[1]: https://github.com/zultron/goldibox
[2]:
https://docs.google.com/drawings/d/1ixn3tSA8_OyTdZ1lz5k4MWjTZ9rEFJM9or3oYW8NuUA/edit?usp=sharing
John
--
website: h
017 at 11:04:36 AM UTC-4, Daren Schwenke wrote:
Neat idea, and perfect name. :)
Thanks!
John
On Tuesday, October 31, 2017 at 2:07:09 PM UTC-4, John Morris wrote:
I'm working on this Machinekit-based weekend project, the
"Goldibox"
arallel is allowed, whew.
I don't know how to do the current sensing, but the L298N provides sense
pins.
Thanks for the tips, Daren.
John
[1]: http://www.st.com/resource/en/datasheet/l298.pdf
On 11/01/2017 10:59 AM, Daren Schwenke wrote:
Just hook up your power full on in one direc
[Putting this back on-list]
On 11/01/2017 11:52 AM, Chris Albertson wrote:
On Wed, Nov 1, 2017 at 8:40 AM, John Morris <mailto:j...@zultron.com>> wrote:
On 11/01/2017 10:15 AM, Daren Schwenke wrote:
When switching peltiers between heat/cool mode you can get some
[Putting back on list]
On 11/01/2017 02:30 PM, Chris Albertson wrote:
On Wed, Nov 1, 2017 at 10:50 AM, John Morris <mailto:j...@zultron.com>> wrote:
The value IMO is in the demonstration of a full integration from
electronics to remote GUI, and in the overall simpl
an error somewhere along the way, but no error message and not
handled. Once I found it, I knew what the problem in my environment was
and easily fixed it. The 'stack smashing' thing just went away after
that, IIRC.
Good luck, and please report back if/when you find it so it
> the control budget under $10 or you look silly using so much over kill
>
> Perceptions matter. Using a 64-bit quad core ARM computer to control an
> ice box just has "bad optics"
>
> On Thu, Nov 2, 2017 at 8:25 AM, John Morris <mailto:j...@zultron.com>> wrote:
Here's where we got that path in the first place:
http://www.spinics.net/lists/linux-rt-users/msg09173.html
Perhaps things have changed in recent kernels, or perhaps you could
double-check (double-grep?) your kbuild configuration for CONFIG_PREEMPT_RT?
John
On 11/02/2017
o it
would wait for an input and then fail)
Sounds like you're using Python remaps in your toolchanger config.
Can you try printing debug info from the Python code?
John
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinek
On 11/14/2017 05:10 PM, Sag ich Dir nich wrote:
no one got an idea?
Am Montag, 13. November 2017 19:09:26 UTC+1 schrieb Sag ich Dir nich:
oh and by the way i am using toplevel.py, remap.py and stdglue.py
Am Montag, 13. November 2017 17:27:33 UTC+1 schrieb John Morris:
On 11
On 11/15/2017 07:10 AM, Sag ich Dir nich wrote:
Here is my Config. Beware, it doesnt look pretty because it´s
experimental atm :)
Am Mittwoch, 15. November 2017 01:39:29 UTC+1 schrieb John Morris:
On 11/14/2017 05:10 PM, Sag ich Dir nich wrote:
> no one got an i
reset_state) = FALSE
now after i restarted the machine, it doesnt even move when i command a
toolchange, it only spits out this error.
thanks for your help
Am Mittwoch, 15. November 2017 16:48:50 UTC+1 schrieb John Morris:
On 11/15/2017 07:10 AM, Sag ich Dir nich wrote:
> Here i
On 11/18/2017 10:00 AM, Sag ich Dir nich wrote:
Thank you, now it works flawlessly :) i also had "#" instead of ";" in a
ngc file, i always confuse them
Glad it works. I submitted that PR, and Mick merged it. Thanks, fellas.
https://github.com/machinekit/machinekit/pul
. It would be neat to see a HAL comp using that scheme.
Also, after having spent WAY too much time with interp and task, I've
often wished for a new start. A pure python interpreter would be nice,
especially if written for easy addition of new and subclassing of old G
codes.
John
est #5399 and
abort on -1, and not blindly contine on.
John
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You received this message because you are subscribed to the Google Groups "Machinekit" group.
To unsubs
nce you're done with it!
John
I don't know if #5399 is set to anything before M66 exits, I would
suspect it would hold the last entered value until M66 exits for
whatever reason
and sets the return value accordingly.
You will need to verify, but suspect #5399 is meaningles
Looks like it:
git:/opt/scripts/:[ef2c5982e3788e07d9ec4a3d23089dc5e5a3f9cd]
eeprom:[A335BNLT000C1625BBBG0497]
model:[TI_AM335x_BeagleBone_Black]
dogtag:[Machinekit Debian Image 2017-12-10]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot
2018.01-rc1-2-g87ef84]
kernel:[4.14.4-bone-rt-r7]
nodej
g to attach those files if shown how.
Thank you,
John Hammond
hammond.jo...@gmail.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&q
I have the program loaded on a BeagleBone Black
--
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 r
rt parport "0x378 out"
(as shown in LinuxCNC Forum #84912) next. I haven't looked at the hal file
yet but will within 2 hours.
Thanks,
John
On Monday, December 18, 2017 at 4:22:14 PM UTC-8, John Hammond wrote:
>
> Linuxcnc error terminal window appears, but nothing runs.
&g
, John Hammond wrote:
>
> Linuxcnc error terminal window appears, but nothing runs.
> I can start linuxcnc by opening terminal window and entering “linuxcnc &”
> . This stops when it does not find my configuration file.
> I have copied the linuxcnc error message along with two othe
Actually I just copied the settings that I had used before in the PC setup
into the stepconf.
On Monday, December 18, 2017 at 4:22:14 PM UTC-8, John Hammond wrote:
>
> Linuxcnc error terminal window appears, but nothing runs.
> I can start linuxcnc by opening terminal window and
rules
obj-$(CONFIG_MYKINS) += tp.o tpmain.o
mykins-objs := tp.o tpmain.o $(MATHSTUB)
mykins$(MODULE_EXT): $(mykins-objs)
# Add the module build to a higher-level target
all: obj-$(CONFIG_MYKINS)
John
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://githu
is there any official support status for the White, both from RCN
and the MK project?
John
--
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 "Mach
On 02/24/2018 07:57 PM, Charles Steinkuehler wrote:
On 2/24/2018 4:15 PM, John Morris wrote:
I finally found the perfect application for my old Beaglebone White.
However, I'm suspicious that it has fallen out of support.
[...]
I haven't done anything to intentionally break suppo
Backing down to the TI 4.9 kernel resolved the problem. I'm now trying
out different kernels to see which works best.
John
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You received this message because you are su
.4.113-ti-rt-r147]
[...]
dmesg | grep gpio-of-helper
[1.511377] gpio-of-helper ocp:cape-universal: Allocated GPIO id=0
[1.511589] gpio-of-helper ocp:cape-universal: Allocated GPIO id=1
[1.511604] gpio-of-helper ocp:cape-universal: ready
END
So who knows what dumb
harles's
suggestions to add the pinmux configuration and this suggestion to free
the pins caused errors. I probably made a mistake following y'all's
directions. I'm happy to go back and troubleshoot if it helps anyone,
but right now with the pins in the default state, it
The BBB Xylotex.ini file Axis 3 is set as:
TYPE = ANGULAR
Currently the comment for SCALE is
# scale is 200 steps/rev * 8 uSteps/rev * 10 TPI.
SCALE=32000
I can see for a linear axis how this works although 32,000 doesn't match
the 16,000 in the comment. Is the scale ultimately the number of ste
>
> I'll answer my own question. I was searching through the HAL docs rather
> than the ini docs.
>
http://www.machinekit.io/docs/config/ini_config/#sub:AXIS-section
In that document I found ANGULAR_UNITS = degrees and has nothing to do with
NC code.
*"'ANGULAR_UNITS = ' - Specifies the 'mac
t controls. Thanks to all the
devs and maintainers for the great work.
John
On 04/03/2017 12:19 AM, John Morris wrote:
It's been three years. Happy Birthday, Machinekit!
John
On 04/03/2016 04:48 PM, John Morris wrote:
Happy two-year birthday, Machinekit! Another grea
ck off the activated limit switch?
Am I missing something or is there some sort of net limit-x bb_gpio.p ...
statement that can be used?
Thanks
John
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You received this message because
>
> Answering one of own questions I think...
>
>From the Wiki for standard parallel port modified for the BBB and Xylotex
BBB-DB25/26:
> # connect DB25-11 to X home and min limit
> net home-x bb_gpio.p8.in-10 => axis.0.home-sw-in axis.0.neg-lim-sw-in
>
# connect DB25-12 to Y home and min lim
P-UHU Servo drive with the BBB-DB25/26
since I didn't have home switches.
HOME = 0.000
HOME_OFFSET = 0.00
HOME_SEARCH_VEL = -.1
HOME_LATCH_VEL =0.2
HOME_IGNORE_LIMITS =YES
HOME_IS_SHARED =0
#HOME_SEQUENCE =2
On Wednesday, April
I'm finally continuing my work on building a new gui and switching this in
progress work from linuxcnc to machinekit. I'm using my ACRA milling
machine as a test bed which I do need to be able to use normally while this
work progresses. It runs on linuxcnc 2.8pre with gmoccapy.
The interface b
On Monday, May 14, 2018 at 11:29:45 PM UTC-8, fairbanks-john wrote:
>
> I just made a fresh install from the git hub clone today and wondering if
> I did something wrong since there are a lot of warnings and notes in the
> installation log which I have attached..
> The .hal f
On Wednesday, May 16, 2018 at 7:06:51 AM UTC-8, Schooner wrote:
>
>
> On 15/05/18 08:29, fairbanks-john wrote:
> > I just made a fresh install from the git hub clone today and wondering
> > if I did something wrong since there are a lot of warnings and notes
> > in
Schooner I think that I pushed a wrong buttons while posting and messed
things up a bit. I got a new computer and build a new configuration since I
think the old machine may have gotten corrupted while attempting to solve
issues. I will rebuild it later. Machine kit loadsrand runs now but I'm
c
Yes, It looks like I'm getting closer to having a working configuration
that is getting close to being suitable for further testing and development
work.
I did purchase a second Mesa 7i80 card and flashed it with my custom bit
file so that I would not have to use the actual card and milling mac
I have Machinekit running now as a run in place with no error but having
issues correctly addressing pins in my Mesa 7i80HD-25 board.
To help resolve this problem I have attached my custom PIN_CNC1_V1_72.vhd
file which is human readable. My install of Machinekit is a cloned install
from git hu
To day I decided that the cause of my problem is most likely the version
of gmoccapy available with machinekit. I had modified my configuration
files to make gmoccapy happy but it appears that there are still
incompatibilities and do not wish to spend more time on.
I used my Mesa 7I80 flash de
I'm running a BBB with Xylotex BBB-DB25/26. Often when I start up
MachineKit I get the opening banner, it vanishes and then a minute or so
later pops up with an error window. Attached is the dump. I can restart
and MachineKit begins normally. Or maybe it fails again and then runs
correctly
>
>
> It seems like a good choice because it works with LCD screens, MachineKit,
> and has the IO that I need. I don't know what I don't know so if anyone has
> any suggestions I'd be interested in hearing them!
>
I'm doing something similar but with a Xylotex BBB-DB25/26 cape connected
to a P
Schooner in reference to your comment:
"I am confused by your use of 'remote'. Gmoccapy is not a remote GUI, but
you were using it.
Are you just referring to accessing the controller machine remotely from
another computer?
Or are you intending to use an actual remote interface via a loader a
On Sunday, May 20, 2018 at 5:20:57 AM UTC-7, Eric wrote:
>
> That looks awesome!
>
> Are you going to be able to manually move the axes too, or is it now going
> to be full CNC?
>
> At the speed that the XY axis turn the handles would have to be balanced
and not near my private parts. That wou
I wait 30 seconds or more then I don't get the issue.
Why it takes so long I don't know.
John
On Friday, May 18, 2018 at 10:55:07 PM UTC-7, Schooner wrote:
> The problem with this run is right at the beginning of the error print.
>
> rtapi/rtapi_msgd.cc:247 ERROR: found exist
I have been setting up a new development system using Mint 18.3 and also a
Windows box using Win7 and have noticed that there is a problem getting
Machinekit logging working properly on Mint every time 'sudo make setuid'
is run. So to help others here is my consolidated fix to overcome this.
T
I’m a little confused on how to interface the Cetus gui with Machinekit on
my new Linux based development PC on which I have already installed
Machinekit as run in place. I’m running on Linux Mint 18.3 with kernel
4.9.98-RT. The Machinekit appears to be running fine and I have down loaded
C
hreads-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: c...@tuta.io
Cc: Machinekit
So as not to hijack the thread,
we can turn `-Werror` back on. I'll also take a
look at Buster builds down the road when I actually start using it, if others
think fixing warnings is worthwhile; if not, I won't fight the current.
John
From: machinekit@googlegro
eciate 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
for it. However, it doesn't explain why it reverts b55b544 (or more likely
I'm missing something). What's the problem there?
No, I'm not looking forward to silencing warnings in gcc 8. ;(
John
From: schoone...@gmail.com
Sent: Thursda
/sys/devices/pci:00/:00:1c.2/:02:00.0/:03:00.0/resource
Thanks again for doing all the legwork to track down this problem. It was easy
to fix with that hard part done for me.
John
From: schoone...@gmail.com
Sent: Friday, March 8, 2019 7
Hey guys,
PR against legacy MK repo at https://github.com/machinekit/machinekit/pull/1478
Thanks for the PCI resource file contents. I think the change should parse
those contents correctly.
John
From: machinekit@googlegroups.com on behalf of
Python functions may have `return` for regular functions or `yield` for
generator functions, but not both.
John
From: machinekit@googlegroups.com on behalf of
Bob Bevins
Sent: Wednesday, March 20, 2019 8:59 PM
To: Machinekit
Subject: [Machinekit
nges.
Understand that my opinion doesn't necessarily reflect the general community
consensus. I'm jumping in to help out with this work because I think it's been
sorely needed for a long time, and I'm super excited to see people stepping up
to sort out this extreme
n and at last into the
visibility of its own light. There's a lot of polishing left to do,
but it's huge progress that it is already usable, with its own
independent code base and package stream. Congratulations, and thanks
to everyone who helped make this happen!
John
On Wednesday
e kinks in `MultiArch` will be worked out some day and this will all be
much simpler.
https://github.com/zultron/mk-cross-builder
John
From: machinekit@googlegroups.com on behalf of
schoone...@gmail.com
Sent: Saturday, April 20, 2019 8:56 PM
To:
Machinekit. If you confirm that the
change is in place and you're still seeing this issue, file an issue on the
tracker, and mention @zultron to ensure I see it (though I would anyway).
John
[1]: https://github.com/machinekit/machinekit/commit/b58f6e83
>
> Than
On Monday, May 20, 2019 at 11:07:12 AM UTC+8, mlampert wrote:
>
> Am I correct that the support for the PB is a 'compile time' decision?
>
Try`board=PocketBeagle`
https://github.com/machinekit/machinekit/blob/b58f6e83/src/hal/drivers/hal_bb_gpio/hal_bb_gpio.c#L83
rry I didn't test the original patch more rigorously. Seems my
super-simple Goldibox HAL config didn't use any GPIO inputs!
John
>
> On Mon, 20 May 2019 14:39:49 -0700
> markus > wrote:
>
> > Yay - that does work, it is required to specify the board though:
be linked both by rtapi_app and given
> module, given the fact that all live in one linker namespace.
>
>
Well, `rtapi_app` CAN export symbols, those marked with `EXPORT_SYMBOL`.
To export a few symbols, that's the "best way" because it exists, it works,
and other develop
since been solved (i.e. fast ARM cross-builds
replaced the old emulated builds that exceeded the 50-minute time limit on
Travis). There are (likely out of date) Travis setup instructions in the
mk-cross-builder repo.
https://github.com/dovetail-automata/mk-cross-builder/
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 M
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
more involved routine.
It seems that in order to avoid a custom build of MachineKit, that I need a way
to either trigger immediate homing or the ability to detect that a user
initiated immediate homing from within HAL. Any ideas?
John Allwine
Owner of Allwine Designs
https://www.allwinedesigns.com
gt;> ...
>> ## I also have similar config for another axis (home-sw2.1...) but there is
>> no really added value to show it here...
>
>
>> On Monday, 24 February 2020 11:55:39 UTC+1, Damien Dando wrote:
>> Hi John,
>>
>>> It seems that in order to
This project seems to have lapsed 5 years ago.
https://github.com/kinsamanka/PICnc-V2/wiki
Any interest in resurrecting it?
John Dammeyer
"ELS! Nothing else works as well for your Lathe"
Automation Artisans Inc.
www dot autoartisans dot com
--
website: http://www.machinek
There's ARM and MIPS. There was 8086 and M68000. The 8086 won the war as
Apple MACs now use Intel and Motorola is now part of NXP. I do wonder whether
the support for MIPS and the PIC32 has waned with Microchip purchasing ATMEL.
Perhaps it's better to go TI with their product l
1 - 100 of 216 matches
Mail list logo
