[Closed] Compiling on latest Arduino IDE  

  RSS
Nomad965
(@nomad965)
Trusted Member

Quick question, are there any issues on compiling with the latest Arduino IDE or should one stick with 1.6.8 ?

Thank you

Prusa i3 MK2s MK2.5s Mk3 Mk3s BearPrusa Zaribo 320 - Kit Build - Rc Driver - Tweak freak...
“I know nothing about surpassing others. I only know how to outdo myself.” -Bushido-...
Posted : 13/10/2017 4:10 am
3d-gussner
(@3d-gussner)
Reputable Member

Hi,

I use the newest version 1.8.5 with the Additional Board URL ' https://raw.githubusercontent.com/ultimachine/ArduinoAddons/master/package_ultimachine_index.json ' and searching in the Boards Manger for 'RAMBO'. Used in the past the Arduino IDE 1.6.8 with all the changes but don't need it anymore.

Before you open Arduino IDE you need to copy the right 'Configuration_prusa.h' file from the variants folder:
- 1_75mm_MK2-RAMBo13a-E3Dv6full.h for Prusa i3 MK2/s with miniRAMbo 1.3 controller
- 1_75mm_MK2-MultiMaterial-RAMBo13a-E3Dv6full.h for Prusa i3 MK2/s with MM upgrade and miniRAMbo 1.3 controller

When you compile the code and then export the compiled binary make sure that you use the 'Firmware.ino.with_bootloader.rambo.hex' file to upload via the Prusa firmware uploader.

Posted : 13/10/2017 11:31 am
stevehlau
(@stevehlau)
Trusted Member

Why do you need to upload the hex file with Prusa firmware updater while you can just upload the firemware directly with Arduino IDE? Any advantage of doing so?

...
Posted : 15/10/2017 5:59 pm
3d-gussner
(@3d-gussner)
Reputable Member


Why do you need to upload the hex file with Prusa firmware updater while you can just upload the firemware directly with Arduino IDE? Any advantage of doing so?

Hi Stephan,

I like to have different hex files for different stages of development. So i can see which version i uploaded or roll back if something odd happens.
Don't know if the direct upload has any disadvantages.

Under the motto: Whatever suits you and works is good.

Posted : 15/10/2017 6:35 pm
cornyTrace
(@cornytrace)
New Member


When you compile the code and then export the compiled binary make sure that you use the 'Firmware.ino.with_bootloader.rambo.hex' file to upload via the Prusa firmware uploader.

For me there is only a Firmware.ino.rambo.hex file generated, Firmware.ino.with_bootloader.rambo.hex is absent. Any idea why this is?

I'm running arduino 1.8.5 with 1.0.1 of the board repo on latest MK2 branch.

...
Posted : 13/11/2017 5:07 pm
3d-gussner
(@3d-gussner)
Reputable Member



When you compile the code and then export the compiled binary make sure that you use the 'Firmware.ino.with_bootloader.rambo.hex' file to upload via the Prusa firmware uploader.

For me there is only a Firmware.ino.rambo.hex file generated, Firmware.ino.with_bootloader.rambo.hex is absent. Any idea why this is?

I'm running arduino 1.8.5 with 1.0.1 of the board repo on latest MK2 branch.

Hi,

Ultimachine updated 23. October 2017 their json file check: https://github.com/ultimachine/ArduinoAddons

I use it all the time and have no issue to compile my modified code and upload the file to the printer.
Here some updated Build instructions:
https://github.com/3d-gussner/Prusa-Firmware/tree/MK2-Private_build
https://github.com/3d-gussner/Prusa-Firmware/blob/MK2-Private_build/BUILDING.md
and
https://github.com/thess/Prusa-Firmware/blob/private-build2/BUILDING.md

Hope that helps,

Waldemar

Posted : 13/11/2017 5:22 pm
walter.v4
(@walter-v4)
Active Member

Thanks for the info.

I am compiling source files version 3.1.0 with arduino version 1.8.5

I have added this line in the "Preferences":
https://raw.githubusercontent.com/ultimachine/ArduinoAddons/master/package_ultimachine_index.json

"RAMBo" board has been selected from menu Tools --> Board:

As already mentioned, only "Firmware.ino.rambo.hex" file is generated.

Is it normal behaviour or should we get at some point the second file with the bootloader as well?

Thanks

Posted : 08/12/2017 5:20 pm
3d-gussner
(@3d-gussner)
Reputable Member


Thanks for the info.

I am compiling source files version 3.1.0 with arduino version 1.8.5

