I ordred 1 meter long shielded reprap discount just in case I want to replace the endstop cables.
Lets hope TL worked something out about the next batch. If not, there will be more of us with this problem.
Ezra was saying it occured on others printers as well. Could it be the taurrino playing gt ames with us, wbich would explain John's comment about not having the problem on his ordbot....
--
You received this message because you are subscribed to a topic in the Google Groups "trinitylabs-talk" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/trinitylabs-talk/8e75_kQxLXo/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to trinitylabs-ta...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
This machine is running 12x4.04Ghz cores, 16GB of Ram, and 6x128GB SSD on a LSI SSD controller. Clearly speed is not an issue with this machine, nor do I get interrupts with my MM1.5, its something to do with the electronics on A1. I’ve just been printing via SD card w/o issues, but clearly its not the cable, pc, etc. I can literally move the USB cable to the MM1.5 and print via USB all day long.
If I had to guess, its some issue with taurrino, even though it’s the exact same windows driver as the Ardunio 2560 mega.
Best regards,
Colt Majkrzak F5CI, F5SE
--
You received this message because you are subscribed to the Google Groups "trinitylabs-talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
trinitylabs-ta...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to trinitylabs-talk+unsubscribe@googlegroups.com.
I've discovered a very nice tip that I should have thought of long ago to help eliminate the stuttering and pauses that you get when printing via USB from Pronterface directly. If you do two small things you will get very improved performance without any pauses or stuttering and it will behave basically like it does when printing from sd card.1. uncheck the "Monitor Printer" checkbox2. Click the "Mini Mode" button after you have gotten your print started.
Ken -The limiting factor is generally not your CPU, but the tight communications line between them - the USB/Serial line. At 'only' 115200 baud, you get only 11KB/sec through the line. Given that each character of a .gco is a byte, and each line roughly 16 Bytes (approx) that's about 700 lines per second, best case. Seems like a lot, but if you're moving at 100mm/sec, doing a curve, you get 'only' 7 line segments per mm, with no extruder commands or other overhead involved (and there's always extruder commands and such).And that's assuming that the things are perfectly synced. Worse, your printer has an onboard (tiny) buffer, of roughly 16B (if I recall correctly) - which means that the PC can't send another line until the first one has been taken out of the buffer. If the PC gets bored of waiting (after all, it's not hard to send data), it can quickly task-switch to something else, which generally takes at least 5ms to get back (on Windows), meaning you've just fell behind by 3 line segments, and have to catch up. It's not bad if you're doing long straight lines - but for heavy tight curves, you simply never catch up, and your print head just sits there for a minute, oozing, and potentially making a blob in your tight corner, ruining your screw fit (a personal problem I've had on USB/Serial). At that point, ball screws and belts be danged, you're simply not putting the head in the right place, and your tolerances are wasted.So yeah - it's not the CPU at all, but the communication line. Going to a 'true' USB can/would help, as would going ethernet, as would a buffer. All of the above can't be done on an Arduino Mega, however. (Ok, the buffer could, but it would be a pain, and might overtax the Arduino anyway)
Triffid -First off, yay! Technical discussion!Having said that, the TCP windowing solution seems like a good idea, and may help immensely. If you're particularly worried about the pause issue, there might be a way to enable another endpoint on the USB for sideband communication, for things such as estops, temp changes, and pauses. Alternately, simply changing the current gcode protocol is another possibility, but one less friendly to the various open source solutions out there currently.
To be honest, I was expecting that the Ethernet port on Smoothie would address most of these issues, as you'll (by necessity) need and have bigger buffers and a higher overall communication rate, plus the advantage of automatic TCP/IP packetizing and windowing.Finally, for my own knowledge - you mention a 16-24 gcode line buffer in 'the' firmware. Are you referring to Smoothie, or Marlin/RAMPS?
How many of the A1s are being run over USB? How many have had to resort to an SD card because the USB connection was not reliable?
--
You received this message because you are subscribed to the Google Groups "trinitylabs-talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to trinitylabs-ta...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.