No Control of Mars Pro Printer at Firmware 4.4.3

I’m a new user (ie Mariner3D has never worked completely for me) I get the #180 symptom, however I do not get any control of the printer which seems different from the experiences of others who get this symptom.

Looking at the serial data being sent from the Pi Zero W to the Mars Pro, I see the following M23 /first file.ctbM4006M4006M4006M4006M23 /second file.ctbM4006M4006M4006M4006M4006M4006M4006M4006 that is, a constant stream of commands without CR LF.

In order to rule out my serial monitor, I performed the following on the Pi Zero W cat 1.txt > /dev/ttyS0 where 1.txt contains three words separated by CR LF.

I see the following in the serial monitor

My conclusion from this is that Mariner3D / Python is not sending the CR LF even though I can see from the Mariner code that it should be sent.

Assuming my observations are reliable, then I think that the commands from Mariner cannot be digested by the printer. I cannot escape the fact that nobody else sees this problem so it is likely to be a problem of my own making rather than Mariner.

A short description of what the bug is that the printer cannot be controlled via the UART.

Expected Behavior I expect that the printer will be sent commands terminated with an “\r\n”. I can see in printer.py that this is the intent of what Mariner3D is doing. I don’t see why this seems not to be happening.

There is nothing of interest in the Mariner3D log.

Details:

• Mariner Version: 0.2.0-1
• Printer Model: Elegoo Mars Pro V4.4.3_c1_LCDF System EL3D-3.0.1
• Raspberry Pi Model: RPi Zero W with raspios_lite_armhf-2021-05-28/2021-05-07-raspios-buster-armhf-lite

Other cmdline.txt is root=PARTUUID=82934f69-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait modules-load=dwc2 [all] clause of config.txt contains

dtoverlay=dwc2
enable_uart=1

Python is 3.7.

[J-Iszatt]

Hello @BlueFinBima and @luizribeiro,

As I was also facing troubles with the specific firmware mentioned above (running on a mars pro 2), I finally managed to find this great explanation (and the even better solution) here! I am extra thankful for the original mariner software as well as the additions to the printer.py file and was wondering if a link or at least a hint to problems with 4.4.3 could be added to the readme of this project? Given that more and more users are upgrading, I am relatively sure, that this would save people a lot of time 😛

On top I want to ask for a couple of lines on how to get the code running by ‘git-cloning’ it (at least for Bima’s repo, there are no .deb files available).

Thanks again for all the great work! Please keep it up. Cheers JI

[BlueFinBima]

@Blanks82 the deb got deleted from the packaging action, and I was unable to get a successful package to recreate it. I have now finally managed to get this to work (I think) and the deb is now available here https://github.com/BlueFinBima/mariner/releases/tag/v0.2.0-1