kbob wrote:I forgot to include this photo. It shows the X idler bracket's new location. I think it needs to move further to the right to be well clear of the laser.
Also, this photo shows a mirror-right-of-center (mroc) mirror mount. That should disambiguate that.
BenJackson wrote:I think the other thing you want to do there is flip the M5 bolt on the back wheel around so the excess bolt isn't sticking down (for maximum Y clearance).
The other suggestion I'd made to Bart back when I built mine is to drill a hole in the right front of the carriage to pass the air assist down to a right-angle fitting.
BTW in case you don't know, the top of the lens assembly unthreads from the bottom part so the whole thing can rotate in the diamond-shaped plate. You may need this adjustment to make sure the final mirror is square to the gantry.
My X idler is a little left of yours and I definitely had to chamfer it to keep it out of the beam path. But my beam geometry might not be the same as yours.
kbob wrote:I do not understand how Marlin et al do flow control on the serial (USB) line. I need to understand how to do flow control in my own serial driver. I don't see anything that looks like software flow control or hardware flow control in the Marlin sources. I don't have an Azteeg schematic to see whether there are hardware flow control lines.
BenJackson wrote:kbob wrote:I do not understand how Marlin et al do flow control on the serial (USB) line. I need to understand how to do flow control in my own serial driver. I don't see anything that looks like software flow control or hardware flow control in the Marlin sources. I don't have an Azteeg schematic to see whether there are hardware flow control lines.
They don't do HW or SW flow control. The AVR hardware has 1 byte of buffering and the firmware implements a deeper buffer in software with the UART interrupt. If this interrupt is held off (and unfortunately it's very low priority) you will lose bytes and the half-baked reprap "checksum" algorithm might detect the line is wrong and demand a retransmit. There were older firmwares (the original "5d") which did so much math in timer interrupts that the fw would lose bytes if you went much over 38400 baud. Newer firmwares are much smarter about this and basically never lose bytes.
bdring wrote:I need to see that lite up in the system.
Users browsing this forum: No registered users and 34 guests