It is not same as VoCore v1.

Just run this script every time you start VoCore2, you will able to make it into AP + STA mode.

If you do not run this script, it will go to AP mode.


uci set wireless.sta.ssid=[HOME AP SSID]
uci set wireless.sta.key=[AP PASSWORD]
uci set wireless.sta.network=wwan
uci set wireless.sta.disabled=0
uci commit
/etc/init.d/network restart
sleep 10
uci set wireless.sta.disabled=1
uci commit


This is not the best solution.
So I just remember one day Vernon Van Steenkist send me one script for VoCore.


#!/bin/sh
#
# Fix loss of AP when STA (Client) mode fails by reverting to default
# AP only configuration. Default AP configuration is assumed to be in
# /etc/config/wireless.ap-only
#

TIMEOUT=30
SLEEP=3

sta_err=0

while [ $(iwinfo | grep -c “ESSID: unknown”) -ge 1 ]; do
let sta_err=$sta_err+1
if [ $((sta_err * SLEEP)) -ge $TIMEOUT ]; then
cp /etc/config/wireless.ap-only /etc/config/wireless
wifi up
# uncomment the following lines to try AP+STA after reboot
# sleep 3
# cp /etc/config/wireless.ap+sta /etc/config/wireless
break
fi

sleep $SLEEP

done

This code is clever, using iwinfo to check if the STA is in normal state.
If after 30 seconds we still can not get into STA mode, we back to AP mode.
This works for VoCore.

For VoCore2, it is slightly different. If we failed to connect to STA, it will not block AP mode.

We can do this to setup your home AP one time:


uci set wireless.sta.ssid=[HOME AP SSID]
uci set wireless.sta.key=[AP PASSWORD]
uci set wireless.sta.network=wwan
uci set wireless.sta.disabled=1
uci commit


then put the following code into /etc/rc.local(run at every startup)


uci set wireless.sta.disabled=0
uci commit
/etc/init.d/network restart
sleep 10
uci set wireless.sta.disabled=1
uci commit


After this, your VoCore2 is able to connect/disconnect STA automatically. Even carry VoCore2 to another position without your home ap, it will still working.

PS: really busy recently :”)

Why is it on indiegogo, is it already a production or just a prototype?

I really do not know indiegogo just have 10% success rate 🙂 Many people do not trust it. ( I have contributed to 2 projects and all failed too. T-T ) We put this on indiegogo just want more people know it, we think it is a good way to spread the news.

VoCore is different than others, it finish its beta, first batch then start crowdfunding. We have send the first batch(sample) to our distributors and some media.  And now it is already in mass production, all features works well.

All videos and photos are from real VoCore2 sample, we do not have anybody good at or have time on PhotoShop or other “magic” tools 🙂

How about current production process?

I have to say the yield rate is not high enough. We meet many troubles, but I think we are able to send out every package on time. 🙂 Do not worry, just wait for our good news.

The Ultimate version shell are not ready yet, left a lot of work to do. Hope the factory could make this done in time. If any parts delayed, we will have to wait. 🙁

Note: a very early/ugly shell from factory. 🙂

1. In the feature list there is a PCIe 1.1, is that real? How to connect to it?

Ye, there is. For VoCore2 standard version there is a hidden interface PCIe1.1. MTK design it for connect to WiFi 5G chips. But for us, we can use it for many interesting projects.

It has eight pins, CLK+, CLK-, RX+, RX-, TX+, TX-, RST, GND.

PS: This is a professional high-speed interface , can not export like other interface, I did not have plan for it yet, so I hide it. OpenWrt do not have driver support it yet, but MTK SDK has its driver source code.

It is at right-top corner of VoCore2.

2. Is it able to power by Li-Battery?

This is a hard question. Our power(5.0VI) support from 3.6V to 6.0V input. Battery output is about 3.7V~4.2V, so the answer is yes. Suggest to use a power bank for stable current.