I found another problem with the code: when the print is launched, the PID values are never taken into account. I suppose that the heat pattern is not refreshed because the queue is always busy, but I am not sure if this is true because I do not understand how this all works. I am having a look at this, but any help would be welcome.
--
You received this message because you are subscribed to the Google Groups "R2C2 - Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to r2c2---suppor...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To unsubscribe from this group and stop receiving emails from it, send an email to r2c2---support+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "R2C2 - Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to r2c2---support+unsubscribe@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to r2c2---suppor...@googlegroups.com.
Hi Bryan,Well in my opinion a true problem in 3D printing today is that even though there are a lot of cool boards out there, most of them aren't really designed by professional hardware designers and lack the reliability/design efficiency they deserve as a component that drive such critical loads (I mean, a fucked up thermistor and you could get an awesome flame out of your printer)Even though new firmwares solve a lot of this, I still think that deserves to be treated better.When I had in mind to redesign a new r2c2 board, I had a few things in mind:- wifi connectivity on top of USB to allow easier use of the printer without tether.- touch screen (or just screen and controls) for standalone printing- detachable drivers to allow easier Change of fucked up ones (even though that is really rare on that board, I think newer drivers are really good, like tmcxxxx ones)- smaller size- additional sensor connections (filament run out..)If there is enough people interested in this thread, maybe we could build something good!NickNicolas ChaslotDrone Maker, Vamatis
Le 20 mai 2018 23:48, Bryan Lambrecht <bryan.l...@gmail.com> a écrit :
Hey Nicolas,I did a mini-remix version of the R2C2 quite a few years ago, bumped it to 4 layers and changed out a decent amount of parts. It works very well and gets less noise on the analog lines, better thermal handling (no heat sinks needed), and the BOM cost was reduced a bit as well.It would be pretty easy to keep the same base and add a bit of functionality or even shrink it down much further or take advantage of new MFG methods.I'm not huge into the firmware side of things, but pretty darn good with Altium since I use it everyday for work.What did you have in mind as far as new hardware design goals?I remember some one was trying to add some PID settings for the heaters but came to the conclusion that it needs more precision out of the ADC to accurately implement the PID controls and get the best performance out of it. I think the hardware is there to do it, just need to re-code a large part of it or something like that, and coding is more of a hassle than fun for me :(-Bryan
--On Sun, May 20, 2018 at 9:39 AM, ncx94 via R2C2 - Support <r2c2---support@googlegroups.com> wrote:Thank you very much for all the work you put into this!Unfortunately I'm not really into the code part so I can't help you a lot... I'd love to build a new hardware based on r2c2 though to bring 3D printing forward!Nicolas ChaslotDrone Maker, VamatisLe 20 mai 2018 18:28, lionel...@gmail.com a écrit :--I found another problem with the code: when the print is launched, the PID values are never taken into account. I suppose that the heat pattern is not refreshed because the queue is always busy, but I am not sure if this is true because I do not understand how this all works. I am having a look at this, but any help would be welcome.--
You received this message because you are subscribed to the Google Groups "R2C2 - Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to r2c2---support+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups "R2C2 - Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to r2c2---support+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups "R2C2 - Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to r2c2---support+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Sounds like we have the same ideas.
-regarding the driver's interface, newer drivers use SPI as
communication so that could free up some pins.
-for the standard connectors with non standard cabling, i'm not
really into that because it can cause to much trouble if beginners
try to plug things where they shouldn't.
- bltouch would be awesome for bed levelling
- i like the idea of having the drivers for the heaters out of the
board. Most people including myself tend to use SSRs anyway as a
board relief
To unsubscribe from this group and stop receiving emails from it, send an email to r2c2---suppor...@googlegroups.com.
By the way, there is another interesting feature that I have been thinking about detecting extruder jams. I do not know if anything has been done yet about this, but there is a relatively easy thing we could do for that: the filament extruder usually has a ball bearing to push the filament against the teethed rod, this ball bearing stops when the filament is jammed. A rotary encoder could do just that: when the machine detects a stop of the encoder, it can initiate a purge procedure and restart where it stopped.
--
--
You received this message because you are subscribed to the Google Groups "R2C2 - Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to r2c2---suppor...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/r2c2---support/9408e538-93ea-5eda-86b0-db21235ce7ed%40laposte.net.
To view this discussion on the web visit https://groups.google.com/d/msgid/r2c2---support/CACL3eKAEcYP3p_r9NxwvFfzXj_RSYCVQYSzcS6FaZ71nEjp_%2Bg%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/r2c2---support/2b2b2843-49d4-45a8-9798-1d9578822696%40laposte.net.
Hi Rui how are you?
It's been a long time!
To view this discussion on the web visit https://groups.google.com/d/msgid/r2c2---support/CAP0gxK_PBL_R3iFByfP3FA62mTy7Tz270WRL9gvbyz3TdPvVzA%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/r2c2---support/0eb23b81-85f9-4043-81ad-422fcdebf2de%40laposte.net.
You received this message because you are subscribed to a topic in the Google Groups "R2C2 - Support" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/r2c2---support/lq2pMaPl2IY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to r2c2---suppor...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/r2c2---support/CAP0gxK-GmdVqCvz3qEtnKr6-LUr7sQs%3DsXvZByU8OrXQnqZ2FQ%40mail.gmail.com.