Just out of curiosity, I'm trying to understand this feature at the slicing level:Added the Option to Enable or Disable Fan Speed Settings

Once you disable Use PWM-Controllable Fans under Printer Settings, the fan speed settings under Advanced Settings will become inactive. If there are no controllable fans on your printer, you can disable this option.

I'm just trying to understand the need for this. Example would be say 3rd party printer support, but even then, lets say their printer does use PWM fans, it would just be ignored anyway?

I just get the feeling someone requested this and I cannot follow the logic on it. There might be a good reason or example, so I kind of want to know to understand that reason (what printer this was requested for) so that I then know what printers has kind of a wonky setup to not send PWM fan gcodes to. Or, it would just seem logical to me, to remove the setpoints in the layer list. Again, sorry, I just really have a curiosity of the printer example where one would even request this setting, let alone use it.

Also, while this release fixed/added the M107 to the end gcode for the Pro2 series, from what I can tell even after using the restore to defaults, the older series profiles did not also add this? The code needs added to every single factory supplied profile as a default. Users with 3rd party printers, they make their own profile or copy or use an existing template, and again, for 99.999% of all printers out there, this still would be valid to turn off everything (including the typical layer controlled print cooling fan) likely turned on during the print.Hopefully in the next next version. All that said, extremely fast release cycle and update there.

Jetguy wrote:Just out of curiosity, I'm trying to understand this feature at the slicing level:Added the Option to Enable or Disable Fan Speed Settings

Once you disable Use PWM-Controllable Fans under Printer Settings, the fan speed settings under Advanced Settings will become inactive. If there are no controllable fans on your printer, you can disable this option.

I'm just trying to understand the need for this. Example would be say 3rd party printer support, but even then, lets say their printer does use PWM fans, it would just be ignored anyway?

I just get the feeling someone requested this and I cannot follow the logic on it. There might be a good reason or example, so I kind of want to know to understand that reason (what printer this was requested for) so that I then know what printers has kind of a wonky setup to not send PWM fan gcodes to. Or, it would just seem logical to me, to remove the setpoints in the layer list. Again, sorry, I just really have a curiosity of the printer example where one would even request this setting, let alone use it.

The reason why we develop this feature is for stopping confusing the customers who own the dual-extruder N series' printer. As by default, there is no PWM controllable fan on dual-extruder N series' printer. We are keeping on getting questions from customer asking why editing the fan speed doesn't show any difference during printing from beginning to now.

Jetguy wrote:Also, while this release fixed/added the M107 to the end gcode for the Pro2 series, from what I can tell even after using the restore to defaults, the older series profiles did not also add this? The code needs added to every single factory supplied profile as a default. Users with 3rd party printers, they make their own profile or copy or use an existing template, and again, for 99.999% of all printers out there, this still would be valid to turn off everything (including the typical layer controlled print cooling fan) likely turned on during the print.Hopefully in the next next version. All that said, extremely fast release cycle and update there.

We have added M106 S0 in all the printing templates. You can see it with Restore Default.

I know this might seem petty, but M106 S0 and M107 are not the same thing.Yes, M106 sets PWM to the minimum and thus the fan does not spin, however, that is not true off.M107 is proper off.The idea being again, proper standards. As a rule, you turn off- true off, anything you turned on at the end of a print.

The issue with dual extruder owners not understanding a constant on fan- that's a user error, it just needs corrected with proper training and manuals. Changing the gcode and settings for that reason??

Again, here is just a case where I don't agree with the decisions, I've stated my reasons.

Also, I read your comment here in this semi related topic viewtopic.php?f=3&t=6299&p=29805#p29805"We tested on our single-extruder printer, the fan didn't stop after print completed."Again, lacking details, what that a 3.1.0 Ideamaker produced gcode or a 3.1.6 produced gcode, and we are talking about the single extruder factory layer cooling fan and the fact the new default end code with M106 S0 for whatever reason failed to turn off the fan at the end of the print?

I'm currently on 3.1.0. Help > Software Update is saying 'Current version is newest.'Seems like it's not working for me, and so I have to go to the website and re-download and reinstall again (and lose settings)?

Jetguy wrote:I know this might seem petty, but M106 S0 and M107 are not the same thing.Yes, M106 sets PWM to the minimum and thus the fan does not spin, however, that is not true off.M107 is proper off.The idea being again, proper standards. As a rule, you turn off- true off, anything you turned on at the end of a print.

The issue with dual extruder owners not understanding a constant on fan- that's a user error, it just needs corrected with proper training and manuals. Changing the gcode and settings for that reason??

Again, here is just a case where I don't agree with the decisions, I've stated my reasons.

Also, I read your comment here in this semi related topic viewtopic.php?f=3&t=6299&p=29805#p29805"We tested on our single-extruder printer, the fan didn't stop after print completed."Again, lacking details, what that a 3.1.0 Ideamaker produced gcode or a 3.1.6 produced gcode, and we are talking about the single extruder factory layer cooling fan and the fact the new default end code with M106 S0 for whatever reason failed to turn off the fan at the end of the print?

Kind of what I'm getting at here.

Thanks for your comments first.For Marlin-based printers, the M106 S0 code works the same as M107 to stop the fan. Although the definition of M106 code is for setting fan on, M107 is for setting fan off, M106 S0 code can stop fan as well. And for the other printers, M107 code may have been deprecated, as we found this here: http://reprap.org/wiki/G-code#M107:_Fan_OffBut take the origin different definitions of these two codes into consideration, we will take your suggestion and use M107 to replace the current M106 S0 in future version.

About my comment in the other post you mentioned, it was tested with version 3.1.0 ideaMaker on single extruder printer with one default code-control fan.

probably already asked this question: will there be an application ideamaker for tablet phones? or even worth the wait? It would be very convenient on the road or remotely to make calculations, prepare models for printing, answer customer questions on the basis of calculations. otherwise you have to carry a laptop with you, which is very large and inconvenient. Not everyone can afford a compact apple netbook.

There seems to be a new function when a new print is intended to start via WLAN: A hint occurs similar to "I have removed all previous printed components" in red color. But when clicking on it the same hint comes back after some milliseconds and requires to release the printer at its own display as it was in older versions. That makes no sense in my opinion

Nobbi50 wrote:Release 3.1.6 crashes very often, when I try to load an uploaded file from the internal memory of the N2+.following message: pops up:

Runtime Error!Programm:C:\.....\ideaMaker.exeThis application has requested the Runtime to terminate in an unusual way.Please contact the applicatiion's support team for more information.

This never happened with older versions of IdeaMaker! I installed the previous version again and there is no failiour. Then I installed the 3.1.6 again and I got the same problem.

Windows 10

FWIW, I'm on Win7 64bit and saw the same crash with 3.1.6. The way it invoked was I think when I went to open a new STL to slice it, there may have been the connection window open to the printer hidden behind other screens. So it could have been 2 instances open. Either way, yes I have seen the crash, no, it's not OS dependent, does seem to be specific to 3.1.6.