Jump to content

Dustin

Team UltiMaker & Admin
  • Posts

    689
  • Joined

  • Days Won

    13

Posts posted by Dustin

  1. Feedback is great and all.. 
    But your mostly shouting at the void right now.

    Best place to provide this such of feedback is on github where the dev's are nearly full-time.. 
    https://github.com/Ultimaker/Cura/discussions
    They only occasionally lurk the community forum.

    Additionally UltiMaker Cura is open source. The shear number of people that contribute to the code base makes it clear when people want something that has no resources to be developed they take it upon themself to get it done. 
    With that said, clearly there has not been as much demand for added support for this functionality you mention as it does not appear anyone has figured it was worth their time to add it if they wanted it.

  2. From what i can tell these logs are all for Dremel slicer not UltiMaker Cura.
    You will need to contact Dremel for help with that. 

    As for running UltiMaker Cura it might be possible Dremel is using the same system directories as UltiMaker Cura (this has been noted to happen with other brands) which corrupts the UltiMaker Cura files.

    UltiMaker and most of the community here isn't able to offer much advice for unofficial releases of UltiMaker Cura. 

  3. it sounds like you have interference despite having decent scores.

    Considering you have replaced the fan, i would make sure you have not accidentally smashed wires in the printhead. 
    Smashed wires cause noise that messes with the sensor.. sometimes these need to be replaced sometimes simply correcting the routing of the wire will fix it. 

    I understand UltiMaker was out of stock on fans for a few weeks. But if you self sourced the fan, please ensure its the same model. A similar fan for example from amazon will usually not work and generates interference with the sensor readings.

    Beyond that I would recommend following the final steps at the bottom and contacting support with your log files etc as they can often help find issues or errors.

    UltiMaker does not provide formal support via the community, but I wanted to make sure information here was accurate and not misleading. Improperly troubleshooting the issue can endup more costly than it needs to be.
     

  4. not sure why you replaced the capacitive board.. unless the wires were damaged or a flooded printhead damaged it.. the issue is almost never related to that part.. the true sensing is up in the printhead pcb.. the capacitive board is more of a "antenna" to over simplify it. 

    Looking at how dirty beadsters printhead is inside.. and the fact that the fan sticker is some reason on the outside of the printhead makes me think the fan is too dirty or even damaged.. 
    If that fan is not running at spec it can cause issues with active leveling.

    People often overlook the support article for this.. but statistically it resolves a significant majority of issues.
    https://support.ultimaker.com/s/article/1667410781005
    It is common people skip steps on this article and its usually those cases where what they skipped was the issue. 

  5. 6 hours ago, haeh said:

     

    It's an old thread so sorry to reply now, but since I was directed here from google when searching about the slow boot of UM2+C, it's worth correcting the statement above.

     

    The UM2+C does NOT run linux, but just a version of Marlin.

    If you check the schematics of the mainboard used, the microcontroller used is an ATMEGA2560, which is WAY WAY too slow to run any operating system. It runs just Marlin, and it's also not particularly good at it, if you consider that Marlin above a certain speed starts sending steps to the motors not uniformly, but in groups of two or four. 

    Check "marlin double quad stepping", which starts happening at 10 kHz, which means for the UM2 series 125 mm/s.

     

    So we don't know why the UM2+C is so slow, but it's not linux.


    Actually now you're wrong as well.

    While you are correct about the UMO, UM2, UM2+.

    The UltiMaker 2+ Connect runs a dual microcontroller system.
    The motion board is still powered by the ATMEGA but the parent controlling system and what drives the display and networking is indeed a linux based system powered by an onion module.
    The ATMEGA is running a slimmed down version of marlin that mostly only processes commands from the master linux system.

    Though regrettably, yes the boot time of the 2+ Connect is very slow, there is not much that can be done about this.

    Since the release of the UltiMaker 3, and to the current S7. All printers run this dual microcontroller configuration though they have all gotten faster primary controller processor upgrades/memory/etc. This is why a S series (S3,S5,S7) will boot considerably faster in most cases.

    This is also why its not possible to plug a modern UltiMaker S series or 2+ Connect (or even UM3) into a computer via USB. The printer no longer functions as a client but a self contained host and client.
     

  6. Please don't go after community members. 
    They are only offering help.

    It sounds like you feel you have found bugs in UltiMaker Cura, this needs to be reported via github not via ranting at community members on the community forum.
    Report bugs here: https://github.com/Ultimaker/Cura/issues

    Additionally it appears your issue relates to remote desktop? that isn't even officially supported or recommended by UltiMaker.
    Details here: https://support.ultimaker.com/s/article/1667337917781

×
×
  • Create New...