-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test with Prusa Mini #157
Comments
Hi @probonopd, my Prusa Mini is arrived a few days ago. So i will try and report tomorrow. |
Hi, Prusa Mini Firmware: 4.1.0 The d1 can not connect to the printer. here is the telnet output:
i have no clue why it says "discovering". |
Thanks for testing @cpeuschel. Would have been too easy if it "just worked"... Do you have the hardware to check whether you can talk to the printer on ESP-RX and ESP-TX? What happens if you send M115? |
Any Prusa mini owners still around? Please do check whether you can talk to the printer on ESP-RX and ESP-TX using a serial-to-USB converter. Hi @cpeuschel try switching TX and RX if you have not tried that yet. The printer's TX needs to be connected to the ESP RX and vice versa. |
if you would connect Octoprint you must connect the pi via micro USB cable into the printer. So if we connect the wemos d1 with an micro USB cable directly on the printer maybe it work? Provided there is a way to send the commands (M115, etc.) via USB? @probonopd is that possible? |
Not with just the ESP8266 or ESP32. For this we would need a device with USB host capabilities. |
Hi, I have flashed ESP-01 to your firmware, it worked on the programmer but It didn't work in the Prusa buddy (clone). I have seen in router logs that esp acquired IP, but it didn't communicate from browser. It looks like the actual Prusa firmware set reset pin to turn off ESP. |
Interesting. Thanks for testing. Can you connect to the ESP via |
Hi there, I flashed I only have a multimeter so I can't do too much diagnostics, but post-boot it appears that IO0, IO2, and EN are high and RST is low. |
I built a serial mitm device out of two usb dongles and after grounding RST momentarily it seems to just work, even after switching it off and unplugging it, weirdly enough. Not sure if I broke it or what. Maybe it had it seated poorly? In order to install it I have to take out the power switch and it's a pain in the butt, so I don't want to do that until I know it's working. I wasn't able to send a large gcode file through (30MB), though I was (seemingly) able to upload a small (830K) sample file with curl that came with the printer. I wasn't able to print or download the uploaded file. I uploaded a text file with a few characters in it and still didn't seem to be able to download it. I think this thing only has 1M of flash, so that could be part of the issue, I'm not sure. I am able to download a 0 byte "Unknown" file on boot, however. If I fiddle with socat more I may be able to get hex dumps of the communication if you have things you want to try. |
Great @vilhelmen, thanks for testing. When it is "half-working", can you connect to the ESP with telnet, to see any debug messages? It is expected that this currently works only for gcode files that are small enough to fit into the internal memory of the ESP chip. For larger files, you could use a different ESP module with a SD card slot and a microSD card attached to the ESP. I guess this is not what Prusa has in mind with the Prusa mini connector for the ESP01. I guess they will make a firmware that will allow the ESP01 to upload files to the microSD card attached to the printer. But that needs to be implemented in the Prusa firmware. Until they do that, have fun tinkering with WirelessPrinting! |
I completely forgot about the telnet port. Now that I'm working on it today, the serial line is completely silent. Telnet connects on boot, but remains quiet and a reconnect fails. RST to GND is reporting -40mV, which seems suspicious. Connecting/disconnecting RST causes a bunch of data to be output on both lines, but that could be noise, and seems to eventually trigger a reset. The mini starts emitting the The mini, as far as I can tell, doesn't have a microSD slot. There's a mystery barrel plug(?), some sort of small usb, I never remember which is which, a USB A port, and ethernet. There's a nonzero chance I broke something, and my setup is a mess of wires, so something could have come loose. I'll rewire and see what I can come up with, but no promises. |
Ah, right. I wonder where Prusa wants to buffer large files then? USB? How does it work for wired Ethernet? |
That's a good question! Did some light googling and it seems to suggest that you just don't, it's monitor only. https://help.prusa3d.com/en/article/prusa-connect-local-mini_133279 |
What? You can't send a Gcode file to a Prusa Mini over Ethernet? That'd I'd call a fail then... wasn't this feature meant for print farms? |
Yeah, this is getting more disappointing the more I look into it :/ |
Well, I rewired everything and I'm powering the ESP externally. If I only connect the serial lines, the ESP doesn't get past the "Connecting at X" loop. There's a response from the printer after the 115200 pings, but it's inconsistent. Nothing like the consistent Maybe I still have a faulty connection, or maybe I shorted something in my < 1 week old mini, hard to tell. |
Have you resolved your problem? The TX and RX lines are some "resistant" because they only pull down. If you connet by mystake to GND there are no damage because the HIGH state is achieved with a pull up resistor. And if you connet to Vcc the circuit is more tolerant as I know. |
Ive been investigating this topic last few days, and also came to a conclusion that rx and tx on esp cannot be used since there is nk firmware support for it. Since comm via usb seems to work fine it also crossed my mind that i should look into a board wgich has a wifi module and usb. But looking at wemos specs it seems to me that usb is used for programming and power. Also the whole board seems to be powered by 5V. Prusa mini only has 3.3V ehich are added for esp support. |
A 3D printer with no support for RX and TX? |
I am new to this whole scene, but thats what it looks like to me. They seem to be trying to add it: prusa3d/Prusa-Firmware-Buddy#1246 And one other comment also caught my eye: prusa3d/Prusa-Firmware-Buddy#1246 (comment) I aint no hardware/firmware guy, but if there is already working comm over usb, how difficult can it be to make it work over rx/tx :/? |
This is the changes I made to prusa mini source in order to get the uart6 working, it works as I'm using an rpi zero powered directly from esp port present on buddy. the main issue I found while trying esp3d is the lack of sd support in the firmware. |
@Turro75 if you can print on the Prusa Mini over serial with a Raspberry Pi, then you might be able to print using WirelessPrinting as well. No special support in the firmware is needed apart from the serial connection. |
Ouch...I haven't check where I am... |
@Turro75 can you upload your modified Firmware? |
this is a firmware based on Llama custom firmware with uart6 enabled. here my pull request that generated the bbf file: |
@cpeuschel that looks promising! |
With the ESP-01 module you can't upload large gcode files. For this reason I used a wemos d1 mini |
@Turro75 thanks for your firmware, I had to add line |
Boas eu na entendo nada disto mas o que reparei antes de instalar o esp01 é que tem 1 conector de antena logo o lado ! Pode estar relacionado? |
Did you use that uart6 enabled firmware or official firmware? |
The Prusa Mini has a slot for an ESP-01 module.
Can we get WirelessPrinting to run on it?
The header on the Buddy board:
Connected to the CPU like this:
Source: https://github.com/prusa3d/Buddy-board-MINI-PCB/blob/master/rev.1.0.0/BUDDY_v1.0.0.pdf CC BY-SA 4.0
Prusa Mini owners are asked to try and report, since I do not have the printer.
The text was updated successfully, but these errors were encountered: