Who would have thought that this would be so complicated. Or maybe, it was just complicated for me. I thought that I looked everywhere on a step-by-step for installing this, but I finally found it on a forum. Thanks to the beer & chips forum, because I had almost given up on using the rPi for this portion of my project and was going to resort to using windows for the IDE programming of the WeMos D1 clone board.

Anyways, follow these steps (maybe I just held my mouth right and it worked).

The new Arduino IDE will be in the drop down, along with your old Arduino IDE (probably 1.0.5 – which is installed when you type sudo apt-get arduino in a terminal window from the Raspberry). You will notice the difference immediately in the splash screen startup and the window pane header will read, “Arduino 1.6.12”.

Congratulations!

I had to delete the Nokia examples from the sketchbook as the IDE was having difficulties using the “-”. You can change them to “_” and it will work, or just delete that folder. I wasn't going to use those anyways, so I don't think I will miss them.

Any extra libraries that you have downloaded for the 1.0.5 IDE will have to be relocated using the Library Manager in the 1.6.12 IDE (which is relatively painless).

I was also interested in using the WeMos D1 development board for this project since it has the ESP8622 with WiFi native to it. If you are wanting to do this, navigate to File → Preferences and look near the bottom of the window that pops open for “Additional Boards Manager URL:”.

MarkDH102 wrote:Many thanks. I've just installed 1.8.0 using your method and my UNO is working fine.

That's good to know.I'm about to start playing with a Mega 2560 with a CANBUS shield. It will be talking to a PI with CANBUS and it would be great to be able to do all of the development on the PI.
PeterO

Discoverer of the PI2 XENON DEATH FLASH!
Interests: C,Python,PIC,Electronics,Ham Radio (G0DZB),Aeromodelling,1960s British Computers.
"The primary requirement (as we've always seen in your examples) is that the code is readable. " Dougie Lawson

by just using
arduino-nightly-linuxarm.tar.xz
you get the newest, not have to think or check about revisions
and that would be a easy update script.
( i use Downloads... pls change )nano /home/pi/Downloads/arduinoinst.sh

As long as the Arduino installation has the board manager (so ≥ 1.6 or so), it can update drivers/compilers/libraries for any available board. The need to chase after minor versions has pretty much gone away, unless there's a major bug or security issue.

‘Remember the Golden Rule of Selling: “Do not resort to violence.”’ — McGlashan.

If you've extracted file from a tar archive as a regular user, you won't need the privilege escalation of sudo. What you might get, though, are read-only files and folders, which rm -r will choke on. I think that the distribution archives contain git control files, and they're notorious for being read-only. That's why rm -rf works, as it will delete read-only files that belong to you. `sudo rm -r` may delete everything belonging to everyone, so mistakes can remove your entire system

Yes, you can do it manually from the Boards or Libraries menu at any time, and choose whether you want to update particular components or not. After a while, the Arduino UI may prompt you that updates are available, but it's not essential. You don't have to check the Release Notes: it will be more up-to-date than that.

The only advantage I can see of using 1.8.1 over 1.8.0 is the multi-coloured serial plotter. I can't find anything about the nightly builds, but I'm unlikely to ever use those.

‘Remember the Golden Rule of Selling: “Do not resort to violence.”’ — McGlashan.

thanks, i tried but still seehttp://kll.engineering-news.org/kllfusi ... roblem.jpg
followed bytar: Exiting with failure status due to previous errors
at next untar.
i checked with info rm
but not find something, so question is why it works under sudo to completely erase the directory structure?

scruss wrote:I can't find anything about the nightly builds, but I'm unlikely to ever use those.

yes, this up to date thing is overrated...
but i see it like this: on a new release you will find always errors, so its better to wait some days and load the release with the repairs... >> nightly
while with OS there are incremental updates this zip file thing for programs lacks this feature.

my update philosophy for arduino is
++ when i buy a new board
++ when i start a new project

but in this case here i select the nightly thing because it allows to make a install or update script
what is independent from the version!!!
but like in your code viewtopic.php?p=1093180#p1093180
i need to type the version numbers 4 times..
just a idea from a lazy man.

Last edited by KLL on Tue Jan 31, 2017 3:36 am, edited 1 time in total.

That's a nightly build, so you expect problems, and by the looks of things it's already fixed. I think it would be sensible to only report problems here that pertain to full/official releases.

PeterO

Discoverer of the PI2 XENON DEATH FLASH!
Interests: C,Python,PIC,Electronics,Ham Radio (G0DZB),Aeromodelling,1960s British Computers.
"The primary requirement (as we've always seen in your examples) is that the code is readable. " Dougie Lawson

how you know, where you see that? or you mean my work-around? that's not a fix.

Maybe you don't understand the concept of a nightly build, but no one produces actual "fixes" for nightly builds of software, so a workaround or going back to the previous day's working version is as close to a fix as you'll get.
If the developers are on the ball the next nightly build won't have the problem.
Reporting problems with nightly builds here is pointless. No one here is going to fix it !
PeterO

Discoverer of the PI2 XENON DEATH FLASH!
Interests: C,Python,PIC,Electronics,Ham Radio (G0DZB),Aeromodelling,1960s British Computers.
"The primary requirement (as we've always seen in your examples) is that the code is readable. " Dougie Lawson