User`s guide

MASSA PRODUCTS CORPORATION
Product Manual- April 24, 2012 7 M3 Wireless Ultrasonic Level Sensor
3.0 Operating Modes for Gateway and Sensor
3.1.8 Dia.yml Settings Description – Outgoing Status Message Mode
The setting “outgoing_message_mode” in the dia.yml file sets the type of automated outgoing status message format
when the sensor wakes up from sleep. See Appendix E for the format of the outgoing message and section 4.0 for an
applications example. Leaving this control line out of the dia.yml, blank value, or incorrectly typed setting value will
not access this sensor setting. Limits: 0 – 6 (Limits 0 – 4 for sensor main versions to 25)
outgoing_message_mode: 0
3.1.9 Dia.yml Settings Description – # of Records in Outgoing Status Message
The setting “auto_message_length” in the dia.yml file controls the number of Event Blocks (records) within the
automated outgoing message when sensor wakes up from sleep. See Appendix E for the format of the outgoing
message. Leaving this control line out of the dia.yml, blank value, or incorrectly typed setting value will not access this
sensor setting. Limits: 1 – 8.
auto_message_length: 8
3.1.10 Dia.yml Settings Description – Ultrasonic Signal Sensitivity Setting
The setting “sensitivity” in the dia.yml file controls the thresholds levels and timing for capturing the reflected signal.
Most applications should have this set to ‘Normal’. When considering settings other than Normal, set the dia.yml to
obtain waveforms for a target placed at the furthest distance, like an empty tank. Review the waveform as seen in
Appendix F to determine if this setting requires a setting other than Normal. Poor reflections should go in the direction
of a Very High setting while very strong signals and applications with short sensing ranges can consider settings in the
Very Low direction. Customized settings is an option on more difficult applications, consult Massa Products for
support. Leaving this control line out of the dia.yml, blank value, or incorrectly typed setting value will not access this
sensor setting. Select 'normal', 'high', 'very high', 'low', 'very low' or 'custom'. Enclose with quotes.
sensitivity: 'normal'
outgoing_message_mode mode name
Outgoing Status Message Mode Description
0 Manual Sensor will only send messages upon request during the Awake period
1 Auto Send 1
Sensor will send a single Command 1 message containing up to 8 blocks of Event Records will
wait for the entire programmed Awake Time for any normal protocol requests. There is no demand
for any acknowledgement and no retry will be sent.
2 Auto Send 2
Sensor will send a single Command 1 message containing up to 8 blocks of recorded Event
Records will wait for ½ the programmed Awake period then sensor will send a second copy.
Awake period will continue in its entirety for any normal protocol requests. There is no demand
for any acknowledgement and no retry will be sent.
3 Auto Send 3
Sensor will send a single Command 1 message containing up to 8 blocks of recorded Event
Records will wait for ½ the programmed Awake period for a protocol acknowledgement
(Command 200). If acknowledge message is not received within ½ of Awake period, then a second
copy will be sent. Awake period will continue in its entirety for any normal protocol requests.
4 Auto Send 4
Sensor will send a single Acknowledge message indicating that it is awake. Coordinator now can
send messages during the Awake period.
5 Auto Send 5
Sensor will first acquire range and other status information followed by sending a single Command
1 message containing up to 8 blocks of recorded Event Records. The Awake period will continue
in its entirety for any normal protocol requests. There is no demand for any acknowledgement and
no retry will be sent. The Data Collection Interval Register is disabled.
6 Auto Send 6
Sensor will first acquire range and other status information followed by sending a single Command
1 message containing up to 8 blocks of recorded Event Records. Sensor will wait for ½ the
programmed Awake period then send a second copy. The Awake period will continue in its
entirety for any normal protocol requests. There is no demand for any acknowledgement and no
retry will be sent. The Data Collection Interval Register is disabled.