Jump to content

Cura update

ryan-walks

By ryan-walks
in UltiMaker Cura

 Share

Recommended Posts

ryan-walks

ryan-walks 0

Posted
Posted · Cura update

Hey guys,

I recently started working with a Ultimaker printer and am trying to get it up and running. Before the printer was running using ReplicatorG, I install Cura and then updated the new firmware. Now its stopped working with ReplicatorG and Cura. When I run the checkup on Cura it just says "connecting to machine" and that disk spins around forever.

If it hit skip checks, the next screen still fails at connecting to the machine.

I have matched the BAUD rates and made sure the com ports are correct in device manager. I'm running win7 32bit.

 

    • Link to post
    Share on other sites
    ryan-walks

    ryan-walks 0

    Posted
    • Author
    Posted · Cura update

    Where can I find the error log in the first run wizard?

    I've tried loading the code on the uC manually using avrdude and I get this:

    tkeo.jpg

    This is my problem in Cura:

    93ky.jpg

    The BAUD rate in my device manager should match the baud rate in cura right? Also where can I find old firmware, stuff that will work with ReplacatorG 24? If I can't get this to work I will just have to downgrade.

     

    • Link to post
    Share on other sites
    ryan-walks

    ryan-walks 0

    Posted
    • Author
    Posted · Cura update

    Hey I just got an error log:

     


    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Send: M105 T0
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Send: M105 T0
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Send: M105 T0
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Send: M105 T0
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Send: M105 T0
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Send: M105 T0
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Send: M105 T0
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Recv: echo:Unknown command:""
    Recv: ok
    Send: M105 T0
    Serial timeout while writing to serial port, trying again.
    Unexpected error while writing serial port: SerialTimeoutException: 'Write timeout' @ machineCom.py:_sendCommand:506
    Changing monitoring state from 'Operational' to 'Error: SerialTimeoutExcepti...'
    Connection closed, closing down monitor

     

    • Link to post
    Share on other sites
    gr5

    gr5 2,172

    Posted
    Posted · Cura update

    Hopefully daid will post again as I have never had any trouble in this area and don't understand it but I believe the default hex file is the one with the faster baud rate yet you installed the lower speed rate (although I thought it didn't matter). The log file looks EXACTLY like what I would expect with baud rate issues. Also with a broken USB, or arduino, lol.

    Anyway I would go to cura and go to "file" "preferences" and set the baud rate explicitly to whatever version of the firmware baud rate is.

     

    • Link to post
    Share on other sites
    ryan-walks

    ryan-walks 0

    Posted
    • Author
    Posted · Cura update

    Hopefully daid will post again as I have never had any trouble in this area and don't understand it but I believe the default hex file is the one with the faster baud rate yet you installed the lower speed rate (although I thought it didn't matter). The log file looks EXACTLY like what I would expect with baud rate issues. Also with a broken USB, or arduino, lol.

    Anyway I would go to cura and go to "file" "preferences" and set the baud rate explicitly to whatever version of the firmware baud rate is.

     

    Thanks for your reply, I've when I go into device manager it won't let me set my baud rate to the 250k, so I installed "MarlinUltimaker-115200.hex" from the \firmware directory using the custom firmware loader on Cura. Still same problem.

     

    • Link to post
    Share on other sites
    Daid

    Daid 306

    Posted
    Posted · Cura update

    Default firmware is at 250000 baud, but the problem could be hardware related, I've seen the above happen with a bad Arduino.

    I see a "operational" state in your log, which can only happen if it gets a proper temperature reading from the machine, which kinda rules out a baudrate problem.

     

    • Link to post
    Share on other sites
    ryan-walks

    ryan-walks 0

    Posted
    • Author
    Posted · Cura update

    The unit was working fine until the firmware upgrade.

    Are there steps for troubleshooting the shield? Or could it be the mega2560?

    If I used an ISP programmer to erase & reprogram the flash, could that work? I'm thinking it could be the USB boot loader chip on the board.

    edit: If anyone know what firmware the boards were running when ReplicatorG0024 was the most current software that would be perfect. That's when the printer was working last.

    edit edit: twpd.jpg

    Here is a picture of the shield, maybe this will help.

     

    • Link to post
    Share on other sites
    Daid

    Daid 306

    Posted
    Posted · Cura update

    ... It's blue? Wondering where you got it from.... because that's not an official UM board. The 1.5.4 electronics where green, have "ultimaker.com" on the (and a few other things), the temperature sensor connectors are the wrong type, and the steppers do not have cooling-ribs. There are also some other colored wires that are not standard UM.

    Anyhow, if there is a black Arduino on there from DFRobot, then your Arduino is broken. Very early Ultimakers had those and I have not seen a single one of those Arduino still working this day.

    Else, pull off the Arduino and check if you can program it like that. You could also try the ISP route, but if the normal bootloader no longer works then a big chance that the ISP route won't do you any good.

     

    • Link to post
    Share on other sites
    ryan-walks

    ryan-walks 0

    Posted
    • Author
    Posted · Cura update

    Thanks for your help, this is defiantly useful information. So if its the wrong shield, is it possible that when I updated the firmware it burnt some of the ports? Is there any documentation of this older shield and possible compatible firmware to go along with it?

    This is the Arduino, so not the black one.

    thnu.jpg

     

    • Link to post
    Share on other sites
    Daid

    Daid 306

    Posted
    Posted · Cura update

    Well, it says 1.5.4 on the board. And the firmware still works fine with the 1.5.4 boards (which are a quite common version, I have one at home and 3 in machines in our local FabLab)

    Did you try programming the Arduino without the shield connected?

     

    • Link to post
    Share on other sites
    Daid

    Daid 306

    Posted
    Posted · Cura update

    Also, out of curiosity, that the Electronics looks like a knockoff. Curious where you got it from. The Arduino also looks odd, as it does not say "Made in Italy" (something seen on all real Arduino's) So could be shady build quality electronics.

     

    • Link to post
    Share on other sites
    ryan-walks

    ryan-walks 0

    Posted
    • Author
    Posted · Cura update

    I loaded new firmware fine using my ISP programmer, it loads fine. Its still not working with Cura.

    I found this:

    http://firmware.ultimaker.com/firmware/

    Is there anything that I could try to get it working with ReplacatorG0024 or Cura?

    edit: ReplacatorG0026 not 24

     

    • Link to post
    Share on other sites
    ryan-walks

    ryan-walks 0

    Posted
    • Author
    Posted · Cura update

    Also, out of curiosity, that the Electronics looks like a knockoff. Curious where you got it from. The Arduino also looks odd, as it does not say "Made in Italy" (something seen on all real Arduino's) So could be shady build quality electronics.

     

    I'm not %100 sure where the electronics came from, and the arduino says "designed in Italy" on the back.

     

    • Link to post
    Share on other sites
    kolia

    kolia 31

    Posted
    Posted · Cura update

    Not very useful for you but I got the same problem some times ago. Most probably there was a problem with the bootloader. I then tried some alterative way to load the firmware with a secondary original Arduino (is it what you call ISP?) but it didn't work either (or I didn't do it well, as I'm a electronics newbie).

    In the end I just got a new Arduino and problem solved immediately.

    And yes, it was a knockoff too (one with 'Made in Italy' written on even)... you get what you pay I guess :)

     

    • Link to post
    Share on other sites
    ryan-walks

    ryan-walks 0

    Posted
    • Author
    Posted · Cura update

    An ISP (in system programmer) was designed by Atmel to let programmer handle non-usb compliant microcontrollers. They use a communication method known as SPI (Serial Peripheral Interface). They look like this:

    ispMKII.jpg

    They have headers like this:

    isp_6pin.jpg

    The Arduino Mega2560 has two of those headers, one for the bootload uC and one for the main uC. If you use the bootload uC to load code onto the main one (using the usb connection), your using the boot uC as an ISP (basically). Essentially its one more thing to go wrong IMO.

     

    • Link to post
    Share on other sites
    ryan-walks

    ryan-walks 0

    Posted
    • Author
    Posted · Cura update

    Update:

    After sifting through dozens of hex and source files, with a little guess work, and a lot of research. I finally found firmware that will not only connect, but let me jog and heat up the extruder!

    Its the:

    http://firmware.ultimaker.com/firmware/UM-v1.1-PCB1.5-thermocouple-build-1-AtMega2560.hex'>http://firmware.ultimaker.com/firmware/UM-v1.1-PCB1.5-thermocouple-build-1-AtMega2560.hex'>http://firmware.ultimaker.com/firmware/UM-v1.1-PCB1.5-thermocouple-build-1-AtMega2560.hex'>http://firmware.ultimaker.com/firmware/UM-v1.1-PCB1.5-thermocouple-build-1-AtMega2560.hex

    at:

    http://firmware.ultimaker.com/firmware/

    Its looks to be some older stuff, but it seems to work on ReplacatorG0026.

    edit: It seems to be working with Cura as well.

     

    • Link to post
    Share on other sites

    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now
     Share
    Followers 0
    Go to topic listing

    • Our picks

      • UltiMaker Cura 5.7 stable released

        UltiMaker Cura 5.7 stable released

        ArunC posted a topic in UltiMaker Cura,

        Cura 5.7 is here and it brings a handy new workflow improvement when using Thingiverse and Cura together, as well as additional capabilities for Method series printers, and a powerful way of sharing print settings using new printer-agnostic project files! Read on to find out about all of these improvements and more. 
         
          • Like
        • 18 replies
        MariMakes

        Picked By

        MariMakes,

      • Release Notes: S-Line Firmware 8.3.0 (Latest)

        Dustin posted a topic in Firmware,

        S-Line Firmware 8.3.0 was released Nov. 20th on the "Latest" firmware branch.
        (Sorry, was out of office when this released)

        This update is for...
        All UltiMaker S series  
        New features
         
        Temperature status. During print preparation, the temperatures of the print cores and build plate will be shown on the display. This gives a better indication of the progress and remaining wait time. Save log files in paused state. It is now possible to save the printer's log files to USB if the currently active print job is paused. Previously, the Dump logs to USB option was only enabled if the printer was in idle state. Confirm print removal via Digital Factory. If the printer is connected to the Digital Factory, it is now possible to confirm the removal of a previous print job via the Digital Factory interface. This is useful in situations where the build plate is clear, but the operator forgot to select Confirm removal on the printer’s display. Visit this page for more information about this feature.
          • Like
        • 0 replies
        MariMakes

        Picked By

        MariMakes,
      View All
    ×
    ×
    • Create New...