-
Notifications
You must be signed in to change notification settings - Fork 992
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
Issue reports for a non-connected printer so no command M115 output? #1531
Comments
I suggest you hook up an ftdi to the uart and see if you get any error messages. I also suggest you disable as much of the config you do not need (like network and panel etc) as you may well be running out of memory, start with as little as you can enabled, then enable stuff as you need it. However we do not support MKS SBASE products for reasons amply discussed elsewhere, so I would suggest contacting them for further support. We do not have any of those boards to test with. Best of luck. |
I wouldn't know but even the config comment itself mentions the purpose of the rate setting is for connecting to pronterface/terminal which is what I'm trying to acomplish.
Also this line is one of the only two lines mentioning "usb", the other one pertaining to storage devices. |
you connect to pronterface over usb, not serial uart, so that baud rate setting is irrelevant and should be commented out. you can connect pronterface to usb at whatever baudrate you want. you are also using a very old config where the comments are out of date |
Thank you for bearing with me @wolfmanjm So I get that in case of such an error kliment/Printrun#1393 (comment) I might flash a new firmware one day but I'm not eager to do it with that unsupported trash (both the board and the whole printer). EDIT: |
Update: What I did: Run as Administrator My very first G-Command issued:
M115 still gives no return. |
you have such an old firmware that it does not support M115. so do not worry about that. |
Is it even worth upgrading? Does the new post-2017 firmware affect actual printing process? Someone told me smoothieware has undergone a significant upgrade sometime in 2019, with some config.text reorganisation. I'd gladly research it myself but the releases section is empty |
Yes there were significant upgrades, much smoother acceleration amongst other changes. |
Again, thanks for all your help and for bearing with me despite my board being MKS SBASE. |
How would I go about reporting issues with Smoothieware config.txt when I haven't even succeeded in connecting my no-name printer to a terminal?
Smoothieware seems to regard my config.txt as corrupted (so the printer won't respond) if I dare to alter a single character in the serial communications section. I can't even alter baud rate for USB from the already set 250000. Changes in other parts of the config.txt do not cause such issues and do have an effect. I obey the encoding (ANSI) and end of line standard (Unix(LF)).
config - works.txt
config - doesnt work.txt
Please don't trash the issue report. I'm willing to provide any details necessary.
Printer in question is an end-of-life startup project based on MKS SBASE 1.3 https://lumeplus.wixsite.com/lume
The firmware I have is from 2016/2017 and has been provided by the manufacturer of the printer.
The text was updated successfully, but these errors were encountered: