[Machinekit] Re: Velocity Extrusion - Dips in Velocity

I had issues with retraction that sound like this, but mine was built as a linear delta so I just disabled retraction and turned rapids up to 500mm/sec which solved it 95%. I haven't returned to it, but I probably should now. I will take a look later. On Monday, June 3, 2019 at 8:26:24 AM

[Machinekit] Re: CRAMPS + BBB Nema 23

The DRV8825 drivers have issues with larger drive voltages when coupled with low inductance motors, probably like your Nema 23 ones. This shows when trying to do microstepping. High voltage and low inductance causes a biasing toward the full step positions, which leads to some 'banding'

Re: [Machinekit] Re: Machinekit on PocketBeagle

Thank you for the work here. I'm about to venture down this rabbit hole myself and this is useful stuff. On Tuesday, May 21, 2019 at 3:24:44 PM UTC-4, mlampert wrote: > > wow - that was quick. I'll have to setup my box for compiling mk, > haven't done that yet. > > For the record, if nobody

[Machinekit] Re: config-pin setting for Mode 0 (gpmc) question

If other pins exist in that location and others are writeable but this one isn't, this means that pin has been claimed by some other device already. Like if you try to use HDMI pins, but don't disable HDMI first... you'll get what you got. The other scenario is you are using the wrong build and

Re: [Machinekit] Transition to Machine Kit for fully custom LinuxCNC build?

I was able to easily exceed the max physical hardware step rate for a DRV8825, which is 250kHz, on 9 channels simultaneously, using a BBB/BBG/BBGW. PRU based stepping is pretty darn fast. The maximum it can do would be based on the internal path it takes (crossing PRU boundaries), the rate you

Re: [Machinekit] Re: Machinekit on BBB; not all configurations load

You need to start a bit further up. https://www.youtube.com/watch?v=sYwr0HMudRg On Thursday, April 4, 2019 at 9:57:29 AM UTC-4, Daren Schwenke wrote: > > It's ok, but starting where you are starting from may take you a while. :) > The error tells you the file and line number in

Re: [Machinekit] Re: Machinekit on BBB; not all configurations load

It's ok, but starting where you are starting from may take you a while. :) The error tells you the file and line number in that file: PocketNC.hal:10: The log also tells you where it was starting from: /home/machinekit/machinekit/configs/ARM.BeagleBone.PocketNC-1 >From there find that file in

[Machinekit] Re: Machinekit on BBB; not all configurations load

