-
-
Notifications
You must be signed in to change notification settings - Fork 19.5k
Fix (crashing) error on M105 output #6584
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
Conversation
LGTM. Will verify shortly if you need an extra +, need to get my cube printing shoes on. |
…ERIAL_PROTOCOL_F also removed wayward 'address of' ampersand in setTargetHotend and setTargetBed parameters
I think I agree the 'address of' does not serve a purpose in these function declarations. Why was that put there? If I knew the answer, I would merge this right now.... |
I have no idea why it's there, but there's no purpose for it that I can see. We're just referencing the value of the int passed in when setting the temps. My guess is that there was some need for it in a previous version. |
OK... We can change it back if it turns out there is a real reason for it. I think it can also be argued that the non-BugFix branch should get this change, but we should probably have a discussion about that... I'll merge just to help get rid of some of the crashes... |
Yeah, it's a pretty big deal. I can't imagine anyone who checks temps w/M105 can use 1.1.0? |
Actually... part of the discussion ought to be what the default branch is... If we are NOT going to cross bug fixes over to the v1.1.0 branch... Probably the default branch should not point at it. The default branch should point at something that works for most people. |
I can't check this right now.
Does this mean that host programs won't show won't show 1dp of precision in
temperature read backs?
|
I believe the answer is "Yes." It maybe that switching to double is better than int. |
My build from
And M105 works fine:
|
Do you know which commit that is, Tannoo? Looks like it's from before 2658cc7, which would make sense. EDIT: I don't think the ampersand was causing a problem, necessarily, but it was unnecessary and didn't make sense, given what the function does now. |
seems to work with OctoPi so far
Not a huge fan of that missing point of precision tho.... Now to try and print something! |
…ERIAL_PROTOCOL_F (#6584) also removed wayward 'address of' ampersand in setTargetHotend and setTargetBed parameters
…ERIAL_PROTOCOL_F (#6584) also removed wayward 'address of' ampersand in setTargetHotend and setTargetBed parameters
…ERIAL_PROTOCOL_F (#6584) also removed wayward 'address of' ampersand in setTargetHotend and setTargetBed parameters
…ERIAL_PROTOCOL_F (#6584) also removed wayward 'address of' ampersand in setTargetHotend and setTargetBed parameters
…ERIAL_PROTOCOL_F (MarlinFirmware#6584) also removed wayward 'address of' ampersand in setTargetHotend and setTargetBed parameters
…ERIAL_PROTOCOL_F (MarlinFirmware#6584) also removed wayward 'address of' ampersand in setTargetHotend and setTargetBed parameters
Use SERIAL_PROTOCOL for ints instead of SERIAL_PROTOCOL_F.
Also removed wayward 'address of' ampersand in setTargetHotend and setTargetBed parameters.
See #6571.