Elegoo Mars 2 Mono having issues printing via web and updating Mariner3d
See original GitHub issueI was wondering if the green topped Mars 2 Mono was supported. I have installed it, get ‘printer ready’ responses from it but am getting the following error when I try to print a file:
Traceback (most recent call last): File “/opt/venvs/mariner3d/lib/python3.7/site-packages/flask/app.py”, line 1950, in full_dispatch_request rv = self.dispatch_request() File “/opt/venvs/mariner3d/lib/python3.7/site-packages/flask/app.py”, line 1936, in dispatch_request return self.view_functionsrule.endpoint File “/opt/venvs/mariner3d/lib/python3.7/site-packages/mariner/server/api.py”, line 208, in printer_command elegoo_mars.start_printing(filename) File “/opt/venvs/mariner3d/lib/python3.7/site-packages/mariner/mars.py”, line 132, in start_printing self.select_file(filename) File “/opt/venvs/mariner3d/lib/python3.7/site-packages/mariner/mars.py”, line 111, in select_file raise UnexpectedPrinterResponse(response) mariner.exceptions.UnexpectedPrinterResponse: //Disk init fail!
I have updated and upgraded my Raspberian Buster and got the following error when it got to updating Mariner3d:
Processing triggers for mariner3d (0.1.1-1) …
- echo postinst called with unknown argument
triggered' postinst called with unknown argument
triggered’ - exit 1 dpkg: error processing package mariner3d (–configure): installed mariner3d package post-installation script subprocess returned error exit status 1 Processing triggers for install-info (6.5.0.dfsg.1-4+b1) … Processing triggers for initramfs-tools (0.133+deb10u1) … Processing triggers for ca-certificates (20200601~deb10u2) … Updating certificates in /etc/ssl/certs… 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d… done. Processing triggers for libvlc-bin:armhf (3.0.12-0+deb10u1+rpt1) … Errors were encountered while processing: mariner3d E: Sub-process /usr/bin/dpkg returned an error code (1)
So, I cannot print and the standard updating path is also not working. I am using 5v @ 3.4a for my Pi Zero W so it should not be a power issue. Any ideas?
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (2 by maintainers)
Top GitHub Comments
I’m going to close this issue since it doesn’t seem like a bug, but rather misconfiguration on your end.
Can confirm, all is well now. 😃