Dragino Technology MS14 Wireless Sensor Node User Manual

Dragino Technology Co., Limited. Wireless Sensor Node

User manual

ContentsPreface v1 Introduction 11.1 Ports .................................. 11.1.1 Screw Terminal ........................ 11.1.2 Ethernet ............................ 11.1.3 Power Jack .......................... 11.2 Pushbutton .............................. 21.3 LEDs ................................. 22 Deploying 52.1 Networking .............................. 52.1.1 Wifi Mode ........................... 52.1.2 Ethernet Mode ........................ 52.2 Configuring Sensors ......................... 62.2.1 Status ............................. 62.2.2 Services ............................ 72.2.3 Current Clamp Setup .................... 72.2.4 Sensors ............................ 72.3 Securing the Fluksometer ...................... 82.4 Attaching Current Clamps ...................... 82.5 Connecting Sensor Clamp Cables .................. 82.6 Powering Up ............................. 82.7 Registering .............................. 92.8 Congratulations ............................ 93 Accessing 113.1 Version ................................ 113.2 Token ................................. 113.3 Data Types .............................. 123.4 Retrieving sensor time series data .................. 123.5 Retrieving sensor parameters .................... 143.6 Retrieving real-time sensor data ................... 14iii
PrefaceThis version of the Fluksometer Manual is based on commit d0f7b63c7cb48826of the Flukso Git repository.v
Chapter 1IntroductionLet’s kick off this manual with a short tour of a Fluksometer’s externals. Wewill introduce each of the Fluksometer’s ports, buttons and LEDs.1.1 Ports1.1.1 Screw TerminalThe screw terminal contains twelve inputs. A port on the screw terminal isdefined as a pair of adjacent inputs. We have printed the port numbers on theside of the enclosure for easy reference, with the polarity denoted by + and -.Ports 1 to 3 are analog ports that are tuned to accept Flukso split-core currentclamps. Ports 4 and 5 can be used for detecting pulses. This includes supportfor, but is not limited to, the S0 interface1common to DIN-rail energy meters.Finally, port 6 offers a half-duplex RS-485 serial interface. Contrary to the otherports, the RS-485 port has its polarity indicated by the letters a and b.1.1.2 EthernetThe ethernet port offers support for a 10baseT/100baseTx interface with auto-negotiation and auto MDI/MDI-X crossover detection.1.1.3 Power JackThe center-positive power jack accepts a DC voltage between 9V and 15V. Theswitching adapter should have a minimum rating of 500mA output current.1S0 is an open-collector interface standardized in DIN EN 62053-311
2CHAPTER 1. INTRODUCTION1.2 PushbuttonThe pushbutton has a triple function. Which function will be triggered dependson how long the button is pressed. Make sure the heartbeat LED is blinkingbefore using the button.Toggle reporting mode If you press the button for 2 to 5 seconds, the Fluk-someter will toggle its reporting mode to the Flukso server from wifi toethernet or vice-versa. A blinking wifi LED indicates the Fluksometer isin wifi mode. An always-off wifi LED means it’s in ethernet mode2.Restore networking defaults If you press the button between 10 and 30seconds, the Fluksometer will restore its default network settings.Restore firmware Keep the button pressed for between 60 and 120 secondsto restore the Fluksometer’s stock firmware3and reboot. You will haveto reconfigure all network and sensor settings. Connect to the local webinterface after the heartbeat LED starts blinking again.1.3 LEDsThe Fluksometer has five red LEDs on the top of its enclosure. Together theseLEDs provide us with an overview of the Fluksometer’s internal functioning, thestatus of its network interfaces and its ability to communicate with the Fluksoserver. From left to right, these LEDs are:Wifi If the wifi interface is enabled, the wifi LED will blink. A fast blinkrate [approx. twice per second] signals that no wifi connection can beestablished. A slow blink rate [once every three seconds] signifies that awifi connection has been successfully set up.Ethernet The ethernet LED will be on when an ethernet link is established.This can either be a 10baseT or 100baseTX link in full- or half-duplexmode.Globe After the Fluksometer has finished its boot sequence, the globe LED willbe on when it can access the Flukso server. Every time the Fluksometerreports to the Flukso server, the LED will blink in case of a successfulcall. The globe LED will be turned off when the call is not completedsuccessfully. A successful call has been made when either a 200 or 204HTTP response code is returned by the Flukso server.Heartbeat The heartbeat LED is positioned right next to the globe led. Whilethe globe LED informs us about the status of the Fluksometer’s externalcommunication, the heartbeat LED allows us to monitor the Fluksome-ter’s internal functioning. This LED will be on when the sensor boardis running its firmware. From the moment the Flukso daemon is startedduring the boot sequence, it will start polling the sensor board every sec-2prior to r221 the wifi led would be always on after toggling to ethernet mode3supported from r216 onwards
1.3. LEDS 3ond for data. Each poll triggers a blink of this LED, thus mimicking a realheartbeat. Hence, a ’heartbeat’ is an indication of a Fluksometer that hasbooted, a running Flukso daemon, a sensor board running its firmwareand proper communication between the main board and sensor board.Power The power LED is directly connected to the internal 3.3V supply. Aburning LED indicates that power has been applied to the device and theinternal voltage regulators are working properly.
Chapter 2DeployingThis chapter will guide you through the installation steps that should lead toyour Fluksometer’s successful deployment. Please consult the troubleshootingchapter if you experience any installation difficulties.2.1 NetworkingOut of the box, a Fluksometer will report to the Flukso server via the wifiinterface. Please refer to section 2.1.1 if you wish to use your Fluksometer inthis reporting mode. As detailed in section 1.2, the Fluksometer’s pushbuttoncan be used to toggle the reporting mode to ethernet. The networking setup forthis case is described in section 2.1.2.2.1.1 Wifi ModePower up your Fluksometer and wait until the heartbeat LED starts to blink.Connect your computer to the Fluksometer’s ethernet port. Then surf to192.168.255.1. Configure the wifi page with the proper name and security keyso that the Fluksometer gets connected with the internet via your local wifi net-work. After saving1these settings, the globe LED on the Fluksometer shouldlight up. To further test your configuration, try surfing to www.flukso.net whilethe ethernet cable is still connected to the Fluksometer.2.1.2 Ethernet ModeWhen the reporting mode is toggled to ethernet, the ethernet interface willbe set as a DHCP client. The wifi interface will be disabled. Connect theFluksometer’s ethernet port to your network and find out which IP address1While saving settings doesn’t take long, restarting the whole wifi and networking stackwith its dependencies can take more than a minute to complete. Be patient.5
6CHAPTER 2. DEPLOYINGNote 1 Art thou WAN or LAN?The default settings listed on the network page will mostly work justfine. Should this not be the case, it’s important to understand whichsection on the network page applies to which interface. In wifi mode,the Local Network or LAN section refers to the ethernet interfacewhile the Internet Connection or WAN section is associated withthe wifi interface. So if you want to assign a fixed IP address to thewifi interface, then you should set the Protocol for the Internet Con-nection to manual and fill in the additional form fields. Conversely,if you wish to change the IP settings on the ethernet interface, thenthe Local Network section should be edited.We understand this configuration aspect will be the cause of someconfusion. We however cannot apply the ethernet and wifi namingto these sections directly since they are swapped when toggling theFluksometer into ethernet mode. The Internet Connection will inthis case refer to the ethernet interface and the Local Network to thewifi interface.it has been assigned by your DHCP server. Power up your Fluksometer andwait until the heartbeat LED starts to blink. The globe LED should now be on.Surf to the Fluksometer’s ethernet IP address. No further network configurationsteps should be required. In case you do need to change something, you shouldread note 1first.2.2 Configuring SensorsThe sensor configuration will be synchronized with the Flukso server each timeyou save the sensor page. A synchronization can only be successful when theFluksometer has internet connectivity. You should therefore make sure theglobe LED is lit before commencing this configuration step. If not, then gotosection 2.1.2.2.1 StatusThe status section lists a couple of parameters to help you verify that yourFluksometer is configured and operating correctly.System Time The Fluksometer’s system time is presented in UTC. If thistime setting is showing a Jan 1970 date, then your network firewall mightbe blocking NTP’s UDP port 123.Flukso server ping test When generating the sensor page, the Fluksometerwill try pinging the Flukso server and report the outcome. A failed pingindicates a networking problem, so please consult section 2.1 before con-tinuing the sensor configuration.Last synchronisation time Saving this sensor page will trigger a synchroni-
2.2. CONFIGURING SENSORS 7sation action with the sensor board and the Flukso server. This entryshows last time a synchronisation attempt was made.Last synchronisation status The last synchronisation status indicates thelast synchronisation attempt’s outcome.2.2.2 ServicesYour Fluksometer will by default be configured to report its measurements tothe Flukso server. Clear the checkbox if you want to stop all communicationwith the Flukso server. Since no HTTP calls will be initiated to the serveranymore, the globe LED will be turned off.The Fluksometer can make its sensor measurements available through a localJSON/REST API as well. While the Flukso server allows you to analyze yourhistorical data and derive trend information, this local API is useful for monitor-ing your sensors in real-time. Sixty datapoints with a second resolution will bemade available via the local API. No historical data is stored on the Fluksometeritself. Set the checkbox if you wish to enable the local API feature.2.2.3 Current Clamp SetupSelect the number of phases that apply for your current clamp setup. Whenselecting 3 phases, the three current clamp ports will be grouped and presentedas a single sensor #1. Sensors #2 and #3 will be disabled automatically aftersaving. When selecting 1 phase, each clamp port will be sampled seperately andmapped to sensors #1, #2 and #3 respectively.2.2.4 SensorsAs already indicated in the previous section, a sensor is a logical entity thatcan aggregate multiple physical screw terminal ports as defined in section 1.1.1.Since the screw terminal contains a maximum of six ports, six sensors per Fluk-someter will suffice. A sensor is defined by a unique identifier. Sensors can beenabled or disabled individually. Leave sensors in a disabled state when notin use. An enabled sensor requires a name. This name will be used in theFlukso website’s charts. It’s important that you assign a distinct name for eachenabled sensor associated with your account. By convention, we use main fortotal household electricity consumption and solar for photo-voltaic production.When adding other users to your chart on the Flukso website, the main sensorswill be the ones on display. A sensor can only contain ports of the same class.Ports that have different classes cannot be aggregated into a single sensor. Wenow introduce each of the three classes in turn:Analog Ports #1, #2 and #3 are analog ports. They accept Flukso split-core current clamps of 50A, 100A, 250A and 500A. A three-phase setuprequires all current clamps to be identical. Besides the current range, youcan also specify the line voltage for each clamp. The default is 230V,
8CHAPTER 2. DEPLOYINGwhich applies to the mains electricity voltage in most European countries.Australia and New-Zealand have a 240V power grid. Please consult thisWikipedia article if you are unsure about your country’s mains voltage.Pulse Ports #4 and #5 on the screw terminal are pulse ports. They aremapped to sensors #4 and #5 respectively. A meterconstant defines theamount of flow represented by each pulse. For electricity, the unit is Whper pulse2while water and gas are specified in liter per pulse. Fractionalmeterconstants are allowed down to 0.001.Uart The RS-485 port #6 is mapped to sensor #6. The baud rate is set to afixed 115200.2.3 Securing the FluksometerDisconnect all cables from the Fluksometer. Now find a suitable location nearthe fuse box to install the device. Mounting holes have been provisioned on theback of the Fluksometer. Alternatively, you can use a plastic cable tie or velcro.2.4 Attaching Current ClampsFor safety reasons, switch off the main electricity supply when installing thecurrent clamps. Attach a clamp to each non-neutral line in the fuse box. Closethe clamps firmly. You should hear a double click. The lip should lie flush withthe clamp’s body.2.5 Connecting Sensor Clamp CablesConnect a cable from each current clamp to the Fluksometer’s screw terminal.Use the red wire for positive polarity and the black one for negative polarity.2.6 Powering UpSwitch the main electricity supply back on. Activate the Fluksometer by insert-ing its power plug.2Most small energy meters define their meterconstant in imp/kWh. 1000, 2000 and 5000imp/kWh values on the energy meter equal meterconstants of 1, 0.5 and 0.2 Wh/pulse on theFluksometer respectively.
2.7. REGISTERING 92.7 RegisteringVist www.flukso.net/user/register and fill in the form to create your account.Once logged in, you can associate the Fluksometer with your account. Clickon the My account →Devices tab and submit the Fluksometer’s serial number.You should now see this Fluksometer added to the device list.Point your browser to www.flukso.net. A first reading should be visible on thehour chart within five minutes from powering up.2.8 CongratulationsYou are now part of the Flukso community!
Chapter 3AccessingOnce the Fluksometer is operational, it will start collecting data on its config-ured ports. These measurements are sent to the Flukso server and stored ina time series database. You can access the data in chart form via the Fluksowebsite. The same data is also made available in a machine-readable format viathe RESTful API.3.1 VersionThis chapter is a description of v1.0 of the Flukso API. Although only a singleversion is currently in use, you are required to specify the version for each APIcall. This will prevent any existing code from breaking when new, incompatibleversions of the API are introduced in the future.You can include the versioning parameter either as part of the header (X-Version:1.0) or as a query parameter (&version=1.0).3.2 TokenThe server will verify each time whether a correct token has been specified forthe requested resource. For extracting information, you can use two types oftokens:Sensor-level token A default token is generated for each sensor providingfull read access to the sensor resource. The database structure has beenconceived to support multiple tokens per sensor, each with different ac-cess restrictions. This functionality is however not currently activated.It might be interesting when you want to make a subset of your sensordata available to a third-party service for further processing. This wouldallow you to revoke this specific token at any time without affecting otherservices accessing the same sensor data.11
12 CHAPTER 3. ACCESSINGAccount-level token A token is also made available to each account, whichyou can regard as an API key. This single token allows you to access dataof all devices and sensors associated with your account.3.3 Data Typesunix time() int32 representing the number of seconds elapsed since mid-night UTC of Jan 1, 1970time range() minute, 15min, hour, day, week, month, year, decade, nightunit() watt, kwhperyear, eurperyear, audperyear, lpermin, lperday,m3peryear3.4 Retrieving sensor time series datarequest retrieve sensor data in time series format from flukso.netverb GETurl https://api.flukso.net/sensor/<sensorid>query params interval time range() time range for which valuesshould be returned, from now -interval till nowstart unix time() start timeend unix time() end timeresolution time range() format data in this resolutionunit unit() convert values to specified unitcallback string() jsonp function nameresponse a JSON array containing [unix timestamp, value] array elementsQuery Parameter Compatibility The most straightforward way to extracttime series data from the platform is by use of the interval query parameter.E.g. specifying interval=month will return one month worth of data in a dayresolution, the default resolution for this interval. A default resolution can beoverridden by including it explicitely in the query parameters. If you wouldlike to fully customize the interval, then you should instead use the start and,optionally, end parameters. Below is a compatibility matrix detailing whichparameters are Required [R], Exclusive [X] or Optional [O].interval start end resolutioninterval R X X Ostart X R O OExample 1icarus75@cirrus:~$ curl -k -v -X GET -H "Accept: application/json"-H "X-Version: 1.0" -H "X-Token: d8a8ab8893ea73f768b66b45234b5c3a"
3.4. RETRIEVING SENSOR TIME SERIES DATA 13"https://api.flukso.net/sensor/c1411c6b4f9910bbbab09f145f8533b9?interval=month&unit=watt"> GET /sensor/c1411c6b4f9910bbbab09f145f8533b9?interval=month&unit=watt HTTP/1.1> User-Agent: curl/7.19.7 (i486-pc-linux-gnu) libcurl/7.19.7OpenSSL/0.9.8k zlib/1.2.3.3 libidn/1.15> Host: api.flukso.net> Accept: application/json> X-Version: 1.0> X-Token: d8a8ab8893ea73f768b66b45234b5c3a>< HTTP/1.1 200 OK< Server: nginx/0.7.64< Date: Thu, 07 Jul 2011 10:34:35 GMT< Content-Type: application/json< Connection: keep-alive< Content-Length: 494<[[1307664000,234],[1307750400,169],[1307836800,72],[1307923200,71],[1308009600,103],[1308096000,263],[1308182400,176],[1308268800,165],[1308355200,261],[1308441600,400],[1308528000,139],[1308614400,235],[1308700800,151],[1308787200,141],[1308873600,113],[1308960000,301],[1309046400,210],[1309132800,166],[1309219200,286],[1309305600,237],[1309392000,241],[1309478400,148],[1309564800,125],[1309651200,187],[1309737600,248],[1309824000,263],[1309910400,143],[1309996800,191],[1310083200,"nan"]]Example 2icarus75@cirrus:~$ curl -k -v -X GET -H "Accept: application/json"-H "X-Version: 1.0" -H "X-Token: d8a8ab8893ea73f768b66b45234b5c3a""https://api.flukso.net/sensor/c1411c6b4f9910bbbab09f145f8533b9?start=1309478400&end=1309996800&resolution=day&unit=watt"> GET /sensor/c1411c6b4f9910bbbab09f145f8533b9?start=1309478400&end=1309996800&resolution=day&unit=watt HTTP/1.1> User-Agent: curl/7.19.7 (i486-pc-linux-gnu) libcurl/7.19.7OpenSSL/0.9.8k zlib/1.2.3.3 libidn/1.15> Host: api.flukso.net> Accept: application/json> X-Version: 1.0> X-Token: d8a8ab8893ea73f768b66b45234b5c3a>< HTTP/1.1 200 OK< Server: nginx/0.7.64< Date: Thu, 07 Jul 2011 12:45:02 GMT< Content-Type: application/json< Connection: keep-alive
14 CHAPTER 3. ACCESSING< Content-Length: 122<[[1309564800,125],[1309651200,187],[1309737600,248],[1309824000,263],[1309910400,143],[1309996800,191],[1310083200,"nan"]]3.5 Retrieving sensor parametersrequest retrieve sensor parameters from flukso.netverb GETurl https://api.flukso.net/sensor/<sensorid>query params param all return all sensor parametersresponse a JSON object containing containing all sensor parametersExampleicarus75@cirrus:~$ curl -k -v -X GET -H "Accept: application/json""https://api.flukso.net/sensor/c1411c6b4f9910bbbab09f145f8533b9?version=1.0&token=d8a8ab8893ea73f768b66b45234b5c3a&param=all"> GET /sensor/c1411c6b4f9910bbbab09f145f8533b9?version=1.0&token=d8a8ab8893ea73f768b66b45234b5c3a&param=all HTTP/1.1> User-Agent: curl/7.19.7 (i486-pc-linux-gnu) libcurl/7.19.7OpenSSL/0.9.8k zlib/1.2.3.3 libidn/1.15> Host: api.flukso.net> Accept: application/json>< HTTP/1.1 200 OK< Server: nginx/0.7.64< Date: Thu, 07 Jul 2011 13:28:18 GMT< Content-Type: application/json< Connection: keep-alive< Content-Length: 183<{"access":1310045295,"type":"electricity","function":"main","class":"pulse","voltage":null,"current":null,"phase":null,"constant":1.0,"enabled":1,"lastupdate":[1310045295,1006793948]}3.6 Retrieving real-time sensor datarequest retrieve real-time sensor data directly from the Fluksometerverb GETurl http://192.168.255.1:8080/sensor/<sensorid>query params interval minute fixed intervalunit watt, lperday fixed unitcallback string() jsonp function nameresponse a JSON array containing [unix timestamp, value] array elements

Navigation menu