Hi @northstar the smart mode threshold specifies the minimum RMS acceleration level (on any X, Y, or Z axis) required for the sensor to permit a data transmission (including Processed Data and Time Domain (Raw) data, if configured).
Transmission occurs at the configured Sampling Interval or when triggered by the Acceleration Wake/Interrupt Threshold (if enabled), provided the Smart Skip Interval has elapsed.
Smart Skip Interval dictates how many consecutive sampling intervals the sensor will skip transmitting data if the RMS acceleration remains below the Smart Mode Threshold.
All regular or motion transmissions are evaluated against the Smart Mode Threshold and Smart Skip Interval before being sent.
I would recommend to take a look at the Gen4: Understanding Data Transmission in Smart Mode article, and focus on flowchart, it explain the transmission logic under smart mode.
Thank you,
Eduardo M
Hi Eduardo,
I am trying to understand the structure of the raw data that is being transmitted by the vibration sensor.
In the Data dropdown, there are array fields labeled [0-9], [10-19], etc. When opening the file I see values associated with numbers 0-9, 10-19, etc. What are these values? They seem too high to be G values, but If they are G values, where is the time associated with each reading?
FYI, I am trying to create a node that would format the data in the following structure: time, X-value, Y-value and Z value then sent the associated json file our cloud server.
Please advise. Thanks.
Hi @northstar Just a quick note on it, what you’re seeing in that image isn’t actually the Time Domain Data message. Those array fields labeled [0-9], [10-19], and so on, are what we expect to see for Processed Data. They represent the bytes of the processed message.
We touched on this earlier in our conversation, but as a reminder, you can always tell the difference between Processed and Time Domain data by checking the mode property:
- If
mode = 1, it’s Time Domain.
- If
mode = 0, 2, or 3, then it’s Processed.
We also sent a screenshot previously that shows this distinction, so feel free to take another look at that as a handy reference.
To make sure you start getting the auto Time Domain data, you’ll want to follow the settings we discussed earlier and use the wireless_config.json file we shared. Did you get a chance to import that flow and apply those configurations? Auto Raw Destination Address?
Thank you,
Eduardo M
Eduardo,
Thank you for recapping the information. That is understood. My question is regarding the structure of the data/array. Attached is a sample list of raw data being generated. What do the values corresponding to the array count indicated (e.g. [12: 95], etc.)? Also where is the corresponding time for the G? As mentioned earlier, I am trying to create a node that would format the data in the following structure: time, X-value, Y-value and Z value then sent the associated json file our cloud server.
Hi @northstar great, sure it represents the Time Domain Data over each of the axis (x,y and z) in “G”:
"x": [-0.07, 0.1, ...],
"y": [0, 0, ...],
"z": [0, 0, ...]
You will have multiple samples here depending on the chosen rate. The Time associated to this data is the time_id property, in your case is:
time_id : "21:06"
You can set the RTC value using the Set RTC command, this will sets the sensor’s internal Real-Time Clock (RTC) to the Gateway current time.
Please take a look at this and feel free to let us know if you have any questions.
Thank you,
Eduardo M
Will do. Where would I be able to find the RTC data for transmission.
Hi @northstar is the time_id into Time Domain Data sensor_data message.
Thank you,
Eduardo M
Hi Eduardo,
We are unable to set the data transmission from a vibration sensor from “Raw” to “Processed”. We have tried to reset the sensor and gateway several times, but nothing has worked. Any ideas?
Hi @northstar Just to make sure, are you looking to configure the operation mode to “Processed”?
Also, could you confirm if you’ve already enabled the Auto config, OTF Config, Wait for Network formation, and Active check-box in Mode command, and then set the Processed mode?
did you get any error during sensor configuration?
Thank you,
Eduardo M
that’s what we have done…but the sensor continues to transmit Raw data?!
Hi @northstar could you share a screenshot of your Config Results message after configuration, please. It comes from Wireelss Device node and should looks like this:
Thanks,
Eduardo M.
Eduardo,
We fixed it. Basically we reset the complete flow. Seems to be working. Thanks for your help.
