By default, the step/dir pins use GPIO access which is valid for either PRU
core. The encoder signals, however, need to be direct PRU inputs, so the
pins chosen and the pinmux setup will need to be valid for the specific PRU
core you choose to run the driver. You setup the pin multiplexing
ONE-eMMC1-01-00A0
BB-HDMI-TDA998x-00A0 name
--
Charles Steinkuehler
cha...@steinkuehler.net
--
Charles Steinkuehler
cha...@steinkuehler.net
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.
020 armv7l GNU/Linux
*$ ls /proc/device-tree/chosen/overlays/*
AM335X-PRU-UIO-00A0 BB-ADC-00A0 BB-BONE-eMMC1-01-00A0
BB-HDMI-TDA998x-00A0 name
--
Charles Steinkuehler
cha...@steinkuehler.net
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: http://www.machinekit.io blog: h
inc
*$ uname -a*
Linux beaglebone 4.19.120-bone-rt-r50 #1stretch PREEMPT RT Fri May 8
22:45:31 UTC 2020 armv7l GNU/Linux
*$ ls /proc/device-tree/chosen/overlays/*
AM335X-PRU-UIO-00A0 BB-ADC-00A0 BB-BONE-eMMC1-01-00A0
BB-HDMI-TDA998x-00A0 name
--
Charles Steinkuehler
char...@steinkuehler.
so:
cannot open shared object file: No such file or directory
Regards
Klemen
On Fri, 12 May 2023 at 17:25, Charles Steinkuehler
wrote:
Your output indicates dlopen is looking for "pru_generic.so" but your
filesystem only has "hal_pru_generic.so".
You need to fix the sc
n
$ uname -a
Linux beaglebone 4.19.120-bone-rt-r50 #1stretch PREEMPT RT Fri May 8
22:45:31 UTC 2020 armv7l GNU/Linux
Every help would be very much appreciated,
Regards,
Klemen
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
Wha have I done wrong ? Is it because I am using a different machinekit
image than what is mentioned at Xylotex's web page ?
Anoop
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You received t
it work with Machinekit + ROS without much
modifications? Do I need to apply some custom branch or some other hacking?
Thank you for your time devoted to this and making these meaningful
contributions, which are a real game-changer for robotics researchers.
Best regards,
Jakub
--
Charles Steinku
c character) between the first digit
and any remaining digits. Two digit values are assumed to have an
implicit zero in the pin number (eg: 82 -> P8_02).
I believe the compiled version of config-pin is somewhat more picky
about naming conventions, but I haven't used it muc
Changing those to the 8-- and 9-- series would make the hal file more readable.
Yes, almost all the hal_pru_generic pins can use the new 8xx/9xx pin
numbering scheme. The only exception is the encoder input pins, which
require a PRU direct input to function properly.
--
Charles Steinkuehler
suggestions on what to do next?
Thanks
John
From: machinekit@googlegroups.com [mailto:machinekit@googlegroups.com] On Behalf Of John Dammeyer
Sent: April-13-21 8:26 PM
To: 'Charles Steinkuehler'; machinekit@googlegroups.com
Subject: RE: [Machinekit] BBB and charge pump
Making progress.
Scope
73018%245f04d6e0%241d0e84a0%24%40autoartisans.com.
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You received this message because you are subscribed to the Google Groups &q
for the BBB so I've not looked at the current state for doing that on the
latest rPiOS.
I haven't been building Machinekit much, but I have been doing a lot of
work recently on the RPi4. I may be able to help if you get stuck on
something.
--
Charles Steinkuehler
char...@steinkuehler.net
M codes for 104
and
109 (and 106 for the fan) but I get nothing. My configs are attached, if
anyone has a BBB and CRAMPS working for 3D printing, or FET controls I'd
love to get your advice.
Thanks
Pete
--
Charles Steinkuehler
cha...@steinkuehler.net
--
Charles Steinkuehler
cha
'd
love to get your advice.
Thanks
Pete
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You received this message because you are subscribed to the Google Groups "Machinekit&quo
l appreciate any ideas on how to make the module work.
Thank you,
Jacek.
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You received this message because you are subscribed to t
you,
Jacek.
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You received this message because you are subscribed to the Google Groups "Machinekit" group.
To unsubscribe from
16c-03d6-4c1c-8cc5-0d8ad5012849n%40googlegroups.com
<https://groups.google.com/d/msgid/machinekit/8c6cb16c-03d6-4c1c-8cc5-0d8ad5012849n%40googlegroups.com?utm_medium=email_source=footer>
.
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: http://www.machinekit.io blog: http://
(on IDROMConst.vhd) are used to simply pass the fixed hardware clock
frequencies to the hm2 driver for its frequency based calculations
The clock tags that specify which clock a module uses (for determining I/O
frequencies) is in the module ID section of the pinout file:PIN. vhd
--
Charles
that I could template from?
Any thoughts on this would be appreciated,
Thanks,
Tom
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You received this message because you are subs
ween different
PRUs could also be key, so I like the idea of hal_pru_generic being
instantiable.
On Thursday, April 30, 2020 at 3:28:51 PM UTC-6, Charles Steinkuehler wrote:
I think it would be easier to extend the existing logic to simply write
to more registers, but an icomp version of hal_pru_
a single instance. The BeagleBone AI
does expose many more pins as direct outputs, but I’m unable to instantiate
more than one instance of hal_pru_generic in order to take advantage of certain
pin configurations. Is it possible to make hal_pru_generic instantiable?
--
Charles Steinkuehler
char
. My name is Gordon Osterstrom
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You received this message because you are subscribed to the Google Groups "Machinekit&q
vely.
So, what are your ideas about where to start on such a cape?
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You received this message because you are subscribed to the Go
config files, and we
can review.
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You received this message because you are subscribed to the Google Groups "Machinekit&q
Justin,
I took your advice and played with the home and home offsets. It now fully
disengages from the switch while homing, but this hasn't solved the
problem. It will home whichever axis is crossest to its switch and then
stop. Any suggestions?
Thanks,
Nathaniel
--
Charles Steinku
Lathe"
Automation Artisans Inc.
www dot autoartisans dot com
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You received this message because you are subscribed to the Goo
gt;;
colors-per-beat = <0x4>;
beats-per-pixel = <0x1>;
mem-word-width = <0x80>;
};
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You received this mess
6 UTC+2, justin White wrote:
>>
>> [image: DE10nano interface.jpg]
>>
>> [image: Photo Sep 23, 10 50 34 AM.jpg]
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
BB U-Boot overlay instructions:
https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Disable_on-board_devices
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You rec
/sys/class/uio/uio0 it means you don't
have the PRUs properly enabled. Make sure you have the PRU UIO device
(*NOT* remoteproc) enabled via u-boot. It's the last entry here:
https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_PRU_Options
--
Charles Steinkuehler
char...@st
o copy (rsync) the contents of the rootfs onto their image. My
Debian rootfs system is agnostic with regards to where it lives, as
long as you pass an appropriate root= command to the kernel. :)
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: http://www.machinekit.io blog: http://blog
ctive (F2)
ESTOP : Should be on until the machine is out of ESTOP (F1)
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You received this message because you are subscribed to the G
hub.com/machinekit/machinekit/blob/master/.travis.yml#L92
https://github.com/machinekit/machinekit/blob/master/scripts/build_docker
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
-
support!).
I do have a personal setup with the hal_pru_generic code running on
one PRU and custom PRU code running on the other PRU (making use of
the PWM & UART present in the PRU module to generate some custom pulse
sequences), so it's definitely possible.
--
Charles Steinkuehler
char...
hing
> I probably should have. I'll try to look into your suggestions a bit later.
>
>
> On Tuesday, August 20, 2019 at 9:41:57 AM UTC-4, Charles Steinkuehler wrote:
>>
>> It sounds like the synthesis tools are optimizing away the stepgen
>> logic, almost certainl
5:00:11 PM UTC-4, Michael Brown wrote:
>>
>> Thanx for the clairifying Charles, I doublechecked tha line and it reads:
>> (StepGenTag,x"02", ClockLowTag,x"06",
>> StepGenRateAddr, StepGenNumRegs, x"00", StepGenMPBitMask),
>
out how to set a resolution for
>>>>>>>> whatever
>>>>>>>> monitor I intended to use.
>>>>>>>
>>>>>>>
>>>>>>> Sadly there are currently no presets for these 2 resolutions for the
&g
fig/DExx_Nano_xxx_Cramps/PIN_st_fpga_soc_dc1f.vhd Line: 80
The configs I have that use SSerial are using ClockLowTag and IIRC
they worked OK. You might check and see if Peter has updated the
IDROMConst.vhd file, the one in the Machinekit repo might be fairly
dated. But I think it ought
ple years since I messed with this and I'm not 100% sure if I had
my 7i76 (and it's sserial driven field IO pins) working with the DE0
or with a 7i92 (I was doing a lot of switching back and forth at the
time but I'm pretty sure the 7i76 was working properly with both).
--
Charles Steinkuehler
char...@stein
hinekit/mksocfpga/blob/master/HW/hm2/config/DE0_Nano_SoC_DB25/DE0_Nano_SoC_DB25_card.vhd#L73
The clock source also needs to match the frequency specified in the
above file. For the DE0_Nano, the 100 MHz medium clock is generated
by an HPS PLL:
https://github.com/machinekit/mksocfpga/blob/master/HW
could find some evidence that either
> sserial is actually running or that the hardware isn’t communicating anything
> at all, like some sort of serial terminal where I could at least check for
> some sort of handshake process.
>
--
Charles Steinkuehler
char...@steink
on july 13 except I changed SS numinst to 1.
>
> On Wednesday, July 17, 2019 at 11:24:07 PM UTC-4, Charles Steinkuehler
> wrote:
>>
>> Got a link to your pin file for review?
>>
>> On 7/17/2019 6:59 PM, justin White wrote:
>>> I used 2 instances of SSerial in
my other sserial configs.
>>
>> I'll probably hold off on anymore testing until I get a board fabbed with
>> dedicated serial hardware, but the firmware could probably use some looking
>> into.
>>
>> On Sunday, July 14, 2019 at 6:08:13 AM UTC-4, justin White wrote:
withstand nearby lightning strikes. :)
That said, spindle motors can throw off enough ESD to cause problems
even with differential signals, which is why you want _something_.
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: http://www.machinekit.io blog: http://blog.machinekit.io gith
digital logic levels. The 7i76 provides an RS-422
transceiver for the SSERIAL bus on TB3.
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You received this message because you are sub
On 6/30/2019 4:34 PM, Doug LaRue wrote:
> On Sunday, June 30, 2019 at 12:46:29 PM UTC-7, Charles Steinkuehler wrote:
>>
>> You should be able to hook to the DB25 directly vs. digging into the
>> control box, but you'll likely need some buffering. The BBB I/O pins
>&
eo =Y)
> 13 X limit( Mach 3 video =Z)
> 14 X Enable
> 15 Probe
> 16 Y Enable( Mach 3 vidoe =Output1)
> 17 Z Enable
> 18 - 25 Ground
>
>
>
> [image: GRBL_Arduino_Nano_DB25_CNC_1.jpg]
>
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: http:
gt;> missing
>>>>>
>>>>> So you can create a copy of a suitable atlas_3x24 .sv named
>>>>> atlas_st_fpga_soc_dc1.sv
>>>>> <http://www.google.com/url?q=http%3A%2F%2Fatlas_st_fpga_soc_dc1.sv=D=1=AFQjCNFaXzIhSaX4akk6lI9iwZh_k2ltV
vacation and very much off-line the last two weeks.
Merged.
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You received this message because you are subscribed to the Google Groups
&q
tion
> `map->l_init_called' failed!
This warning is benign and may be safely ignored.
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You received this message because
re 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 bo
gt; complains about 902 not being valid.
>
>
> On Mon, 20 May 2019 15:55:37 -0500
> Charles Steinkuehler wrote:
>
>> On 5/20/2019 3:36 PM, markus wrote:
>>> Thanks for the clarification - much appreciated.
>>>
>>> It seems the driver is ignoring the
1e9-aea4-606405e00475" "service=log"
> "dsn=tcp://pocketbeagle.local:49152"
> May 20 00:07:39 pocketbeagle rtapi:0: 1:rtapi_app:1381:user hal_bb_gpio:
> ERROR: invalid pin number '901'. Valid pins are 101-136 and 201-236.
The P8/P9 headers do
b.com/machinekit/machinekit/blob/b58f6e83/src/hal/drivers/hal_bb_gpio/hal_bb_gpio.c#L83
>>
>> John
>
> Where? When?
In your hal file when you load the hal_bb_gpio module, eg:
loadrt hal_bb_gpio board=PocketBeagle output_pins=...
--
Charles Steinkuehler
char...@steinkuehler.net
-
:0002 Linux Foundation 2.0 root hub
> END
> machinekit@beaglebone:~$
>
>
> Thanks
>
>
>
> On Wednesday, May 15, 2019 at 4:14:33 PM UTC-4, Charles Steinkuehler wrote:
>>
>> That sounds like something to do with the overlays. IIRC, I didn't
>> have
On 5/13/2019 10:21 AM, Michael Brown wrote:
> On Sunday, 12 May 2019 15:49:38 UTC+2, Michael Brown wrote:
>> On Saturday, 11 May 2019 22:38:47 UTC+2, Charles Steinkuehler wrote:
>>> On 5/11/2019 1:17 PM, Michael Brown wrote:
>>>>
>>>> Next step is hop
s appreciated for any help anyone can provide.
> Thank you for your time,
>
> Bradley
>
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You received this message because you are subs
t;>
>>> Purging the installed Machinekit packages and installing the new ones as
>>> you suggested got HALshow working right away.
>>>
>>> I've pretty much got my encoder interface and output hardware sorted, I
>>> use 24v I/0 but it should handl
m/#!topic/machinekit/eVhvTnuhblE>
I'm not sure what exactly you mean by "development environment", but I
typically develop directly on the system (eg: compile Machinekit & HAL
modules on the DE0/DE10), and use an x86 VM running Debian to build
the uSD images (kern
u whached the presentation Charles linked to ?
In addition to the recorded presentation, you can get the slides I
used from github:
https://github.com/cdsteinkuehler/Presentations/tree/master/2017.04.29.Machinekit_Meetup
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: h
https://github.com/cdsteinkuehler/bobc_hardware/pull/5
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You received this message because you are subscribed to the Google Groups
"Machin
e. So you edit/create an appropriate PIN file, then make sure your
FPGA project uses *that* PIN file when building.
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You re
wm, smart
serial, etc. To get an encoder to show up, just program the FPGA with
an appropriate configuration file and the HM2 driver will detect the
encoder instances.
It sounds like Michael is helping you with an appropriate FPGA
configuration.
--
Charles Steinkuehler
char...@steinkuehler.net
--
the beagleboard am335x_pru_package is more appropriate for that.
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You received this message because you are subscribed to the
e Machinekit source tree, see the files
with "prussdrv" in the name:
https://github.com/machinekit/machinekit/tree/master/src/hal/support/pru
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.co
th the uio_pruss module loaded, AND all the P8 pins
>> available!
>
> So, you shouldn't have to force that overlay, as out of the box, we
> have cape-universal auto-loading..
Does U-Boot automatically change the universal overlay loaded when you
disable on-board "ca
On 5/1/2019 2:03 PM, Jon Elson wrote:
>
>
> On Tuesday, April 30, 2019 at 6:00:51 PM UTC-5, Charles Steinkuehler wrote:
>>
>> Is there a reason you like beating your head against the wall?
>>
>> Just let U-Boot load the universal and PRU-UIO overlays, and us
> .dtbo, I see the addresses of the pinmux offsets, but the setting for them
> was all wrong.
>
> I'd really appreciate some help here, because I'm just LOST!
>
> Thanks,
>
> Jon
>
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: http://www.mac
log/2018-01-17-building-a-device-tree-overlay-for-your-new-pocketcape-design
And you can always dig through the live device-tree via:
/proc/device-tree/
...to see if your overlays got loaded the way you expect.
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: http://www.machinek
erlay,
> but I'm guessing it is now failing for some reason?
It looks like you are loading both your overlay and the universal
overlay, which will conflict with each other. Just pick one or the
other, not both.
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: http://www.machinekit
or HAL, I would recommend you read through at least the
introduction:
http://www.machinekit.io/docs/hal/intro/
You don't need all the details (eg: creating new components with C or
python), but you should be familiar with the concept of components,
pins, signals, and functions.
--
and verify the
UIO PRU driver is loaded, then add one piece at a time to try and get
the configuration you want (again, it's probably easiest to just use the
universal overlay unless there's a strong reason not to).
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: http
and uio_pdrv-genirq loaded.
Any idea what caused this?
Thanks,
Jon
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You received this message because you are subscribed to the Google
ne_capemgr.9/slots
more /sys/devices/bone_capemgr.9/slots
_end of file
But, this now gives an error,
./dtc_load: 5: ./dtc_load: cannot create
/sys/devices/bone_capemgr.9/slots: Directory nonexistent
Is there a document that explains how to do this?
Thanks much for any help!
J
vo.3 0
> #sets servo.4 0
>
> #net servo.1 bb_gpio.p8.out-25
> #net servo.2 bb_gpio.p8.out-24
> #net servo.3 bb_gpio.p8.out-23
> #net servo.4 bb_gpio.p8.out-22
>
>
> # ##
> # PWM and Temperature Signals
> # ###
I
> last tried using the BBB with the old version of machinekit I was using.
> Now I'm trying to update what I have to newer machinekit software (with
> all the new overlays, etc.) and can no longer program the pins to allow me
> to access the gpmc.
>
> Jeff
>
>
&
I can test it out?
Don't take this the wrong way, but if you have to ask about how to
compile a device tree (or overlay), you probably shouldn't be trying
to use the GPMC interface.
Let's take a step back...exactly what are you trying to do?
--
Charles Steinkuehler
char...@steinkuehler.net
P8_14 (which would be
>>> gpmc_AD14 as a starting example), but I get
>>>
>>> *Cannot write pinmux File:
>>> /sys/devices/platform/ocp/ocp:P8_14_pinmux/state*
>>>
>>> Can anyone give a pointer on how to go about configuring pins to use
>&g
ins,
and each specific pin has various other possible functions (eg: pwm,
uart, i2c, timer, etc).
However, the analog pins are generally dedicated for use as ADC
inputs, so they cannot be arbitrary GPIO pins.
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: http://www.machinekit.io
772=att=safe=f_jujwfdh30>
> CRAMPS.hal
> 17 KB
> <https://mail.google.com/mail/u/0?ui=2=6fb2ca6400=0.1=msg-f:1630982304047515506=16a269c3a3b34772=att=safe=f_jujwfdh30>
> <https://mail.google.com/mail/u/0?ui=2=6fb2ca6400=0.2=msg-f:1630982304047515506=16a269c3a3b34772=att=safe
can just use the slower GPIO.
> I'd like to get ahold of a pin config that is verified to work so I know
> what I'm working with
There are lots of choices. :) I have a number of board pinouts
listed in spreadsheet form which you may find helpful:
https://github.com/cdsteinkuehle
suggestions on how to get the communications link working properly?
Thanks,
Jeff
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You received this message because you
s the part that gets used.
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You received this message because you are subscribed to the Google Groups
"Machinekit" group.
To u
ptr;
}
...then use the appropriate type where needed.
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You received this message because you are subscribed to the Google Group
round 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 f
the step
pulses (eg: the PRU, or some of the "tricks" used on the RPi like
programmed DMA to the GPIO port).
* If you want good performance with "bit-banged GPIO ports", get a
decent x86 machine with a parallel port and a motherboard that
performs well with Xenomai or the Preemp
nnect fabric has the ability to
accept a small number of write requests immediately. The PRU can then
carry on with other work while the write request makes its way through
the interconnect to it's ultimate destination.
https://en.wikipedia.org/wiki/Posted_write
--
Charles Steinkuehler
char...@stein
gt; r0-31, the previous link say 3PRU cycles (15ns) but does that
> depends of how many bytes we load? or it takes the same amount of
> time regardless of the number of bytes?
I believe it will take one extra clock for each additional DWORD read
from the PRU data memory.
--
Charles Steink
e signals used for CNC control.
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You received this message because you are subscribed to the Google Groups
"Machinekit" group.
ili mill as a picking place
> machine. This would be REALLY popular., simply place a little vacuum
> picker on the spindle and for very little cost you have a slow slow pick
> and place machine suitable for hobby level PCB assembly. The HF mill
> should be accurate enough
issue with the group settings?
>
> BR,
>
> /Damien
>
>
> --
> 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
> "Ma
working on this board and verifying
capes work as expected.
I couldn't say anything about it earlier, but now they've announced it
at Embedded World. :)
On 2/24/2019 8:53 AM, Charles Steinkuehler wrote:
> I'd call 1-2 minutes for scanning slow, but that depends a bit on how
> much processing
ntioned velocity based extrusion in your previous mail. If you
want to setup velocity based extrusion, my config files are not the
place to start.
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machin
On 2/26/2019 7:24 AM, Damien.D wrote:
> Le lundi 25 février 2019 17:46:06 UTC+1, Charles Steinkuehler a écrit :
>>
>> Personally I don't really want to see hal_pru_generic code reading
>> from the fabric, it eats up too much time. I'd rather see "slow" code
>&g
ing them,machinekit gave a problem for that. Do ı need to add them?
> I know that 'A' is used for extruder but ı used remap code(gcode to mcode).
I do not currently have any machine configurations setup for velocity
based extrusion, all my machines use "conventional" position command
rograms use the "E" axis. You
can either get a slicer that outputs Machinekit/LinuxCNC/Mach style
gcode, post-process the gcode file, or setup gcode remapping to handle
the typical RepRap style gcode.
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: http://www.machinekit.io bl
ts that process GPIO input pin data as needed.
...but really I think you'd be best off just using a PRU direct input
pin. IIRC you said you're using a CRAMPS board. If so, several of
the SPI signals function as direct PRU inputs and are already tied to
a connector via a FET bus level translator so
is readily accessible and easy to find.
>
> Thanks
> Cern.
>
> Dne neděle 24. února 2019 18:05:23 UTC+1 Charles Steinkuehler napsal(a):
>>
>> In case it's useful to anyone else:
>>
>> I have written a simple HAL component to interface to an MLX90621
>&g
) and any system with a
standard Linux I2C bus available (eg: /dev/i2c0).
--
Charles Steinkuehler
char...@steinkuehler.net
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You received this message because you are subscribed
1 - 100 of 409 matches
Mail list logo
