> Its been a weekend of Torment trial and error and head bashing
Setting up a controller for a new kind of machine is a difficult
undertaking. You need to understand many, many things, from
underlying physical and mathematical theory, all the way to very
practical matters. Take your time trying to understand these
matters, before acting. You really need to understand what
"feed-rate" and "acceleration" (or "jerk") mean, for the machine.
How is it related to friction and momentum? Get
your head wrapped around it, instead of "trial and error and head
bashing". The latter will not let you reach your goal.
If you don't believe in yourself, or don't have the time or
patience, get a new TinyG and follow the Liteplacer
documentation, use proven configs from the many Liteplacer +
TinyG + OpenPnP users.
But I'm sure you can do it. Hang in there!Setting up a Duet controller initially is a bit of a leap, because the online-configurator is only really good for a 3D printer (last time I looked). So you need to get your config.g right, manually.
Because the Duet people probably think they got it covered with the configurator, there is no high-level guidance for manual configuration (AFAIK). But the individual configuration commands are very, very well documented. You just need to take your time, putting the puzzle together, one piece after the other. RTFM!
And for a jump start, I sent you a link to Wolfgang's config before. Have you looked at it?
After that, please be sure to follow Issues & Solutions
in OpenPnP. It should recognize Duet and propose the right
solutions for you. Use the blue [i] buttons for help from the
Wiki. Do not try to do it manually.
If you already tried manually, consider starting a fresh OpenPnP
config from scratch.
When you don't understand an issue or solution, or when you think
I&S must be wrong, come back here with the specifics. Do not
dismiss or manually override I&S, just to "make it go away and
hope for the best".
Download the latest testing version, it has extended support:
For the Kinetics, you can not port over the TinyG
settings, because TinyG has Jerk control, whereas Duet
only has Acceleration control. And the Liteplacer software
makes a big mess of that, confusing the physical terms "jerk"
and "acceleration", so forget all what you saw there.
Instead, think physical:
Try to really understand the settings:
Start with low speeds. Get control first, break records
And remember: follow Issues & Solutions!
You received this message because you are subscribed to the Google Groups "OpenPnP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openpnp+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/c320d7ca-99bd-40c9-aec9-ae05d716f28cn%40googlegroups.com.
"And for a jump start, I sent you a link to Wolfgang's config before. Have you looked at it?
I did use this exact file ( of course with my alterations to get the results required ) and if you check my first post has the config.g attached .
Send the machine.xml for the
For the Duet side, I'm no expert and frankly, I cannot provide
support for everything, I have to leave this to others. I
don't understand, why Wolfgang's config, combined with the
excellent documentation by Duet, does not give you pointers for all
that is needed on a simple machine like a Liteplacer.
Maybe @dc42 of Duet can help.
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/161c6777-7dca-4810-9f2f-3d68c295bfd3n%40googlegroups.com.
> Does OpenPnP provide a trace facility that allows you to see what G-code commands it is sending to the Duet?
Yes. The log will (among many other things) log the commends
sent, with timestamps etc.. You need to set logging to TRACE level
on the Log tab.
There is also a dedicated Log Gcode option on the driver.
It will log the Gcode in a separate log file, i.e. without all the
other stuff (no timestamps, though).
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/58280af5-e4ca-44b6-aed1-feb8e80ec02an%40googlegroups.com.
You received this message because you are subscribed to a topic in the Google Groups "OpenPnP" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openpnp/fAF-xz17e5A/unsubscribe.
To unsubscribe from this group and all its topics, send an email to openpnp+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/7084a7ae-1098-57c6-5f5f-687c1cb9c3f6%40makr.zone.
OpenPnP is showing you conceptual tool coordinates. So
for one thing they depend on the tool selected in Machine
Controls. If you move the Nozzle to a certain X/Y coordinate, and
then the camera to the same X/Y coordinates, they should be on the
same spot. But obviously the controller will have different
coordinates, because the Nozzle is shifted (by the so-called head
offsets) from the Camera.
There can be other things, like axis transformations, run-out
compensation, etc. if applicable.
All that's the difference between raw controller coordinates and
conceptual OpenPnP coordinates.
As to the other questions, it seems you really need to increase
your knowledge about such machines. Learn about homing and a safe
homing order (e.g. Z must home to max first, and only then can X/Y
home safely). To a minimal degree, you need to understand these
things. From an OpenPnP stand-point, we take such a level of
understanding and controller side setup for granted.
To be a bit blunt: this is not a Product Support Service channel,
this is still a DIY community, and the Y means "Yourself" 😁.
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/456f6dcf-b250-48ab-bab6-193bc5d1f4acn%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/49913266-d30f-4a96-a116-310e1fd603dan%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openpnp/ce3da365-3018-4789-aa11-ea68dcb20f1an%40googlegroups.com.