You are not logged in.
Pages: 1
Hi Shahin:
Any ideas on how to troubleshoot intermittent "connectivity problems"? I am using nanoDLP with an Arduino Mega2560/RAMPS1.4 and it is working well, but every once and a while during a print I will get a "Could not connect to the printer. Please, check your connection" warning, and the detailed log shows this (for layer 313):
Error 313 2016-09-21 09:33:37.02198 SLAVE Serial Communication Error EOF
Once the error starts, it happens on all subsequent layers. Usually the printer pauses but then keeps going, but sometimes it stops completely and crashes nanoDLP. Is my Arduino going bad? I have tried various versions of nanoDLP (beta) and seem to get errors on all versions. Thanks!
(I can email you debug info for a successful print where these errors appear if you would like).
-robertk925
Offline
It is two separate issues.
"Could not connect to the printer. Please, check your connection" it is the case of timeout for your local connection. It is harmless but if you want to solve it, you need to find out your network why packages from nanodlp takes more than a second to reach your browser.
"Error 313 2016-09-21 09:33:37.02198 SLAVE Serial Communication Error EOF" this one is much more serious, which could cause print issues and should never happens send debug info, my guess is wiring problem between ramps and nanodlp is more likely to cause it but any software or hardware issue on ramp board also could cause such behaviour.
Offline
Thanks for clearing that up Shahin.
Debug info below:
nanodlp.debug.905301036.zip
Offline
Change cable to see if it fix the issue. nanodlp could not write to the serial connection.
Offline
Thanks, will do.
Offline
Shahin, I tried 2 other USB cables and am still getting the following error (on Build 1242), but now I am getting the error on every layer (below example shows layer 45):
Error 45 2016-09-23 08:49:24.246403 SLAVE Serial Communication Error EOF
Error 45 2016-09-23 08:49:24.146221 SLAVE Serial Communication Error EOF
Error 45 2016-09-23 08:49:24.046012 SLAVE Serial Communication Error EOF
Warning 45 2016-09-23 08:49:23.945808 Terminal Problem Reading Terminal EOF
The printer is printing fine even though the log is showing this error. Is this something I should be concerned about? Maybe my Arduino has some sort of USB problem? Thanks!
Offline
I think at one time Arduino takes a lot of AMP.
Do you directly Servo motor?
Board the Mega restart due to a flow dip
Offline
Hi omid2572:
Thanks for the reply. I am not sure if I understand completely, are you saying that the servo may be drawing too much power? I am using a servo that is directly connected to the RAMPS1.4 board, so I will try printing with the servo unplugged.
Offline
If you're using a servo motor for shuttle
Disconnect the servo motor connection
And try again
Offline
Ok, I have tried disconnecting (unplugging) the servo completely and still get "Serial Communication Error EOF" errors. I then tried a completely new Arduino and RAMPS1.4 PCB combo (purchased brand new), reprogrammed with the latest muve3D Marlin firmware, and still with no servo plugged in, and am still getting "Serial Communication Error EOF" errors. Any other suggestions? Thanks!
Offline
Have you tried different cable?
Offline
Yes, I tried 3 different cables.
Offline
Ok, I think I solved the problem for now. It wasn't the RAMPS/Arduino boards or the USB cable. Here is what I tried and my final working solution in the hopes that it might be of help to someone else. Note that in between each step I restarted the RPI3 each time.
1. My servo for the shutter (an SG90 servo) seems to be right on the edge of drawing too much current, which is perhaps why it worked in the beginning (for about a month) but thereafter started to cause problems with resetting the Arduino. Perhaps the gears are starting to get sticky, which can cause the servo to draw more power?
2. I unplugged the servo, but I was still getting the connection errors.
3. I tried changing the baud rate to the Arduino to 250000. While this didn't work, resetting it back to 115200 did (i.e. it cleared the connection errors in the log).
4. I replugged in the servo, and tried adding a 470uF capacitor on the +5V and GND connections. The connection errors came back.
5. I unplugged the servo (again), and again I was still getting the connection errors.
6. I changed the baud rate to the Arduino to 250000 and then back to 115200. Again, this cleared the connection errors in the log.
7. I wired an external 5V power supply to the servo, and now everything works.
Offline
I forgot 1 other step that I tried (that didn't work), as well as a clarification on step 7.
7. (This 5V power supply is only connected to the servo, not the Arduino.)
8. I tried using an external 9V/1A power supply to power the Arduino in place of the USB, but still received connection errors.
Offline
I had similar issue with small servo motors in past. They simply are not designed to last. I had experienced if after a year of use.
Nowadays instead of opening and closing shutter after each layer I close them once per print which extend their life.
I believe your servo is malfunctioned and you need to replace the unit as it could damage your power supply.
Offline
Thanks for the reply Shahin, I will try another servo and report back.
I guess I don't understand the purpose of a shutter that only closes at the end of a print. Isn't the purpose of the shutter to block ambient light coming from the projector (which is always illuminating the entire build area, even though some of the areas are black) in order to prevent fast-acting resins from hardening/degrading? Are you saying that you don't see any difference in print results with/without a shutter?
Offline
I had same kind of concerns regarding unwanted resin cure. I have not seen any difference since change. Maybe resin got a bit more thick.
I had once stalled printer with shutter open (2 3 years ago). After couple of hours it cured a thin layer which ruined my PDMS.
So it could cure but require very long time. Right now shutter is only helpful when projector displaying intro logo.
Offline
Ok, that is good to know. What resin are you typically using?
Offline
If I remember correctly, it was envision pic100 when I had this accident. Right now couple of different one, I prefer 3dm cast.
Offline
I am getting the same serial errors as in my message #6 on this thread, running builds 1261 and now 1279. I have disconnected the servo completely, yet still get this error. My printer seems to print ok, but it is hard to see many of the status messages in the log since it is filled up with serial error messages after each layer (and at startup). I tried 3 different USB cables with no effect. Any suggestions on how to troubleshoot? Thanks.
Offline
I think I have figured out the cause, although not a solution. My Acer 6510BD projector seems to be the culprit. When I unplug the serial cable to the projector these errors go away. When I hard reboot the projector the errors also go away for a while, but eventually return. I have tried every combination of baud rate, parity, stop bits, etc. and nothing seems to fix the error message, although the serial controls still seem to work.
Offline
Interesting, what are their address?
Offline
Sorry Shahin, I am not sure what you are asking for. The USB serial port address that I have connected to the projector? If so, I am using /dev/ttyUSB0
Offline
What about ramp address? ACM0?
Offline
Correct, /dev/ttyACM0
Offline
Pages: 1