I have added this line in the "Preferences":
https://raw.githubusercontent.com/ultimachine/ArduinoAddons/master/package_ultimachine_index.json

"RAMBo" board has been selected from menu Tools --> Board:

As already mentioned, only "Firmware.ino.rambo.hex" file is generated.

Is it normal behaviour or should we get at some point the second file with the bootloader as well?

Thanks

Hi Walter,

sorry for the late answer. Ultimachine updated their ArduinoAddons files on 23rd October 2017 and since that there is only ONE hex file generated.
You can flash your printer with that generated hex file.

Posted : 09/12/2017 2:40 pm
walter.v4
(@walter-v4)
Active Member

Thanks for your quick answer.
I just discovered on prusa3d github folder some "activity" in the stk500v2 and avrdude folders. Maybe Prusa is preparing a new bootloader together with an updated avrdude tool.
Anyway, let's wait and see...

Posted : 09/12/2017 8:51 pm
keith.m10
(@keith-m10)
Eminent Member

You have not installed the <board>boot loader for it to create the other firmware file. 😎

Example: For the RAMBo you need to install the RAMBo boot loader file. But you do not really want to replace the boot loader if you have no problems with it.

Also you can not upload the boot loader through the USB port. The USB communication is part of the boot loader.

Posted : 11/12/2017 1:40 am
valentin.r2
(@valentin-r2)
New Member




When you compile the code and then export the compiled binary make sure that you use the 'Firmware.ino.with_bootloader.rambo.hex' file to upload via the Prusa firmware uploader.

For me there is only a Firmware.ino.rambo.hex file generated, Firmware.ino.with_bootloader.rambo.hex is absent. Any idea why this is?

I'm running arduino 1.8.5 with 1.0.1 of the board repo on latest MK2 branch.

Hi,

Ultimachine updated 23. October 2017 their json file check: https://github.com/ultimachine/ArduinoAddons

I use it all the time and have no issue to compile my modified code and upload the file to the printer.
Here some updated Build instructions:
https://github.com/3d-gussner/Prusa-Firmware/tree/MK2-Private_build
https://github.com/3d-gussner/Prusa-Firmware/blob/MK2-Private_build/BUILDING.md
and
https://github.com/thess/Prusa-Firmware/blob/private-build2/BUILDING.md

Hope that helps,

Waldemar

Hi Walder,

I've followed all of the steps outlined in the links that you have provided and am able to successfully upload the firmware to the printer, however once the flash is complete there is a single error. The top right hand side of the LCD display, rather than showing "Z__ __" it shows "Z ?". For some reason, its not reading the Z component. I've tried simply compiling and uploading the firmware provided by Prusa (3.5.1) however that also has the same issue. I've made a post about this, however, in hindsight I really should have posted here first. Im using an MK3, built earlier last week.

If you have any thoughts on the issue I would love to hear them. Thanks!

Posted : 11/02/2019 8:04 am
simon.b2 liked
3d-gussner
(@3d-gussner)
Reputable Member



For me there is only a Firmware.ino.rambo.hex file generated, Firmware.ino.with_bootloader.rambo.hex is absent. Any idea why this is?

I'm running arduino 1.8.5 with 1.0.1 of the board repo on latest MK2 branch.

Hi,

Ultimachine updated 23. October 2017 their json file check: https://github.com/ultimachine/ArduinoAddons

I use it all the time and have no issue to compile my modified code and upload the file to the printer.
Here some updated Build instructions:
https://github.com/3d-gussner/Prusa-Firmware/tree/MK2-Private_build
https://github.com/3d-gussner/Prusa-Firmware/blob/MK2-Private_build/BUILDING.md
and
https://github.com/thess/Prusa-Firmware/blob/private-build2/BUILDING.md

Hope that helps,

Waldemar

Hi Walder,

I've followed all of the steps outlined in the links that you have provided and am able to successfully upload the firmware to the printer, however once the flash is complete there is a single error. The top right hand side of the LCD display, rather than showing "Z__ __" it shows "Z ?". For some reason, its not reading the Z component. I've tried simply compiling and uploading the firmware provided by Prusa (3.5.1) however that also has the same issue. I've made a post about this, however, in hindsight I really should have posted here first. Im using an MK3, built earlier last week.

If you have any thoughts on the issue I would love to hear them. Thanks!

Hi Valentin,

just released a new how-to build Prusa-Firmware on my github wiki https://github.com/3d-gussner/Prusa-Firmware/wiki/How-to:-Build-Prusa-Firmware
Hope that helps,

Waldemar

Posted : 16/02/2019 4:32 am
Share:

Please Login or Register