Skip to content
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

Closed
otede opened this issue Dec 9, 2023 · 10 comments
Closed

Issue reports for a non-connected printer so no command M115 output? #1531

otede opened this issue Dec 9, 2023 · 10 comments

Comments

@otede
Copy link

otede commented Dec 9, 2023

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.

@wolfmanjm
Copy link
Contributor

uart0.baud_rate 250000 is for the uart not usb. the usb does not have, nor need, a baudrate set.

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.

@wolfmanjm wolfmanjm closed this as not planned Won't fix, can't repro, duplicate, stale Dec 9, 2023
@otede
Copy link
Author

otede commented Dec 9, 2023

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.

second_usb_serial_enable                     true            # This enables a second usb serial port (to have both pronterface
                                                              # and a terminal connected)

Also this line is one of the only two lines mentioning "usb", the other one pertaining to storage devices.

@otede
Copy link
Author

otede commented Dec 9, 2023

@wolfmanjm
Copy link
Contributor

wolfmanjm commented Dec 9, 2023

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

@otede
Copy link
Author

otede commented Dec 10, 2023

Thank you for bearing with me @wolfmanjm

So I get that in case of such an error kliment/Printrun#1393 (comment)
There's nothing Incan do in my end? It either connects or it doesn't? This was my last hope of connecting the printer since its Ethernet module is apparently dead.

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:
I'm sorry, but every single tutorial on connecting printers to terminals (be it Repetier or Printrun) does mention baud rate in the context of USB connection.

@otede
Copy link
Author

otede commented Dec 10, 2023

Update:
I was able to connect via COM3@9600 (250000 baud rate value in the smoothieware config is still untouchable). Not only that, it seems that the whole MONITOR tab in Cura has gone live with all the functionality!

What I did: Run as Administrator

My very first G-Command issued:

M503
SENDING:M503
; No config override
;Steps per unit:
M92 X200.00000 Y200.00000 Z3200.00000
;Acceleration mm/sec^2:
M204 S3500.00000 Z300.00000
;X- Junction Deviation, Z- Z junction deviation, S - Minimum Planner speed mm/sec:
M205 X0.05000 Z-1.00000 S0.00000
;Max cartesian feedrates in mm/sec:
M203 X166.66667 Y166.66667 Z8.33333
;Max actuator feedrates in mm/sec:
M203.1 X300.00000 Y300.00000 Z8.33333
;WCS settings
G54
;Digipot Motor currents:
M907 X0.25000 Y0.25000 Z0.25000 E0.30000
;Home offset (mm):
M206 X0.00 Y0.00 Z0.00
;E Steps per mm:
M92 E196.1200 P57988
;E Filament diameter:
M200 D0.0000 P57988
;E retract length, feedrate:
M207 S3.0000 F2700.0000 Z0.0000 Q6000.0000 P57988
;E retract recover length, feedrate:
M208 S0.0000 F480.0000 P57988
;E acceleration mm/sec²:
M204 E500.0000 P57988
;E max feed rate mm/sec:
M203 E50.0000 P57988
;PID settings:
M301 S0 P10.0000 I0.3000 D200.0000 X255.0000 Y255
;Max temperature setting:
M143 S0 P300.0000
;PID settings:
M301 S1 P10.0000 I0.3000 D200.0000 X255.0000 Y255
;Max temperature setting:
M143 S1 P300.0000

M115 still gives no return.

@wolfmanjm
Copy link
Contributor

you have such an old firmware that it does not support M115. so do not worry about that.

@otede
Copy link
Author

otede commented Dec 10, 2023

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
https://github.com/Smoothieware/Smoothieware

@wolfmanjm
Copy link
Contributor

Yes there were significant upgrades, much smoother acceleration amongst other changes.

@otede
Copy link
Author

otede commented Dec 10, 2023

Again, thanks for all your help and for bearing with me despite my board being MKS SBASE.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants