M106 Fan Commands not in GCode anymore

[atair]

All my profiles stopped writing M106 Commands..
I have an MK3 and a Makerbot. S3D had all profiles running for MK3 and yesterday i momentarily added the Makerbot Rep2 from the Configuration Assistant to print something. After i was done i removed the profile. All that happened in the same Process (i only have 1).

Since then M106 Commands are not in the gcode, and god knows what else broke.
Adding a new Process does not help.
Saving Profiles as New does not help.
Please advise.

V 4.1.1

[atair]

ok running the wizard again with the mk3 repairs the profiles.
This Process / Profile / Printer system is so broken

[wirlybird]

I and others have had issues over time with this same thing and it seems to only affect the Prusa MK2 or 3. Or at least for me and don't know why.
The M106 fan control lines stop being added to the gcode.

It is a real pain when it stops working and you have several profiles saved and have to go back and recreate them all to get it working again.


Support has also been no help on this.

[S3D-Alex]

Could anybody please post a Profile (fff) or Factory File that exhibits this? We would be very interested in investigating this further as we have not personally experienced it or been able to recreate this issue here.

[atair]

I exported the broken fff to see if there is anything.. nothing really - they differ a bit based on setting changes e.g. on the broken one I set the fan to layer1 100% to make sure..
Maybe you'll find something - attached the profiles

It does a M126 in the broken one:

Code: Select all

Broken:
G90
M83
M126 S255
G4 P500
M126 S153
M140 S80 T0
M134 T0
M104 S230 T0
M133 T0
G28 W ; home all without mesh bed level

Fixed:
G90
M83
M106 S0
M140 S80
M190 S80
M104 S230 T0
M109 S230 T0
G28 W ; home all without mesh bed level

[wirlybird]

I exported the broken fff to see if there is anything.. nothing really - they differ a bit based on setting changes e.g. on the broken one I set the fan to layer1 100% to make sure..
Maybe you'll find something - attached the profiles

It does a M126 in the broken one:

Code: Select all

Broken:
G90
M83
M126 S255
G4 P500
M126 S153
M140 S80 T0
M134 T0
M104 S230 T0
M133 T0
G28 W ; home all without mesh bed level

Fixed:
G90
M83
M106 S0
M140 S80
M190 S80
M104 S230 T0
M109 S230 T0
G28 W ; home all without mesh bed level

That is exactly what it does to me. Either the M106 is simply not there or it is replaced by another line such as M126.

I sent the same things to support more than once and was told it was my fault.
They said this was happening because I changed settings in the profile. Their advice … load their default profile and don't make any changes and it will be fine.
So, what? Are we not supposed to change any settings? What a load of you know what.

[S3D-Alex]

I opened the "broken" fff file and found a couple things that can cause this to occur.

First off you currently have the "Update Firmware Configuration" checkbox unchecked in the Gcode tab of your Process Settings. This means that if you switch to say the Makerbot profile and then back to this that the Firmware configuration will not update. This will result in the cooling commands for the Makerbot being placed (this is the M126 you see).

The second thing is that in your Process Settings under the Cooling tab you currently have this set to a PWM value of 255. This should be a percentage so in this case you would use 100.

Wirlybird if you see this issue in any cases where either of the above two conditions are not met please post a file to help us look into this further.

[wirlybird]

I opened the "broken" fff file and found a couple things that can cause this to occur.

First off you currently have the "Update Firmware Configuration" checkbox unchecked in the Gcode tab of your Process Settings. This means that if you switch to say the Makerbot profile and then back to this that the Firmware configuration will not update. This will result in the cooling commands for the Makerbot being placed (this is the M126 you see).

The second thing is that in your Process Settings under the Cooling tab you currently have this set to a PWM value of 255. This should be a percentage so in this case you would use 100.

Wirlybird if you see this issue in any cases where either of the above two conditions are not met please post a file to help us look into this further.

I've sent files to support several times over a few years and was only told this can happen if I change any settings in the default profile.
I was actually told on more than one occasion to not make any changes to the profile and it will work fine.
No help whatsoever. I gave up.