If you have gone to print something and one or more of your printers show up as 'Offline', your BuildFlow cannot connect to the Internet. You can run through this list of things to identify the cause of the problem:
Power not connected
First, check if the power cable of the BuildFlow server is connected properly (at the BuildFlow and the wall socket). To confirm that the power is working, you should be able to see a light from inside the raspberry pi case. If power was the issue, you will see that printer's BuildFlow reappear as 'Ready'.
If there are no flashing lights, plug the BuildFlow server into a computer monitor via HDMI and reboot the device. If you get a read out on the screen, then the device is still working. If not, try a different powerpoint or a different micro-USB power supply.
SD not seated properly/card missing
Make sure that the SD containing the BuildFlow software is plugged in properly. Simply remove the SD card and put it back in. If the SD card is missing and you are unable to locate it, please submit a support request.
There are a few potential causes at the network level. The following is a list of things to check for:
- You may need to check your network settings (network name, username, password, proxy information etc.) to make sure BuildFlow isn't being denied access and that you have the correct information in the configuration file you generated.
- Check whether your network is a 2.4GHZ or 5GHZ connection. A lot of schools have been switching off their 2.4GHZ network, however, some older BuildFlow devices were only capable of a 2.4GHZ connection. If you think you may have one of these devices and your school has switched off its 2.4GHZ network, please get in contact with us and attach a photo of the device to the support ticket submission.
- Your Internet access password may have expired since you configured your BuildFlow. Simply reconfigure the BuildFlow with the new password.
- If you are using a wired connection, make sure the Ethernet cable is in good working condition and plugged in at both ends. If you're using a port in the wall, make sure it has been activated by your network administrator.
- There may have been a change in your networks proxy settings or white-listing since you configured the BuildFlow. You will need to reconfigure the BuildFlow to reflect the new proxy details and reapply all relevant domains to your networks white-list.
- If your network requires a devices MAC address to be white-listed, make sure that has been done.