Comments (21)
it is an anycubic mega S
A quick web search seems to suggest that the firmware for that printer model does not play nice with hosts like OctoPrint and (presumably) Pronterface (ref: OctoPrint/OctoPrint#2309 (comment))
You could enable debugging (Settings > Debug communications) and share your logs to confirm the issue. I would suggest you try connecting using baud rates 115200 and 250000.
What should I see when Pronterface connects?
It will say "Connected." and then the jogging controls will no longer be grayed out and should allow you to move the extruder around.
I assume you are able to print from SD card using the touch screen, right? I mean, the printer is in working condition.
from printrun.
Pronterface should say in the Terminal window:
Connecting...
Printer is now online.
Using tool 0.
You can also activate -->Settings -->Debug Communications. This shows your printer temperatures for bed and extruder continuously.
SENT: M105
RECV: ok T:18.0 /0.0 @0 T1:18.0 /0.0 @0 B:17.6 /0.0 @0 B1:17.1 /0.0 @0
SENT: M105
RECV: ok T:17.9 /0.0 @0 T1:18.0 /0.0 @0 B:17.4 /0.0 @0 B1:16.8 /0.0 @0
SENT: M105
Can you please attach the Pronterface logfile (Printrun.log) and configuration file (printrunconf.ini)? You need to zip them.
(Location for the log file: -->Settings -->Options -->User Interface -->Log path)
from printrun.
Oh, you was faster @rockstorm101 :)
from printrun.
If there is a firmware that is known to work well on this machine, I'll try it.
I can only recommend Marlin which is the one I use on my printer with zero issues. However configuring it requires some deep understanding of your printer internals. Which is why you might want to have a look at this project which provides precompiled binaries for your printer brand. They've got a pretty thorough wiki to help select the right binary. Let us know if you get good results with it.
from printrun.
I don't own an Anycubic mega S, so here is little to help you on this specific hardware/firmware problem. Maybe there is one who can help on this as they sold a lot of this printers around the world.
I think we should leave this thread open so that you have time to fix the hardware / firmware issues first. I mark this thread as "Not a bug" for now.
Maybe some additional hints in general:
-
You may need a device driver software for your operating system. This usually came with the printer (manufacturer SD card?)
-
You need to check whether your system acknowledge the printer as device or not. For macOS you can use a terminal window to check this:
-
Disconnect the printer from your computer and then open the terminal window and type
ls /dev/{tty,cu}.*
followed by [enter]. -
Make a screenshot of the report.
-
Then connect the printer via USB, wit a little and type
ls /dev/{tty,cu}.*
followed by [enter] once more. -
Compare the two reports. You will find a new device connected to a serial port if the device was recognize by your computer.
-
In case there is no connection you need to find out if the problem is related to the USB cable or your printer. I often recognize that people try to use extended USB cable with more than 3 or 5 meters and then had those issues because there a using in addition the printer in an harsh environment with lot of electromagnetic interference. Check if a another (shorter) cable can solve the problem. Also check if another serial port of your computer works better.
For Pronterface, as already mentioned from @rockstorm101 your printer type is usually connected with a 115200 or 250000 baud communication. You can use a terminal tool like PuTTY as well to check the connection. Here you will find some informations about it: https://www.ssh.com/academy/ssh/putty/mac
In addition I attach an example of my connection setup (Windows version of PuTTY):
And here how this is set up for Pronterface:
For selection the serial Port in Pronterface connect the printer to your computer and start pronterface. Then click on button Port. Usually this is enough to select your correct serial com port as this will refresh the next button right with the acknowledged printer on your computer. Then you need to choose the correct printer if there is more then one recognized. The last point is to select the baud rate as mentioned already. Here it is how i looks for my printer:
Hope this will help little bit. Feel free to ask if you have further questions. You are welcome doing so. And keep us informed if you was able to solve your hardware / firmware issues.
from printrun.
Not cool, Cura…I know I get the annoying startup tune as soon as a serial connection is made, so this all makes sense, thank you. I'd love find the GCODE to turn that off.
The machine just completed a 14:28 hour job that almost maxed out the Z axis and it looks good. It seems to be working better than when I unboxed it. ¯_(ツ)_/¯
I may look into replacing that Rolls Royce turbojet fan before I worry about anything else, to be honest. I need to look more closely into what a firmware upgrade would do: mesh leveling would be useful, for example. I like how the Prusa does that and how it lays out a short run of filament near (0,0) as a priming exercise. I know that can be done in GCODE. Still no idea why it was "bricked" as a result of the firmware update but I inclined to think the OEM firmware or hardware doesn't handle serial comms properly.
from printrun.
Is there a baud rate or other setting I need to change?
[...]
Got rubbish reply from /dev/cu.usbserial-0001 at baudrate 57600: Maybe a bad baudrate?
[...]
Got rubbish reply from /dev/cu.usbserial-0001 at baudrate 9600: Maybe a bad baudrate?
What is your printer model? Did 57600 and 9600 baud rates work with PrusaSlicer? My default go-to baud rate would actually be 115200 or 250000
from printrun.
from printrun.
What should I see when Pronterface connects? A prompt? All I get is
Connecting…
I have been able to get some connection (the printer signals that it has a connection audibly) w this:
cu -I /dev/tty.usbserial-0001 -s 57600
but what should I see/what can I do to get something to happen?
from printrun.
Maybe one additional thing as I saw Cura mentioned:
Cure blocks the com port once it find a printer. When running Pronterface you need to close the Cura app because no other app is able to use the com port parallel to Cura. The only workaround is to disable the com port plugin in Cura, but then you can't do serial communications in Cura.
from printrun.
This is all great information…
The machine as it sits in inoperable. It can sometimes accept commands from the screen, like printhead movements, but not reliably. It accepted a G28 command through Cura but not the M502 and M500 that are needed to restore it to factory defaults (or if it did, there was no feedback). Heating does not work so printing is no op. It was able to load/unload filament yesterday so printhead heating worked for a bit but bed heating does not.
I did a firmware change and it was unresponsive after that, but I now have it restored to the OEM firmware and can make firmware changes at will. Previously it was unresponsive to any serial communications. Cura and Prusaslicer can both access the serial comms to make firmware changes and Cura will send some code instructions, but there is no feedback or confirmation in the "console" it provides.
I never used pronterface before this so I have never seen it actually work. I will see about getting some of the debug logging later today.
If there is a firmware that is known to work well on this machine, I'll try it. So far, nothing seems to work but it could be the machine itself. Not sure how something so simple internally could go so wrong but it seems like it is a box of compromises, not something designed to perform well over time.
from printrun.
I have been exploring the Knutwurst project and I just discovered the more complete list of hex files that I have been looking for. I'll try flashing one of them tonight. Maybe this machine can be salvaged after all. It sits next to a Prusa so the comparisons are not favorable.
from printrun.
Printrun doesn't have much to say. I flashed with one of the hexes I think is for this machine and didn't get much. I don't find a printrunconf.ini file anywhere.
2023-10-06 07:24:31,353 - Connecting...
2023-10-06 07:24:58,221 - SENT: M105
2023-10-06 07:25:02,030 - SENT: M105
2023-10-06 07:25:05,850 - SENT: M105
2023-10-06 07:25:09,670 - SENT: M105
2023-10-06 07:25:13,481 - SENT: M105
2023-10-06 07:25:17,288 - SENT: M105
2023-10-06 07:25:21,092 - SENT: M105
2023-10-06 07:25:24,897 - SENT: M105
2023-10-06 07:25:28,699 - SENT: M105
2023-10-06 07:25:32,505 - SENT: M105
2023-10-06 07:25:36,313 - SENT: M105
2023-10-06 07:25:40,131 - SENT: M105
2023-10-06 07:25:43,933 - SENT: M105
2023-10-06 07:25:47,737 - SENT: M105
2023-10-06 07:25:51,551 - SENT: M105
2023-10-06 07:25:55,360 - SENT: M105
2023-10-06 07:25:59,175 - SENT: M105
2023-10-06 07:26:02,980 - SENT: M105
2023-10-06 07:26:05,760 - Connecting...
2023-10-06 07:26:05,935 - SENT: M105
2023-10-06 07:26:07,211 - Reset.
2023-10-06 07:26:09,741 - SENT: M105
2023-10-06 07:26:13,553 - SENT: M105
2023-10-06 07:26:17,358 - SENT: M105
2023-10-06 07:26:21,162 - SENT: M105
2023-10-06 07:26:22,643 - Not connected to printer.
2023-10-06 07:26:22,643 - Disconnecting from printer...
2023-10-06 07:26:22,643 - Exiting program. Goodbye!
from printrun.
It says a lot: I'm not able to connect.
Pls make a screenshot of -->Settings -->Options -->Printer settings
Edit:
Config file:
It may be that it is the same as for Linux --> search for .pronsolerc instead printrunconf.ini
from printrun.
from printrun.
from printrun.
from printrun.
Well, sometimes being too dumb to know when you're licked pays off…I think this machine is working again, as well as it ever did. Cura can connect and send commands: G28 is my go to, as it will jog the printhead enough to let me know it got through. The heating is working, due to my guess about where those two wires went. Getting ready to run the test file to see how well it works. If this works, I'd be up to try a firmware upgrade but I have tried so many. I need to be sure it's the right one this time. Pronterface is connected.
![Screenshot 2023-10-07 at 6 52 51 PM](https://private-user-images.githubusercontent.com/4120380/273420730-6e1b23d3-f84b-497e-9b17-9f6d3862ee44.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MDQ3NjEwMTMsIm5iZiI6MTcwNDc2MDcxMywicGF0aCI6Ii80MTIwMzgwLzI3MzQyMDczMC02ZTFiMjNkMy1mODRiLTQ5N2UtOWIxNy05ZjZkMzg2MmVlNDQucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDEwOSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDAxMDlUMDAzODMzWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9YjYzOTdmY2Y0NDZkYThlNGQ1ZDFiOTc5OWY0ZGUwNDlkOGVkNTIyMGFmYzE2NmUxNzBhODljYjM3Njg3NWRlNSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.UOjeon25eK7SHutR4TUMIWs-jOMrac_CESVF7JUxx2U)
For some reason, the machine seems to just halt when cura is on the serial port. Heating doesn't increase, nothing runs.I unplugged the cable and the machine picked up again. Pronterface doesn't have that effect.
But it is having a lot of trouble printing, major adhesion issues that are outside the scope of what we're talking about. I scrubbed the build plate w soap and water and now I am seeing results. A firmware that supports mesh leveling would be favorite.
from printrun.
Hi,
good to hear your printer works again.
For some reason, the machine seems to just halt when cura is on the serial port. Heating doesn't increase, nothing runs.I unplugged the cable and the machine picked up again. Pronterface doesn't have that effect.
As I wrote before:
Maybe one additional thing as I saw Cura mentioned:
Cura blocks the com port once it find a printer. When running Pronterface you need to close the Cura app because no other app is able to use the com port parallel to Cura. The only workaround is to disable the com port plugin in Cura, but then you can't do serial communications in Cura.
You can't run Cura and Pronterface at the same time. This is exactly the message you will receive when two apps try to communicate to the same serial port.
Side note: Be also careful when you have establish more then one serial connection. When Cura starts it will scan all available serial ports and flood them with communication traffic witch cause other applications with communication errors and broken connections (e.g. running micro controller boards via USB connection at the same time).
Cleaning the build plate with hot water and dish soap is perfect. Rinse the bed with clear water and use a clean kitchen towel (don't wash these towels with softener). Avoid touching the print surface with your fingers and don't use isopropanol for cleaning as often mentioned a lot in forums. While it works fine for some bed materials like Garolyte / FR4 (as long as there is no grease e.g. from finger tips involved), but you will mostly spread the grease of an contaminated bed over the surface as a very thin layer. After the isopropanol is evaporated it will leave the grease back. Sooner or later you will loose the adhesion - mostly sooner...
Use a cheap glue stick like UHU, Pritt or what ever is available in your country. Write an "O" or a "X" on the print surface (only a little is needed) and wipe it evenly with a very wet paper towel over the complete build plate so that the glue is evenly averaged over the complete build plate as a very thin layer. This is enough for multiple prints. The glue acts as an adhesion promoter under heat and release the printed part after cooling from the bed. Heat up the bed afterwards so that the water can evaporate.
Mesh leveling can help a lot, especially if the bed isn't even or you are a beginner. Knowing how to level a bed manually is something you need to practice a bit, but it is easy to do and take for my printers only a minute. I use stripes of used print paper scrap for doing this. Heat up the bed to the needed print temperature (the heat should be stabilized) and the nozzle to around 160°C, clean the nozzle if needed and make the 5 point check. Usually after doing this the second time the bed is leveled. For me this is faster then doing a complete mesh bed leveling - but if I had to run a printer farm I would use mesh leveling too :)
from printrun.
from printrun.
What is happening is that Cura being connected stops the printer, as if it's waiting for instructions.
That's what happen when Cura try to connect to a printer. Roughly explained Cura try to establish a connection by initializing a serial connection and then try to find out what baud rate is used. Doing so it sent a gcode command to the printer with different baud rates and look for a specific answer. In case it do not become the expected answer it try again with an other baud rate for all known rates. I'm not quite sure how often it try to start the loop again but I guess they do repeat it a couple of time to be sure that there is no connection. (Think back to the time where we had use a acoustic coupler modem for communication between computers, It is more or less the same process and you could listen to this process back in these days). This behavior can force a printer to do "silly" things.
Side note: Keep in mind that UltiMaker do not support the direct serial communication via Cura since quite some time. This is why users switch to other solutions like Pronterface
Pronterface is different in this behave. It don't try to establish a connection itself. The user have to do that manually and have to tell Pronterface the correct com port and baud rate. If the setup is wrong you only see that there is no connection possible and then the program waits for the user for correcting the setup and for starting the next connection attempt.
from printrun.
Related Issues (20)
- Strange green lines on the PLATER window HOT 10
- Switching main visualisation window from 3D to 2D don't work for Gcode and STL Plater window
- Rework spoolmanager as a plugin
- Test suite failure on decode_utf8 function for AttributeError
- Octoprint's command bar always jumps down HOT 4
- Falha Nine Type HOT 4
- Can't open Pronterface on Ubuntu 22.04 HOT 2
- Can't open because Apple can't check malicious software and request an update HOT 4
- Regression for Python 3.9 due to type hints HOT 1
- Unstable behavior if there's no controlling terminal HOT 4
- 3D view broken in own-compiled package, Debian repo version is good -- part deux! HOT 20
- Text fields and buttons lack padding around their contents, and other minor UI issues HOT 1
- UI hangs after some time, print continues HOT 2
- ValueError: could not convert string to float: line 1995 pronterface.py HOT 46
- Pronterface - Errno 6 Device not configured HOT 5
- My Laser uses the RS 232C communication protocol and not G-Code HOT 10
- Thank you for making pronterface printrun and allowing me to connect the laptop to the 3D printer HOT 2
- Running Pronterface on Aarch64 and Trying Other Tools in the Suite HOT 6
- filament reload error HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from printrun.