Show all posts by user
Page 1 of 1 Pages: 1
Results 1 — 10 of 10
Quoteteikjoon
Quotehg42
It is scalable and flexible like hell...
you can have a dedicated controller for each axis and each heater etc. (e.g. take 2-5EUR Arduino Nanos).
Poked around in the klipper documentation to see how I could do this
but keep in mind, this is only a potential thing to do, if you need scalability, or may be you like the modular approach.
A simple mega2560/RAMPS combination
by
hg42
-
Firmware - experimental, borrowed, and future
Quoteteikjoon
am I correct to assume that I would need to wire up a stepper driver to each Arduino Nano, load up the firmware with them (configuring its alias) and then connect all of them to the main Raspberry Pi through a USB hub?
3 x yes
Note I should have said "could" instead of "can" because there are some limitations.
For a corexy it is currently necessary to have XY on the same CPU, bec
by
hg42
-
Firmware - experimental, borrowed, and future
to be clear...
if you want a (high end) system working out of the box, a Duet (or other 32bit boards) is a good choice.
Such "one board does it all" solutions are especially well suited to a professional environment, where high availability and a low failure rate are wanted or necessary.
Boards like Duet or Smoothieboard are also well designed for high standards in security and durability.
I als
by
hg42
-
Firmware - experimental, borrowed, and future
Quotenewbob
I like that large part of Klipper (including configuration) is on Rpi and can be modified almost on the fly, no recomplile/flash needed.
I agree, it's another level of flexibility.
On Smoothieware you can edit the configuration and restart.
On Klipper you can edit just about every aspect that matters and restart.
Now many developers will say, today you compile very fast and you can
by
hg42
-
Firmware - experimental, borrowed, and future
"25 times a second" cannot be mentioned anywhere because it's definitely not true...
"NTP like" isn't mentioned anywhere, it's my own conclusion from the code I have looked at (not thoroughly).
This looked for me like:
send a request for a timestamp (taking some time to go through the communication channel),
receive the timestamp,
take the half between the times of the request and reception of
by
hg42
-
Firmware - experimental, borrowed, and future
@Traumflug you are not asking a question but spitting out general offensive sentences about other people. Simply stop that and anything will go smoothly.
Example:
QuoteMy personal conclusion about this is that technical quality doesn't really matter as long as the result somehow gets a printer moving
you are basically saying Klipper doesn't have technical quality and everybody is stupid
You ca
by
hg42
-
Firmware - experimental, borrowed, and future
QuoteThe only absurd here is that you can't even tell us how often stepper speeds are updated. Instead you point to some documentation like a broken record. Documentation which does not answer the question.
because the question is absurd, if you read the documentation.
The documentation tells you, that
the host calculates step times exactly with constant acceleration, no approximation, no stai
by
hg42
-
Firmware - experimental, borrowed, and future
QuoteKlipper uses the same tricks as everybody else. Pre-calculate movements, then approximate steps. As far as I can see, acceleration is done on the host side, so it can accelerate by stair-stepping only. Stair-stepping is fine, but not "physically exact".
as I understand the docs (didn't look into the low level code yet), an acceleration fucntion (currently constant but may be S curve etc.) i
by
hg42
-
Firmware - experimental, borrowed, and future
@Traumflug I don't agree
QuoteTraumflug
Thanks for the charming words, but I disagree. Teacup always came with excellent performance. It comes with not hackish, but well designed code. It has demonstrated to do 1'600'000 steps/seconds (right, that's 1.6 MHz of synchronized stepper movements). It does evenly distributed stepper steps, avoiding Bresenham. It comes with a dedicated configuration a
by
hg42
-
Firmware - experimental, borrowed, and future
Quotepamalofeev
You can read about my printer here
congratulations! really nice printer and very smooth.
It's an ideal companion for klipper...the same kind of enthusiasm...
by
hg42
-
Firmware - experimental, borrowed, and future