On 29.03.17 19:56, Bruce Layne wrote:
> I'd still like to finish that project but a lot has changed since then
> in the fast moving 3D printer world, including much better extruders, so
> it would require some time to learn and hack in some upgrades to
> maximize reliability and print quality.
This thread renewed my interest in 3D printing. I bought the parts and
did the mechanical assembly of a Hadron ORDbot a few years ago but
wanted to do a nice electrical installation instead of the usual rat's
nest wiring on most home brew 3D printers. Then the complete kit became
available an
On 30 March 2017 at 00:06, Gregg Eshelman wrote:
> The Select Mini Version 2 is supposed to be out sometime soon. It has
> improvements like a cooling fan in the base.
> Here's a video showing the V2 updates.
> https://www.youtube.com/watch?v=c43HVaiSF88
I don't seem to be able to find a UK sou
The Select Mini Version 2 is supposed to be out sometime soon. It has
improvements like a cooling fan in the base.
Here's a video showing the V2 updates.
https://www.youtube.com/watch?v=c43HVaiSF88
On Wednesday, March 29, 2017, 2:36:53 AM MDT, John Alexander Stewart
wrote:Greg:
If you want ine
On 3/29/2017 10:52 AM, Jon Elson wrote:
>>
> Maybe contact Charles Steinkuehler first, as he is an active
> 3D printer user and knows what is currently hot.
> There is a HUGE turnover in these things, and what was the
> best design a couple months ago is now obsolete.
I'm no longer really "curre
It's me again ... :-)
While in the [TRAJ] section of the INI file is see the variable CYCLE_TIME =
0.010, but is not mentioned in the INI config documents. I am only guessing
that this is the polling interval time for the trajectory planner but am not
sure. Can I add this to my list?
Thanks
Hello all,
I am going through the INI file of my stepper based Gantry machine and am
looking at the [EMCMOT] section. In this section I see two variables:
COMM_TIMEOUT = 1.0
COMM_WAIT = 0.010
I am guessing they have something to do with the communication times, but the
INI Configuration se
Ah - it does work.. (the axis splash screen has G64 - resetting the ini
startup..)
sam
On 03/29/2017 02:39 PM, Todd Zuercher wrote:
> It works, but... And this is a big but. If an operator or machine file
> changes the g64 setting, it will not be changed back to that default start up
> setti
That will be overridden by the G code program so not a safe thing to do.
JT
On 3/29/2017 1:54 PM, Tomas J wrote:
>> Currently the fix is adding G64Px.xxx at the beginning of all programs.
> Or add "RS274NGC_STARTUP_CODE = G64 P0.02" to [RS274NGC] section of .ini
> file...
>
---
In the case I am working on the disable option would work just fine.
On Wed, Mar 29, 2017 at 2:39 PM, Todd Zuercher
wrote:
> It works, but... And this is a big but. If an operator or machine file
> changes the g64 setting, it will not be changed back to that default start
> up setting until th
It works, but... And this is a big but. If an operator or machine file changes
the g64 setting, it will not be changed back to that default start up setting
until the next time Linuxcnc is closed and restarted. This is why a proper
proper file preamble for your g-code files is so important. A
Does that work? I tried that on 2.7 sim and it didn't seem to work.
(unless I was doing something stupid)
On 3/29/2017 1:54 PM, Tomas J wrote:
>> Currently the fix is adding G64Px.xxx at the beginning of all programs.
> Or add "RS274NGC_STARTUP_CODE = G64 P0.02" to [RS274NGC] section of .ini
>
> Currently the fix is adding G64Px.xxx at the beginning of all programs.
Or add "RS274NGC_STARTUP_CODE = G64 P0.02" to [RS274NGC] section of .ini
file...
--
Best regards,
Tomas
--
Check out the vibrant tech community
I agree on both counts, that G0 should always be exact stop, and that the
behavior should be configurable via an INI setting (maybe not HAL, because
switching settings online would have weird side effects). It should be an
easy change (there is one location in the TP that does pre-checks for
blend
I agree somewhat. :) I think it should be a hal pin or a ini setting
sam
On 3/29/2017 12:43 PM, Todd Zuercher wrote:
> My personal opinion is that all G0 moves should always be exact stop
> positioning moves not blended moves. To treat them as anything else seems
> silly. If the previous be
My personal opinion is that all G0 moves should always be exact stop
positioning moves not blended moves. To treat them as anything else seems
silly. If the previous behavior of Linuxcnc was to blend them, then it is just
plane wrong and should be corrected. Having multiple G0 moves executed
ok - thanks - I will try it.
On Wed, Mar 29, 2017 at 11:21 AM, sam sokolik
wrote:
> From the manual
>
> 'G64 and G64 P0 tell the planner to sacrifice path following accuracy in
> order to keep the feed rate up.'
>
> So G64 and G64P0 are the same. (go as fast as you can - cutting corners)
>
> Y
On Wed, Mar 29, 2017 at 1:00 AM, Erik Christiansen
wrote:
>
> Where the 3D printer would be in front is forming nice fillets, as in
> the transition from a boss to its supporting surface, and inside a
> pulley rim, going to the spokes. With foam fabrication, it may be
> necessary to affix a squar
From the manual
'G64 and G64 P0 tell the planner to sacrifice path following accuracy in
order to keep the feed rate up.'
So G64 and G64P0 are the same. (go as fast as you can - cutting corners)
You would need to set the maximum divination you want.
G64P.005 - go as fast as you can but don't
The customer reported that adding G64P0 at the front of the program did not
fix the problem.
I was not in attendance so I cannot verify the command was correctly
applied.
I will get the ARC_BLEND_ENABLE = 0 in the ini file and report back.
thanks
Stuart
On Wed, Mar 29, 2017 at 10:22 AM, sam sok
On 03/28/2017 09:48 AM, andy pugh wrote:
> I find myself astonished that I don't have a 3D printer.
> I am thinking of buying one.
> Longer-term I think I will end up making a large-format delta pritner,
> so the one I buy will be more ot a toe-dipping exercise, and I am
> looking at:
> http://www.
The cheap and dirty way would be to add
add in the TRAJ sectio/n
ARC_BLEND_ENABLE = 0
/This puts the trajectoy planner into pre 2.7 mode (pre circular arc
blend - 1 segment look ahead)
You obviously lose x segment look ahead. During testing exact stop mode
happened between G0 and contouring m
Gentlemen,
This is connected to the G64 question I asked on the developers list
yesterday.
G64 P0 does not change the positioning problem on the machine.
Problem description:
desired machine motion
position XY with Z above the material/work level
move Z to material/work
Greg:
If you want inexpensive but good quality and compact, check out the
> Monoprice Select Mini. (AKA Malyan M200)
>
Very interesting - thank you for the pointer. I may have to re-think my "no
3D printer at home"...
John.
Traditional pattern making was 3d built up, did not need subtractive
milling or 3d plastic printer
:)
Dave Caroline
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! ht
Laying down even amounts of metal with a mig is surprisingly difficult.
Many years I had to build up some shafts so I rigged up a setup in an
old lathe with the torch clamped in the tool post. The problem I found
was that if you get a high spot you end up depositing more metal on the
high spot
On 28.03.17 15:48, andy pugh wrote:
> I find myself astonished that I don't have a 3D printer.
> I am thinking of buying one.
> Longer-term I think I will end up making a large-format delta pritner,
> so the one I buy will be more ot a toe-dipping exercise, and I am
> looking at:
> http://www.ebay.
27 matches
Mail list logo