Looking at* nothing* else, these are not the same location. It looks like the hal you picked is hard coded to use that path. Machine configuration directory is ' */home/machinekit/machinekit/configs/ARM.BeagleBone.PocketNC-1'* PocketNC.hal:10: execv(

[Machinekit] Re: Nvidia Jetson Nano

implement HALTALK stack on it and have the actual > Machinekit-HAL running on something else (BBB for example). > > Cern. > > Dne středa 20. března 2019 3:57:18 UTC+1 Daren Schwenke napsal(a): >> >> I guess unless some of you work for Nvidia, someone having one already is &

[Machinekit] Re: Nvidia Jetson Nano

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

[Machinekit] Nvidia Jetson Nano

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/

Re: [Machinekit] Additional axis outside kinematics?

to think about it... until now. Looks like an easy fix to just pass it through though. I need to just do it. Thank you Bas. On Saturday, September 8, 2018 at 4:13:49 AM UTC-4, Bas de Bruijn wrote: > > > > On 8 Sep 2018, at 03:40, Daren Schwenke > > wrote: > > I'm not sure

Re: [Machinekit] Additional axis outside kinematics?

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

Re: [Machinekit] Additional axis outside kinematics?

short. So am I correct in saying that adding the extra axis to trivkins would solve the issue also though? On Thursday, September 6, 2018 at 1:16:07 PM UTC-4, Daren Schwenke wrote: > > G0 X10, moves to X10 as an MDI command. G0 A180, does nothing. > I imagine this is because tripodkins doe

Re: [Machinekit] Additional axis outside kinematics?

and analog pins. I believe the Machineface gui, as written, always acts on the joints though. So there I can push the button for A and A moves. On Thursday, September 6, 2018 at 12:24:42 PM UTC-4, Bas de Bruijn wrote: > > > > On 6 Sep 2018, at 12:32, Daren Schwenke > > wrote: &g

Re: [Machinekit] Additional axis outside kinematics?

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

[Machinekit] Additional axis outside kinematics?

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

[Machinekit] Re: RPI high rate GPIO via DMA transfers

, August 12, 2018 at 10:49:55 PM UTC-4, Daren Schwenke wrote: > > Following the other thread on GPIO made me wonder how stable that approach > was going to be, so I went looking around and came across this: > > https://github.com/Wallacoloo/Raspberry-Pi-DMA-Example/blob/master/dma-gp

[Machinekit] RPI high rate GPIO via DMA transfers

Following the other thread on GPIO made me wonder how stable that approach was going to be, so I went looking around and came across this: https://github.com/Wallacoloo/Raspberry-Pi-DMA-Example/blob/master/dma-gpio.c Having DMA handle the GPIO writes removes the CPU from the equation, and his

[Machinekit] Re: RPI gipo help

Curious, what kind of step rates can you reliably get out of this on the Pi? On Sunday, June 17, 2018 at 12:06:02 PM UTC-4, Timothy March wrote: > > Having trouble getting gipo's to work can get all to show up as outputs > but when I load comp no pins are available output or input. The following

[Machinekit] Re: NGCWriter is now in Cura Plugin Repository

Totally awesome. Thank you. On Monday, March 19, 2018 at 3:02:36 PM UTC-4, 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

[Machinekit] Re: Gcode from remote source

Thursday, April 5, 2018 at 9:38:13 PM UTC+2, Daren Schwenke wrote: >> >> Depends on what you are running for your USB. Ethernet, then you are >> good. >> There is the old way using halcmd stuff, and the new way using the >> mkwrapper protocol. >> The la

[Machinekit] Re: Gcode from remote source

Depends on what you are running for your USB. Ethernet, then you are good. There is the old way using halcmd stuff, and the new way using the mkwrapper protocol. The latter is what is used for Machineface and Cetus. I use Machineface for running my machine from my tablet. File transfers are

[Machinekit] Re: mach3 interface board 5 axis

Oh... and be careful, measure stuff first to make sure they don't have pull-up resistors, etc.. If the BBB I/O ever sees 5v you WILL fry it. Ask me how I know... On Tuesday, February 27, 2018 at 2:51:44 PM UTC-5, Daren Schwenke wrote: > > It looks like they use the optocouplers for

[Machinekit] Re: mach3 interface board 5 axis

It looks like they use the optocouplers for inputs and possibly a level converter/buffer/inverting buffer for outputs. Find a good picture of the chip tops and look them up. That picture is not quite good enough. It will probably work fine. Some old laptop parallel ports I've stolen buffer

[Machinekit] Re: Can MK read g-code from serial port?

Short answer, yes although there is a better way. Machinekit can accept gcode from a socket if setup to do so, but what you are asking for with a tablet interface is actually already implemented via Machineface. Injecting gcode is generally reserved for 'dumb' implementations. With

[Machinekit] Re: Slow to start machinekit installed BBG (Linux beaglebone 4.14.16-ti-rt-r30 #1 SMP PREEMPT RT)

I never bothered figuring it out as it still works, but I can tell you I experienced a similar issue. Not related to this, but one thing that helped me later is disabling the window manager. No desktop on the BBG, so it just crashes over and over consuming a surprising amount of resources.

[Machinekit] Re: BiggleBone Red from element 14 and Machinekit with furaday cape

The thread here has what I'm talking about. https://groups.google.com/d/msg/machinekit/RrNLUo4ASP4/1-Aedz5RBgAJ I gathered from this that uboot will still run from the emmc even if you are booting from the sd card. This prevents that, cause it clears the emmc basically. On Monday, January 29,

[Machinekit] Re: BiggleBone Red from element 14 and Machinekit with furaday cape

My guess is you haven't taken the steps required to enable the overlays. Stock debian uses a different layout for the IO pins. What this: bash: line 0: echo: write error: No such file or directory is likely complaining about (badly) is the pins themselves don't exist because you haven't made

[Machinekit] Re: BB-blue BB-enhanced : machinekit and stepper compatibility ?

There are many capes. Please denote which one you are having an issue with. Simplest way to solve this yourself is determine which pins are used on-board (hdmi, wireless, etc), and then cross those to which pins are used for your cape. If any of the logic pins overlap, you will loose that

[Machinekit] Re: CRAMPS Stepper board problem not sure

On Sunday, January 28, 2018 at 7:14:45 PM UTC-5, gary wrote: > > also getting error exceeds machine minimum on axis x and y this is with a > delta with the g code > It is physically possible to move the arms beyond vertical with respect to each tower, but the lineardelta kinematics math

[Machinekit] Re: BBB and new cramps board delta homing problems

I would suggest giving this a try: https://github.com/machinekoder/Rostock-CRAMPS You will need to slice with a modified version of Cura to use it as it is velocity extrusion, but probably a better place to start. On Friday, January 19, 2018 at 9:22:19 AM UTC-5, gary wrote: > > yes i tried

[Machinekit] Re: BBB and new cramps board delta homing problems

On Thursday, January 18, 2018 at 1:07:36 PM UTC-5, gary wrote: > > The first link didn't work... > It's not a link. Look on your device. That directory contains the predefined macros related to FDM. They need to be defined in your ini to exist. > on the BeBoPr++ i thought i changed this >

[Machinekit] Re: BBB and new cramps board delta homing problems

Take a look at /usr/share/linuxcnc/ncfiles/remap-subroutines/fdm A recent example config which uses the fdm files there: https://github.com/Arcus-3d/Arcus-3D-C1-BeBoPr\ Relevant section from ini which map those codes:

[Machinekit] Re: BBB and new cramps board delta homing problems

On Saturday, January 13, 2018 at 2:06:35 PM UTC-5, gary wrote: > > is there a formula for calculating the radius to figure the distance i > need to change it after all corners are done? > Technically, there is an automated way to calculate it all based on the four height measurements, but I've

[Machinekit] Re: BBB and new cramps board delta homing problems

On Thursday, January 11, 2018 at 4:01:08 PM UTC-5, gary wrote: > > I got it to work i had to change remove the - from scale and also the - > from HOME_SEARCH_VEL and now seems to be work correct with the gcode.. > > Been looking for some hal commands to change the axis's values like when >

[Machinekit] Re: BBB and new cramps board delta homing problems

Update your config files on the post bin to reflect their current state and I'll take a look -- 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"

[Machinekit] Re: beaglebone black lcd cape + machinekit working together

Hate to state the obvious but... Start here: https://groups.google.com/forum/#!topic/machinekit/pFV3IgKqJSo On Saturday, December 30, 2017 at 4:52:27 PM UTC-5, Cyrus wrote: > > Hi, > > I am trying to get a touchscreen lcd bbb cape to work with machinekit. > When I install the prebuilt

[Machinekit] Re: Machinekit + Debian Stretch on the BeagleBone Black

Very nice. I'll be referencing that... :) The services to disable for a faster boot is good stuff. I only had to install dirmngr by itself as installing machinekit seemed to pull the rest in for you, but I started with a different image. On Tuesday, December 5, 2017 at 3:51:57 PM UTC-5,

[Machinekit] Re: Inverted tripodkins

On Sunday, November 12, 2017 at 3:39:34 PM UTC-5, Daren Schwenke wrote: > > What I would have expected to be the solution would have been setting > initial homed position with a negative Z value, like this: > [TRAJ] > HOME = 300 250 -300 > When I do that and home though, the

[Machinekit] Re: Inverted tripodkins

just make a new kinematics module which is always inverted. Seems like a waste though. On Saturday, November 11, 2017 at 6:10:32 PM UTC-5, Daren Schwenke wrote: > > I posted the result, not the cause: > > https://github.com/machinekit/machinekit/blob/314246595127ddc2dc08bb0f8a9e8606260e

[Machinekit] Re: PRU/stepgen bug? keeps generating pulses once position-cmd reached

Search this forum for 'PRU Hunting'. On Sunday, November 12, 2017 at 11:58:32 AM UTC-5, Damien D wrote: > > Hello, > > I'm creating my first Machinekit configuration, so far I have been able to > solved everything by myself but now I'm facing annoying issue with stepgen. > I'm using a BBB with

[Machinekit] Re: Inverted tripodkins

I posted the result, not the cause: https://github.com/machinekit/machinekit/blob/314246595127ddc2dc08bb0f8a9e8606260e1679/src/emc/kinematics/tripodkins.c#L202 On Saturday, November 11, 2017 at 6:01:17 PM UTC-5, Daren Schwenke wrote: > > I have been searching for a while for how to imp

[Machinekit] Inverted tripodkins

I have been searching for a while for how to implement tripodkins. Got that sorted, but it's made for struts and not cables. So I actually need inverted tripodkins. Real word the non-inverted tripodkins translates to the opposite compensation occurring. A Z axis coordinated move in the

Re: [Machinekit] Cramps wiring 5 Reference switches to one input?

Please take a photo of the traces so I can determine which circuit they use. If they are the same as 'normal', then they use the phototransistor as a pull-down. It's wired across a 10k and an led + resistor connected to +5. Connect them out in parallel separate from the BBB. If the LED's

[Machinekit] Re: Cramps wiring 5 Reference switches to one input?

If these are switches, you are risking nothing. It will work fine. Just make sure to use the same logic level ground or +3.3v for all of them. If they are optical, they may 'fight' over the logic level to provide so that would require additional thought. On Thursday, November 9, 2017 at

Re: [Machinekit] Re: hal_pru_generic not making steps/pwm, Debian Stretch 4.4.91-ti-rt kernel, BBGW

It was my config-pin settings. I was setting the mode for the PRU pins to 'gpio'. I changed them all to 'low' and now it works. On Monday, November 6, 2017 at 5:56:04 PM UTC-5, Charles Steinkuehler wrote: > > On 11/6/2017 4:42 PM, Daren Schwenke wrote: > > I started over with De

Re: [Machinekit] Re: hal_pru_generic not making steps/pwm, Debian Stretch 4.4.91-ti-rt kernel, BBGW

into the CRAMPS config and find out. On Monday, November 6, 2017 at 11:04:43 AM UTC-5, Daren Schwenke wrote: > > > > On Monday, November 6, 2017 at 8:37:21 AM UTC-5, Charles Steinkuehler > wrote: >> >> That processor is supposed to have the PRUs, so I'm not sure what'

Re: [Machinekit] Re: hal_pru_generic not making steps/pwm, Debian Stretch 4.4.91-ti-rt kernel, BBGW

On Monday, November 6, 2017 at 11:46:29 AM UTC-5, Robert Nelson wrote: > > On Mon, Nov 6, 2017 at 10:34 AM, Daren Schwenke <darens...@gmail.com > > wrote: > > > > > > On Monday, November 6, 2017 at 11:04:43 AM UTC-5, Daren Schwenke wrote: > >> &g

Re: [Machinekit] Re: hal_pru_generic not making steps/pwm, Debian Stretch 4.4.91-ti-rt kernel, BBGW

On Monday, November 6, 2017 at 11:04:43 AM UTC-5, Daren Schwenke wrote: > > > > On Monday, November 6, 2017 at 8:37:21 AM UTC-5, Charles Steinkuehler > wrote: >> >> That processor is supposed to have the PRUs, so I'm not sure what's >> going wrong. I don'

Re: [Machinekit] Re: hal_pru_generic not making steps/pwm, Debian Stretch 4.4.91-ti-rt kernel, BBGW

ig. I'm going to start over with a working config and narrow it down to a couple pins toggling and see what happens. > > On 11/5/2017 7:53 PM, Daren Schwenke wrote: > > am3358bzcz100 <http://www.ti.com/lit/ds/symlink/am3358.pdf> > > > > BBGW <https://beagleboard.org/gr

Re: [Machinekit] Re: hal_pru_generic not making steps/pwm, Debian Stretch 4.4.91-ti-rt kernel, BBGW

I'm going to try starting with Jessie and see if I fare any better. I'll get another data point then at least. Too many variables right now. On Sunday, November 5, 2017 at 8:59:48 PM UTC-5, Daren Schwenke wrote: > > In case you are wondering why I picked such an ancient cape to model &

Re: [Machinekit] Re: hal_pru_generic not making steps/pwm, Debian Stretch 4.4.91-ti-rt kernel, BBGW

On Sunday, November 5, 2017 at 8:53:56 PM UTC-5, Daren Schwenke wrote: > > am3358bzcz100 <http://www.ti.com/lit/ds/symlink/am3358.pdf> > > BBGW <https://beagleboard.org/green-wireless> > On Sunday, November 5, 2017 at 7:59:31 PM UTC-5, Charles Steinkuehler > wrote: >

Re: [Machinekit] Re: hal_pru_generic not making steps/pwm, Debian Stretch 4.4.91-ti-rt kernel, BBGW

am3358bzcz100 <http://www.ti.com/lit/ds/symlink/am3358.pdf> BBGW <https://beagleboard.org/green-wireless> On Sunday, November 5, 2017 at 7:59:31 PM UTC-5, Charles Steinkuehler wrote: > > On 11/5/2017 5:04 PM, Daren Schwenke wrote: > > On Sunday, November 5, 2017 at

Re: [Machinekit] Re: hal_pru_generic not making steps/pwm, Debian Stretch 4.4.91-ti-rt kernel, BBGW

On Sunday, November 5, 2017 at 1:21:40 PM UTC-5, Daren Schwenke wrote: > > > > On Sunday, November 5, 2017 at 12:29:42 PM UTC-5, Charles Steinkuehler > wrote: >> >> On 11/5/2017 7:23 AM, Daren Schwenke wrote: >> > On Sunday, November 5, 2017 at 8:

Re: [Machinekit] Re: hal_pru_generic not making steps/pwm, Debian Stretch 4.4.91-ti-rt kernel, BBGW

On Sunday, November 5, 2017 at 1:21:40 PM UTC-5, Daren Schwenke wrote: > > > > On Sunday, November 5, 2017 at 12:29:42 PM UTC-5, Charles Steinkuehler > wrote: >> >> On 11/5/2017 7:23 AM, Daren Schwenke wrote: >> > On Sunday, November 5, 2017 at 8:

Re: [Machinekit] Re: hal_pru_generic not making steps/pwm, Debian Stretch 4.4.91-ti-rt kernel, BBGW

On Sunday, November 5, 2017 at 12:29:42 PM UTC-5, Charles Steinkuehler wrote: > > On 11/5/2017 7:23 AM, Daren Schwenke wrote: > > On Sunday, November 5, 2017 at 8:01:59 AM UTC-5, Daren Schwenke wrote: > >> On Sunday, November 5, 2017 at 7:51:02 AM UTC-5, Charles Ste

Re: [Machinekit] Re: hal_pru_generic not making steps/pwm, Debian Stretch 4.4.91-ti-rt kernel, BBGW

On Sunday, November 5, 2017 at 8:01:59 AM UTC-5, Daren Schwenke wrote: > > > > On Sunday, November 5, 2017 at 7:51:02 AM UTC-5, Charles Steinkuehler > wrote: >> >> On 11/5/2017 6:37 AM, Daren Schwenke wrote: >> > That's the confusing part

Re: [Machinekit] Re: hal_pru_generic not making steps/pwm, Debian Stretch 4.4.91-ti-rt kernel, BBGW

On Sunday, November 5, 2017 at 7:51:02 AM UTC-5, Charles Steinkuehler wrote: > > On 11/5/2017 6:37 AM, Daren Schwenke wrote: > > That's the confusing part. Things work fine with hal_bb_gpio, and not > with > > hal_pru_generic. > > > > The estop hardware l

Re: [Machinekit] Re: hal_pru_generic not making steps/pwm, Debian Stretch 4.4.91-ti-rt kernel, BBGW

affect. > > If either of those fail, the PRU is probably not working for the same > reason...get the above fixed and things ought to work better. > > On 11/4/2017 11:24 PM, Daren Schwenke wrote: > > I noticed most of my pins were tied to PRU 1, so I moved one pin so

[Machinekit] Re: hal_pru_generic not making steps/pwm, Debian Stretch 4.4.91-ti-rt kernel, BBGW

end. https://pastebin.com/96ZWP0KD On Saturday, November 4, 2017 at 7:27:51 PM UTC-4, Daren Schwenke wrote: > > > > On Saturday, November 4, 2017 at 7:21:21 PM UTC-4, Daren Schwenke wrote: >> >> Suppose this would be useful info. Started with this image: >> >> h

[Machinekit] Re: hal_pru_generic not making steps/pwm, Debian Stretch 4.4.91-ti-rt kernel, BBGW

On Saturday, November 4, 2017 at 7:21:21 PM UTC-4, Daren Schwenke wrote: > > Suppose this would be useful info. Started with this image: > > https://rcn-ee.com/rootfs/bb.org/testing/2017-10-29/stretch-iot/BBB-blank-debian-9.2-iot-armhf-2017-10-29-4gb.img.xz > Did the stuff for

[Machinekit] Re: hal_pru_generic not making steps/pwm, Debian Stretch 4.4.91-ti-rt kernel, BBGW

, Daren Schwenke wrote: > > BBGW with a 'mostly' BeBoPr cape. Hand wired, very basic, with some pins > moved so they didn't step on wifi. > Booting from eMMC. > > Config here. Starts, no errors. > https://github.com/Arcus-3d/Arcus-3D-C1-BeBoPr > > GPIO works, trigger

[Machinekit] hal_pru_generic not making steps/pwm, Debian Stretch 4.4.91-ti-rt kernel, BBGW

BBGW with a 'mostly' BeBoPr cape. Hand wired, very basic, with some pins moved so they didn't step on wifi. Booting from eMMC. Config here. Starts, no errors. https://github.com/Arcus-3d/Arcus-3D-C1-BeBoPr GPIO works, triggering estop and machine power correctly. halcmd shows it should be

Re: [Machinekit] Re: Goldibox

Yes it's excessive, over the top, and somewhat pointless, but an excessive demo which shows the journey from beginning to end in a space where documentation is sparse is definitely better than no demo at all. -- website: http://www.machinekit.io blog: http://blog.machinekit.io github:

Re: [Machinekit] Re: Goldibox

gt; [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 <jo...@zultron.com > > > <mailto:jo...@zultron.com >> wrote: > > > > On 11/01/2017 10:15 AM, Daren Schwenke wro

Re: [Machinekit] Re: Goldibox

when people do silly things like switching from full cool to full heat. On Wednesday, November 1, 2017 at 11:40:10 AM UTC-4, John Morris wrote: > > > > On 11/01/2017 10:15 AM, Daren Schwenke wrote: > > When switching peltiers between heat/cool mode you can get some really

[Machinekit] Re: Goldibox

Neat idea, and perfect name. :) 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" > [1]. Kind of like a cross between a fridge and an incubator, you set > minimum and maximum temperatures on its

Re: [Machinekit] Re: Arcus3D-C1 Open source tripodkins cable printer.

The mixing head was not open source. Everything else was. That was a misquote. At least it will not be until we can get to producing them ourselves, so the cost/benefit analysis people will do will land on the side of 'just buy it'. We were trying to be totally self-funded to do so, but the

[Machinekit] Re: Arcus3D-C1 Open source tripodkins cable printer.

Featured on Hackaday, again. :) http://hackaday.com/2017/10/12/this-3d-cable-printer-remixes-the-delta/ Go Machinekit! Still need to build a tripodkins config with Machineface... On Friday, October 6, 2017 at 5:10:35 PM UTC-4, Daren Schwenke wrote: > > Built this with the intent of r

Re: [Machinekit] Arcus3D-C1 Open source tripodkins cable printer.

at 11:55:15 AM UTC-4, Daren Schwenke wrote: > > > > On Saturday, October 7, 2017 at 8:16:49 AM UTC-4, Bas de Bruijn wrote: >> >> >> >> On 6 Oct 2017, at 23:10, Daren Schwenke <darens...@gmail.com> wrote: >> >> Built this with the intent of run

Re: [Machinekit] Arcus3D-C1 Open source tripodkins cable printer.

On Saturday, October 7, 2017 at 8:16:49 AM UTC-4, Bas de Bruijn wrote: > > > > On 6 Oct 2017, at 23:10, Daren Schwenke <darens...@gmail.com > > wrote: > > Built this with the intent of running Machinekit/tripodkins with it. > Have not worked on the config ye

[Machinekit] Arcus3D-C1 Open source tripodkins cable printer.

Built this with the intent of running Machinekit/tripodkins with it. Have not worked on the config yet, but the hardware looks like it will work now, so soon. https://hackaday.io/project/26938-arcus-3d-c1-cable-printer https://youtu.be/KQ19fT4BQQU -- website: http://www.machinekit.io blog:

Re: [Machinekit] Re: Machinekit at the Milwaukee Maker Fair.

sy. > Switches are wired and installed I need to install terminals, and hook > into the cramps and redo the Hal and ini's. Yikes, I'm running out of time > here. > > > > On Sep 14, 2017 2:47 AM, "Daren Schwenke" <darens...@gmail.com > > wrote: > >>

[Machinekit] Re: Machinekit at the Milwaukee Maker Fair.

I'm at my other home in FL currently and crashed the head on the printer, destroying part of the head and splitting my ceramic bed. Nema23 and 9mm belts may have been a bad choice. Tried updating to use the new pythonic configs and it turns out in the current fdm module (without using the

Re: [Machinekit] Re: hal_temp_bbb locked up, now.

ebone:/sys/devices/bone_capemgr.9$ cat slot slot-4/ slot-5/ slot-6/ slot-7/ slot-8/ slots machinekit@beaglebone:/sys/devices/bone_capemgr.9$ cat slots ^C^C^C On 9/6/2017 11:36 AM, Daren Schwenke wrote: > > machinekit@beaglebone:~/git/Arcus-3D-M2$ ls -al > > /sys/devices/ocp.3/4

[Machinekit] Re: hal_temp_bbb locked up, now.

at 12:12:40 PM UTC-4, Daren Schwenke wrote: > > I have a BBB with hal_temp_bbb locked up, right now... still running. > What should I gather here to help diagnose why? > > Everything else seems normal, just no temp updates. > -- website: http://www.machinekit.io blog: http://blog.ma

[Machinekit] Re: BBB and Axis gui

The perceived lack of performance of Axis on the BBB is due to software rendering. It's not a memory constraint. The hardware acceleration of graphics is broken in the earlier kernels, which is what xenomai currently works on. Newer kernels use xenomai 3 (I believe) and we don't. The newer

[Machinekit] Re: hal_temp_bbb locked up, now.

/44e0d000.tscadc/tiadc/iio:device0/in_voltage4_raw cat: /sys/devices/ocp.3/44e0d000.tscadc/tiadc/iio:device0/in_voltage4_raw: Resource temporarily unavailable machinekit@beaglebone:~/git/Arcus-3D-M2$ On Wednesday, September 6, 2017 at 12:12:40 PM UTC-4, Daren Schwenke wrote: > > I have

[Machinekit] hal_temp_bbb locked up, now.

I have a BBB with hal_temp_bbb locked up, right now... still running. What should I gather here to help diagnose why? Everything else seems normal, just no temp updates. -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received

[Machinekit] Re: Running 3D Printer using Machinekit + CRAMPS + BBB

I have run this in the past with no issues. My current testing machine is targeting the BBGW though, so it's using rt-preempt (so wireless works) and the BeBoPr config instead (as CRAMPS shares pins with the wifi/bluetooth module) So I can't directly assist you atm. On Sunday, September 3,

Re: [Machinekit] M-Code errors

Up to 2.3.1 works with his walkthrough. On Thursday, August 31, 2017 at 9:01:58 AM UTC-4, Pranav Pandey wrote: > > No, I didn't use the Cura 2.1.3. I am using the latest version 2.7. I will > try with the 2.1.3 version once > > On 31 Aug 2017 18:11, "Bas de Bruijn" >

[Machinekit] Re: M-Code errors

The Cura plugin also requires you to create a machine that uses it. It's also made for velocity extrusion, so you would need to use a config that also uses velocity extrusion. It's one or the other. Then you will be outputting ngc files instead of gcode, and E/A will disappear. E/A will be

[Machinekit] Re: M-Code errors

If you want to simplify your life, and don't mind a remote interface, I would go a little different route. Axis still sucks on the BBB due to software rendering sucking up most of the CPU. The solution to that is use a remote interface. The one for 3D printing is 'Machineface'. That and the

[Machinekit] Re: Machinekit on the BeagleBone Green Wireless (BBGW) + CRAMPS

Tried linux-image-4.9.40-bone-rt-r7. It's 15% better for processor usage, but still a lot higher than xenomai. 3735 root 20 0 63524 58884 10816 S 30.4 11.7 0:29.66 rtapi:0 3754 machine+ 20 0 14608 9260 6644 S 3.3 1.8 0:03.32 hal_temp_bbb 3766

[Machinekit] Re: Machinekit on the BeagleBone Green Wireless (BBGW) + CRAMPS

One more thing. You may need to do this to force it to use the uboot version on your SD card instead of the eMMC. sudo dd if=/dev/zero of=/dev/mmcblk1 count=1 seek=1 bs=128k On Saturday, July 29, 2017 at 4:39:49 PM UTC-4, Daren Schwenke wrote: > > Everything works, with the caveat of

[Machinekit] Re: Machinekit on the BeagleBone Green Wireless (BBGW) + CRAMPS

Everything works, with the caveat of really high processor utilization. About 80-90% all the time, with rtapi:0 taking about 50% of that. This makes for a slower user interface even when using remote. But, that doesn't seem to affect operation as I've printed 2 good looking 1.5 hour parts so

Re: [Machinekit] Re: Machinekit on the BeagleBone Green Wireless (BBGW) + CRAMPS

lt;robertcnel...@gmail.com> wrote: > On Fri, Jul 28, 2017 at 11:41 PM, Robert Nelson <robertcnel...@gmail.com> > wrote: > > On Fri, Jul 28, 2017 at 5:40 PM, Daren Schwenke <darenschwe...@gmail.com> > wrote: > >> So I think this is getting really cl

[Machinekit] Re: Machinekit on the BeagleBone Green Wireless (BBGW) + CRAMPS

2 root 20 0 000 S 0.0 0.0 0:00.00 kthreadd 5 root 0 -20 000 S 0.0 0.0 0:00.00 kworker/0:0H On Friday, July 28, 2017 at 6:40:06 PM UTC-4, Daren Schwenke wrote: > > So I think this is getting really close now. I'm com

[Machinekit] Re: Machinekit on the BeagleBone Green Wireless (BBGW) + CRAMPS

So I think this is getting really close now. I'm compiling again so I can remove the dependencies outside of the RIP build I have. So I'm going to take this and sort the last few thingies here (by removing them) and test it on a real machine. Then, if it works, I'll compile a list of what had

Re: [Machinekit] Re: Machinekit on the BeagleBone Green Wireless (BBGW) + CRAMPS

They don't work so well headless. :) On Friday, July 28, 2017 at 4:34:52 PM UTC-4, Charles Steinkuehler wrote: > > On 7/28/2017 3:25 PM, Daren Schwenke wrote: > > found the new path and changed 154 to: > > syspath = > > '/sys/devices/platform/ocp/44e0d000.tscadc/T

Re: [Machinekit] Re: Machinekit on the BeagleBone Green Wireless (BBGW) + CRAMPS

0.tscadc/tiadc/iio:device0/ > > > https://github.com/machinekit/machinekit/blob/master/src/hal/user_comps/hal_temp_bbb.py#L154 > > > On 7/28/2017 2:59 PM, Daren Schwenke wrote: > > Ok. Pointed it directly at your file. Further: > > > machinekit@b

Re: [Machinekit] Re: Machinekit on the BeagleBone Green Wireless (BBGW) + CRAMPS

and in the terminal stopping configserver... done machinekit@beaglebone:~/machinekit/configs/ARM/BeagleBone/Fabrikator-Mini-CRAMPS$ On Friday, July 28, 2017 at 3:40:16 PM UTC-4, Charles Steinkuehler wrote: > > On 7/28/2017 1:44 PM, Daren Schwenke wrote: > > > > machinekit@beag

Re: [Machinekit] Re: Machinekit on the BeagleBone Green Wireless (BBGW) + CRAMPS

completed successfully.# # If things don't work check config.log for errors & warnings # machinekit@beaglebone:~/machinekit/src$ make -j 1 On Friday, July 28, 2017 at 3:40:16 PM UTC-4, Charles Steinkuehler wrote: > > On 7/28/2017 1:44 PM, Daren Schwenke wrote: > >

Re: [Machinekit] Re: Machinekit on the BeagleBone Green Wireless (BBGW) + CRAMPS

Well, specifically I did this, which is probably a new combination for the beagle: debian/configure -pr ./configure --with-platform-beaglebone --with-rt-preempt On Friday, July 28, 2017 at 2:44:08 PM UTC-4, Daren Schwenke wrote: > > I followed these: > http://www.machinekit.io/docs/d

Re: [Machinekit] Re: Machinekit on the BeagleBone Green Wireless (BBGW) + CRAMPS

ell command 'dmesg' and in the terminal stopping configserver... done machinekit@beaglebone:~/Arcus-3D-M2$ On Friday, July 28, 2017 at 2:30:49 PM UTC-4, Charles Steinkuehler wrote: > > On 7/28/2017 1:20 PM, Daren Schwenke wrote: > > I'll try that. > > Loaded up my non-pythonic

Re: [Machinekit] Re: Machinekit on the BeagleBone Green Wireless (BBGW) + CRAMPS

nekit@beaglebone:~/Arcus-3D-M2$ date Fri Jul 28 18:19:11 UTC 2017 On Friday, July 28, 2017 at 2:09:08 PM UTC-4, Charles Steinkuehler wrote: > > On 7/28/2017 12:59 PM, Daren Schwenke wrote: > > After the dd, it now takes a seriously long time to boot. > > Before it was ~45 second

Re: [Machinekit] Re: Machinekit on the BeagleBone Green Wireless (BBGW) + CRAMPS

at 1:59:41 PM UTC-4, Daren Schwenke wrote: > > After the dd, it now takes a seriously long time to boot. > Before it was ~45 seconds till it was back on the network. Now it takes > around 5 minutes. > > On Friday, July 28, 2017 at 11:21:09 AM UTC-4, Robert Nelson wrote: >>

Re: [Machinekit] Re: Machinekit on the BeagleBone Green Wireless (BBGW) + CRAMPS

After the dd, it now takes a seriously long time to boot. Before it was ~45 seconds till it was back on the network. Now it takes around 5 minutes. On Friday, July 28, 2017 at 11:21:09 AM UTC-4, Robert Nelson wrote: > > On Fri, Jul 28, 2017 at 10:06 AM, Daren Schwenke > <darens.

Re: [Machinekit] Re: Machinekit on the BeagleBone Green Wireless (BBGW) + CRAMPS

pick. On Friday, July 28, 2017 at 11:52:29 AM UTC-4, Robert Nelson wrote: > > On Fri, Jul 28, 2017 at 10:50 AM, Charles Steinkuehler > <cha...@steinkuehler.net > wrote: > > On 7/28/2017 10:46 AM, Daren Schwenke wrote: > >> > >> > machinekit@beag

  1   2   >