Here we collect all errors that users have experienced
Q: I experience that regardless of which voucher I use, I always get redirected to another page?
- A: Yes, we have not fixed the communication between the LNCC and the voucher server, and too often this communication fails. Thus, the voucher
4) Deployment on site
This chapter is part of the DigI:Processes_and_Technology, and describes the initial testing on arrival, as well as the deployment in the field. Note: Before you go out in the field, perform the test on arrival to make sure the equipment works.
4.1 Test on arrival
After receiving the equipment from the customs office, an initial test needs to be accomplished for the equipment set. For villages as part of the medical studies, the test is done by Felix Sukums and his team at Muhas.
For equipment going out to the communities, the initial needs to be accomplished at a site where Mobile Broadband (3G, 4G) is available. The test plans is provided by Wisam to accompany the testing.
- (1) InitialTesting Overview.pdf on owncloud = DeviceConfig
- (2) Detailed TestPlan.pdf on owncloud = DeviceConfig
Initial testing -
- LTE Antenna: insert SIM card, connect cables, POE, power source test, and check that lights are working. A detailed connecting and testing document is available on OwnCloud (see Figure 4.1 or (1) InitialTesting Overview)
- LNCC router: connect the Internet wire coming from the LTE to port 1 on the LNCC, connect the LNCC to power source, and check if the power light is lightning green on the back side, in order to establish a local network /wifi.
- Village server/ RPI: connect the RPI to electricity using the charger, normal Samsung mobile charger, and check if the power light is blinking/on. Then, connect the PRI to port 2 on the LNCC using an Internet wire.
- When all the equipment are well connected to each other and the electricity the person should check on his mobile/ Tablet the accessibility of the Basic Internet network.
Success: I can connect, next step implementation in the site and testing 4.2.
Failure: I can't connect, go to step 4.3.4.
- Test the village platform by opening your browser and open the web-site yeboo.com, or what have been specified for the specific village your are testing its spot :
Success: I can reach the site and the videos, next step 4.2,
Failure: I can't reach. the reason could be:
a) check the RPI connection to LNCC on port 2, and electricity, if that is well connected.
b) check with Wisam or Hamed if the RPI is identified to work with the used LNCC
c) check with Wisam or Maurice that the main server of the village platform is working
d) open the RPI case and check the small lights beside the USB, red and green lights, if they aren't working that means no power and Internet are reaching the RPI otherwise if reason a) was checked well that indicates the RPI is dead and should be replaced with a new one take contact with Wisam
- If the information spot providing wifi and the village platform is accessible, then, the set will be shipped to its final destination, the targeted village.
4.2 Testing in the field
After arrival at the site, connect the equipment and perform a functionality testing before raising the pole. Connect the equipment in the same way in step 4.1 and repeat all the tests to ensure getting the connection to the Basic Internet network and the village platform.
4.3 Error testing in the field
When the equipment (LTE, LNCC, Village server) are deployed in the field, the user should be able to perform simple steps to check the configurability. Through our central equipment, we are able to connect remotely to the LNCC and the RPI (if they are on the network).
A user being at the the site can test the following:
- 4.3.1. I look for Wifi "BasicInternet", and connect to Wifi.
Success: I can connect, next step 4.3.2.
Failure: I can't connect, go to step 4.3.4.
- 4.3.2. - only if the Raspberry Pi is connected on port 2 - The user opens a browser (e.g. Chrome) and connects to Yeboo.com (or Yeboo)
Success: The health information page (see Figure 1) is shown, and the hotspot works as planned
Failure: Web site not found. Goto step 4.3.3.
- 4.3.3. In the Web browser, type google.com.
YES: Google is working, network access. Test Yeboo.com. If still not connected to the health site, probably the Raspberry PI is dead, or a configuration team. Contact the BasicInternet Team
NO: if google.com is not shown, then we have no network access.
- Try the following Web sites: 10.5.50.1 - if success, it means that the network connectivity is established (?)
- basicinternet.org - we have full network access
- if these sites are not working, then we have the potential problems:
- No credit on the SIM card,
- Devices not working,
- Cables unconnected/loose
the LTE/UMTS network is down. Use the "network cell info light" App (Google Play) to see if a mobile network is up.
- 4.3.4 Check the equipment: Is the light blinking at the back of the LNCC?
NO: no power, or LNCC is dead.
YES: Lights are blinking. Reboot the LNCC: disconnect the power, reconnect and see if the lights come up. Check if you have electricity. If the LNCC still does not work, we need to replace (step 4.4)
Question: What happens if the RPI is "dead", what will the user see when typing Yeboo.com?
- A: If the Raspberry Pi is dead/no power, and we type Yeboo.com, we'll get address not found
4.4 process for replacement
Make sure that all LNCCs and the corresponding RPIs are connect to the network