NetBurner 3.5.0
PDF Version |
|
Once product development is complete, there are a number of choices for device location and configuration:
\nburn\pctools
, and built versions are in \nburn\pcbin
. You may modify or rebrand these utilities and distribute to your end customers, so long as they are only run with NetBurner target hardware.A device can be located the following ways:
\nburn\pctools\find
.
Applications are programmed into flash memory by sending an application image to the device's configuration server, located at its IP address on port 20034. This can be done in a number of ways, all of which are multi-platform (Windows, macOS, and Linux):
To send a file from a web browser, enter the URL of your device. The URL format is "<ip address>:<port number>", such as: "10.1.1.100:20034". Once at the web page, browse for the application image file and select "Update".
nbupdate is a multi-platform command-line utility written by NetBurner. The format is: nbupdate <filename> <ip address>
. For example, nbupdate myApp.bin 10.1.1.196
, or nbupdate myApp.s19 10.1.1.196
.
If the environment variable DEVIP is set the IP address parameter is not required. For example, SET DEVIP=10.1.1.196
. Now you can call nbupdate with only the application file name. To determine the current setting of DEVIP, type "SET DEVIP".
WGET is an industry standard utility that allows you to download files over TCP/IP protocols FTP, HTTP and HTTPS. If you are using macOS or Linux, WGET is usually already installed (or can using your package manager). Windows users will need to install it, please refer to https://www.gnu.org/software/wget/.
The WGET utility can be used for a number of things:
To program a new application into the device:
wget --post-file=myApplication.bin 10.1.1.60:20034/appupdate.html
All updates are processed by the Configuration Server running on the device. The --post-file
specifies a POST operation is to be performed. The IP address and configuration port number are next, along with the server post destination that will always be appupdate.html.
If using authentication with a username of "user", and password of "pass":
wget --auth-no-challenge --user=user --password=pass --post-file=myApplication.bin 10.1.1.60:20034/appupdate.html
Read the current configuration into a file named config.txt: wget 10.1.1.60:20034/Config
.
In this case the destination is Config, rather than appupdate.html.
If you would like to specify a directory to store the file, use the -P
option: wget 10.1.1.60:20034/Config -P \myDir
The easiest way to do this is to first read the configuration and save to a file so you have a template to work with, then edit the settings you need. Then post the configuration file to each new device:
wget --post-file=newconfig 10.1.1.60:20034/Config
Once deployed, your customers can modify the configuration by: