many resends
I am seeing many resends from my Raspberry Pi server to the Ender 3 printer. I have printed the file directly from a SD with success but the same file gets many resends when it is sent from the Raspberry Pi server to the printer. It is also prepending an automatic leveling and a preliminary priming path before the code that is appearing in the .gcode. I had tried to add these to the CuraEngin pre code in the gcode section but have since deleted it. I have reinitialized the initical gcode with the option in the CuraEngine with no joy. Does the Repetier Server keep a prefile that may be added? Could it be a handshaking problem between the Ender 3 usb-serial port and the Repetier Server?
Comments
Regarding g-code we only send the g-code you saved in server plus start/end g-code defined in server. So if it gets send it is included in one of these.
Regarding port use one of the /dev/serial/by-id or by-path ports you see. Must be one of these. ttyS0 is devitively wrong.
/dev/serial/by-id/...
or
pi@RepetierServer:/dev $ cd /serial
If you run
lsusb
you should see a list of connecte dusb devices including your printer if it is enabled and connected.
There are 2 possible errors here - no usb connection then you won't see it with lsusb as well. As a test remove usb able and run again. If one entry disappears tha was your printer.
If you can see the usb device and you have no /dev/serial I assume linux does not have a driver for that device or did not detect it.
Run
lsmod
to see active modules. In my list I see
cdc_acm 28672 2
which I'm pretty sure is my serial driver. You won't see a driver in your case I think, but consider they might have other names.
Othe rpi has these usb devices
If you see you have a CH3xxx driver and no module try
insmod ch341
I ran the lsusb and got the following:
The first run was with the ender 3 printer not connected. The second run was with it connected. The third run was with the touchscreen disconnected. The fourth run was with it reconnected.
The windows version of the server uses the usb and works well.
The raspberry pi server is installed from the latest download of the version 1.4.6. It has gone through initialization and the printer has been installed with the connectWizard but it never returns from the protocol test.
Try connecting something else to that usb port just to test that the pi usb port works. When printer creates com port on windows it should be ok. If othe devices (webcam/mouse/keyboard) do not appear as well I'd assume a defect on usb port. Then try other port e.g. the one where you connected the touchscreen which is a working device on working usb already tested.
And when other devices work there should be no reason and you need to dig deeper why linux does not show usb.
Try
tail -f /var/log/syslog
unplug usb and plug it back. There should appear new infos while you do. Press Ctrl+C when finished. There linux will most likely show why it did not list it as usb.
so pattern is ttyUSBxxx or ttyACMxxx
for usb connections.
"ls -l /dev/serial"
both give "ls: cannot accell '/dev/serial': No such file or directory"
tail -f /var/log/syslog
test I supposed above to see why linux does not add it.