Digistump Forums
The Oak by Digistump => Oak Support => Topic started by: rocksolidsr on March 14, 2018, 07:07:06 am
-
I have the kickstarter edition Oaks and just started messing with them.
I followed the tutorial and was able to connect to the ACRON-XXXXX AP but that is as far as I can get, it never connects and lists available APs
(https://www.dropbox.com/s/eqhfjhfz7g2zu4h/2018-03-14%2009.57.26.png?dl=0)
It currently has software version 1
(https://www.dropbox.com/s/ynqcc0fubvps3ec/2018-03-14%2010.01.09.png?dl=0)
Can anyone help me get this connected
-
So you're connected to the ACORN-XXXXX AP, and when you press next to see the list of APs nothing happens? It's possible you're having the same problem that other people where having, which sounds like it stems from either a bug in the SoftAP page, or a change in how newer web browsers are behaving... as it seems to have been resolved by going back to say a version of firefox (on a computer, that is, not your phone ;)) from about a year ago. It's normal for it to have version 1 at the moment... it obviously hasn't connected to the internet and been able to download the current firmware revision.
To be honest, you're best (and simplest bet) to get the firmware updated is to do the serial update (http://digistump.com/wiki/oak/serialupdate), but obviously, you're still going to have a problem if you can't configure the wireless! Maybe try it on another device? Laptop, etc? Also, when you connect to the Oak's ACORN-XXXXX, on my android tablet, I used to wait about 10 seconds, and then tell it to stay connected if it warned about no internet... seemed that the initial connection took a few seconds to settle. And btw, closer is not better... so probably not best to have the phone right on top of the Oak... have at least 3-4 feet between it and the device configuring it if it's being temperamental.
-
yes I'm definitely connected because I can navigate to 192.168.0.1/version and 192.168.0.1/device-id
I tried using both my computer and my phone. On the computer I tried with Chrome and with an older version of Firefox v45.5.1 and it still did the same thing
-
I was able to update to the latest firmware (I think) following the below tutorials
http://digistump.com/wiki/oak/tutorials/serial_through_arduino
https://digistump.com/wiki/oak/tutorials/serialupdate
After it was done and I rebooted it, I got the three bursts on the LED but I still cannot get a list of access points to get it connected.
I'm not totally sure it updated though as the version at 192.168.0.1/version is still 1?
any other ideas on how to get this up and running?
-
Is there anything else I can do to get these boards to work?
-
Someone reported joy with Firefox 44 on the other thread. Might not make any difference, (because I'm not sure when it broke), but thought it useful to confirm that version worked for someone recently.
-
[...]
I'm not totally sure it updated though as the version at 192.168.0.1/version is still 1?
any other ideas on how to get this up and running?
You should check out 192.168.0.1/system-version, as this will give you an indication of the firmware version. Also if there is no response, then you're running the oldest firmware.
-
Hi,
Same here... just came across a stock of my kickstarter oaks - had a project in mind so I thought I'd give it a go...
So, here's my solution, and it's worked for all the units I've tried it on...
You need a 3.3V USB/TTL Serial dongle, perl, python, node.js and a bit of patience.
Make sure you have installed perl, python, node.js.
Get the particle CLI as per: https://docs.particle.io/guide/tools-and-features/cli/photon/ (https://docs.particle.io/guide/tools-and-features/cli/photon/) or alternatively you could (as per further down that page) just
# how to install the particle-cli
$ npm install -g particle-cli
$ particle login
Now, first, do a factory reset as per https://github.com/digistump/OakRestore (https://github.com/digistump/OakRestore)
Wait a moment, then reset/repower.
Grab the code from here: https://github.com/malaire/oak-with-rpi-server/blob/master/oak-set-wifi.pl
Then connect to the Soft AP of the Oak, and type:
curl -X GET -i http://192.168.0.1/info
Copy into a notepad the id string from the output {"id":"biglonghexadecimalnumberyouneed"....
Setup WiFi with
perl oak-set-wifi.pl YOURSSID wpa2-aes YOURWIFIPASSKEY
Note: Obviously set the correct security setting for your Wifi network.
Wait a moment. Then:
curl -X GET -i http://192.168.0.1/connect-ap
At this point, the Oak should restart and connect to your WiFi. There should be lots of flashing as it connects to Particle Cloud. Give it a minute or two.
If this doesn't happen restart the Oak, and try the last two steps again (set Wifi and tell it to connect).
Once this has all happened, claim your device using the particle CLI (you have to particle login first of course - it's not hard...) - of course you also need to be on your normal wifi connection now.
Using the id number you saved earlier:
particle device add biglonghexadecimalnumberyouneed
Now you can log on to Particle Console, and you should see a new unnamed device. Give it a name.
I'd recommend you push the simple Blink script from Particle to make sure you have latest firmware. Then you can get back to making stuff.
Hope that helps :) Thanks to all who made the scripts used.
-
I have two kickstarter oaks which I just pulled out of the wrapper to use in a project. I have been able to update their firmware via serial. I cannot, however, get either of them to connect to wifi via the method in the documentation. This is after several tries with at least 3 different browsers on three different platforms as well as different versions of said browsers. I have come to the conclusion that Digistump is likely aware of this issue and has (so far) shown little interest in fixing it despite the fact that they are still offering the device for sale on their website. Without the ability to communicate, these devices are essentially junk. Needless to say I'm hugely disappointed in Digistump as this is the first (and very likely the last) product I have bought from them.
-
I believe the issue to be a change in how browsers are interpreting some of the javascript code used resulting in an error in the browser console because something isn't working how it should be, meaning you have to revert to quite a few versions back... say at least a year (i.e. something around firefox 46/47 may work)... You'll have better luck if you go through the "official ESP8266 Arduino Core" thread and change over to the ESP8266 Arduino core, which is what the Digispark core was originally based on, but forked away from it to add Particle and OTA support as that didn't exist at the time.
http://digistump.com/board/index.php/topic,2847.0.html
-
There seems to be two things going on with recent browsers:
1. Cross-site scripting protection. Fetching the file from "https://rawgit.com" means it is not allowed to access "http://192.168.0.1". I solved that by saving the file to my hard drive. Fetching it through a file: URL avoids the problem.
2. After fetching the public key from /public-key the script tries to use it to encrypt the Wi-Fi password before calling /configure-ap. This encryption fails. Until some JS guru fixes it, all I can advise is to use an old browser. IE 11.0.9600 worked for me.