Jump to content

etienne-martin

Dormant
  • Posts

    13
  • Joined

  • Last visited

Posts posted by etienne-martin

  1. It's not a problem in SketchUp. We would have seen it on your layers view.

    Could you post a screenshot of the Ultimaker configuration?

    What exact material did you used? (to check the temperature, not for the "stopping" problem)

    No special noise from the belts?

    Are the screws on the belts wheels correctly screwed?

  2. Bonjour,

    Comment fait-on pour démarrer le ventilateur en utilisant ces deux moyens?

    Merci d'avance ;)

    Hey,

    Tu as un Ulticontroller ? Ou tu commandes ton Ultimaker via USB ?

    Dans les 2 cas, tu peux commander la mise en marche du ventilateur directement...

    Sinon, tu te créé un fichier G-Code contenant uniquement M106 et tu lances l'impression, ça allumera tout de suite le ventilateur.

  3. I did several tests, forcing (horrible noise) at each start.

    The printers works perfectly, excepting this problem... So the probleme could have existed for the "test print" sent with the printer.

    As I will have soon to use this printer for workshops in the museum, I would like to find a solution (And I think the motor wont't like this situation for a long time...).

    Does the Ultimaker team has something to suggest?

     

  4. Also, not that it will probably make any difference, but how are you asking the UM to read g-code? Via USB or SD on the Ulticontroller? I know there were some issues users discovered when trying to manipulate things with the Ulticontroller while USB printing that I don't know were resolved as the Ulticontroller's primary function is to remove the necessity for the USB tether...

     

    All my tests where made via USB. I only tried to eject the SD card, and put it in again...

    No change this morning.

    I tried to plug an other switch on the Y front input. No change.

     

  5. Thanks for all your answers.

    I'm working in a sciences museum (The Pass, in Belgium), and the ultimaker was chosen built, because I haven't a lot of time to build it my self (I would have love that ;) )

    So the Utimaker arrived without damage on the box, and with a test print done... I think the problem came from the upgrading I asked during the first use wizard operation. ( as said LePaul).

    I'm sure of :

    - the input (according to the name "printed" on the wood... I also tested all the other switches during the wizard test... nothing reacts)

    - the electrical fonction of the switch (tested with its cables)

    - the cables are safe (as i said, the printer was completed)

    - the connection is OK (I disconnected/reconnected several times...)

    - I don't think pullup resistor could be missing on your PCB (as i said, the printer was completed, and a print test was realized before shipping)

    -the limit switch can be touched by the block (but even if I touch it with my finger, there's no recognition during the wizard test...

    I think the input on the PCB is not damaged

    Because, I said earlier, if I try to start the wizard with a contact on the Y front touch sensor's, the program asks me to be sure there's no contact a the beginning of the test :roll:

    (I never print with the Utimaker, only did the test until the limit sensor test for the wizard...) My only test of print was for test the idea of SandervG, printing without finishing the wizard, but the printer forced during the movement for the starting position, so I had to put off the printer)

    Can I find somewhere an older version of Marlin, to see if the problem could come from the upgrade?

    Is it possible to delete the memory (even if I think it's done when I ask an upgrade, during the wizard...)

    I also looked into the Cura posts, but saw no problem like mine...

    I'll try again tomorrow...

     

×
×
  • Create New...