MASSA PRODUCTS CORPORATION M3 & Digi Gateway Quick Guide on Getting Started
M3 & Digi Gateway Quick Guide on Getting Started 2 060513
Massa Products Corporation assumes no liability for applications assistance or customer product design. Customers are responsible for their products and applications using Massa’s sensors.
Getting started
This guide is used to get you quickly started on setting up your application. For more information, see the M3
User’s Guide. Here are the basic steps (don’t power sensor just yet):
1) Gateway: Obtain a gateway and connect it to your laptop’s Ethernet port
2) Gateway: Gain access by using Digi’s Device Discovery utility (40002265_G.exe)
3) Gateway: Verify the gateway’s firmware is up to date (see Digi’s website).
4) Gateway: Verify the gateway’s XBee firmware is at least version 21A0
5) Gateway: Verify/set the gateway’s XBee registers as follows: Scan Channels (SC)=0x1ffe, Peripheral sleep
count (SN)=2880, Cyclic sleep period (SP): 1000
6) Gateway: Manually set the date and time under the System Configuration UI.
7) Gateway: Obtain latest python files from Massa’s website and load dia.zip, dia.py, python.zip and zigbee.py
into the gateway’s Python Files section. The dia.yml will need to be edited.
8) Gateway: In the Python Auto-start Settings UI, enable command line dia.py dia.yml and keep Action on Exit
as None
9) EDIT: Using a text editor, open the dia.yml file and adjust the following line items show below. Note that
enabling a setting is done by removing the # symbol at the beginning of the line.
extended_address '00:13:a2:00:40:98:13:a3!' # enter your sensor’s MAC address as seen on label
sleep_interval_sec: 120 # example sleep time of 2 minutes
awake_time_sec: 31 # maintain 31 sec
outgoing_message_mode: 5 # 5 sets operation to obtain status (level) then wake up & send message
log_status: ‘true’ # record messages in python files section named status_log.txt
Note: For editing the dia.yml, consider obtaining a free copy of Notepad ++ text editor and configure it for python use.
10) Gateway: Load the edited dia.yml into the gateway’s Python Files section
11) Gateway: Reboot and wait 1 minute
12) Sensor: Power sensor and observe the LED to sequence 3 green blinks followed by a steady red. In
approximately 15 seconds the sensor should start blinking red every 2 seconds indicating it is associated with
the gateway. Since the dia.yml control file has been set up to reprogram the sensor, you may notice
additional blinks other than the steady 2 seconds.
13) Sensor: After the sensor settings have been programmed, it will go to sleep and wake up every 2 minutes to
send and message. Point the sensor to a flat target within the sensor operating sensing range.
14) Gateway: After a few wake-up periods, open the status_log.txt file to view the automated messages that will
include the range (distance) to wall, temperature and other information.
15) EDIT: Obtain diagnostic data on an empty tank (or near empty). Using a text editor, open the dia.yml file and
enable the following line item show below (by removing the '#' symbol. Load this edited file into the
gateway and reboot. After a few minutes, check the Python Manage Files UI for waveform files that will
appear as: M3data_0013a200402c163e_20120229075448.M3. For model M3/150 there will be 2 such files, for
other models there will be 4 files. To view these files, obtain a copy of the M3 Application Software and
recall each one. After you have obtained the files, disable this line (with # symbol) and reload the dia.yml.
This is to avoid obtaining diagnostic data on every gateway boot as this does would draw unnecessary sensor
current draw.
obtain_diagnostic_data: 'true'
NOTE: When a sensor is going to be installed for long term testing or in a final installation, it is recommended that
the setting “comm_fail_boot” be enabled. This enables watchdog operation to reboot sensor in rare cases of a
Zigbee communication failure. See sensor manual for information.
This is the minimum requirements of setting up a gateway and sensor for local observation. The next step is to
obtain an account at Digi’s Device Cloud (by Etherios) that will be used as a server to receive the sensor’s
automated messages.
