Tinymesh Q&A
Enter your keywords to find answers:
Technical questions from customers, answered by Radiocrafts' support engineers, about Tinymesh mesh networking.
No questions match your filter.
01Do you have any field experience about wave propagation in mining?
No experience in wave propagation in mining, but generally better range with lower RF frequency and RC Data rate. They should do field test with Radiocrafts demo kit to verify range and system settings.
02Why is Tinymesh only available in a standard Radiocrafts module form factor?
There are many pitfalls in RF hardware design. A good and reliable RF design is time consuming and requires high level experience and expertise. Even though RF transceiver chipsets may require only a limited amount of external circuitry, component selection, PCB layout and antenna matching for optimum performance, are challenging tasks for any design team. Due to the stringent QA / QC procedures applied to the production of the Radiocrafts RF modules, our customers may rest safely that their end product contains an optimized RF solution. Radiocrafts modules come fully 100% tested from factory, including verification of RF frequency stability; TX output power and input sensitivity.
03What is TinyMesh?
Tinymesh™ is a powerful and comprehensive wireless mesh network infrastructure solution with two main components; the Tinymesh™ Protocol Stack – embedded in Tinymesh™ Modules that go inside the devices you want to connect, and Tinymesh™ Cloud Service - a suite of data handling and internet tools to control your connected devices.
04What is the Tinymesh Cloud service?
The Tinymesh Cloud service enables safe and reliable remote control over the Internet for any local Tinymesh network. The Tinymesh Cloud Service provides an Internet API for application program development, and the Tinymesh Workbench application for systems administration, configuration, prototyping and concept testing.
05What is the maximum communication range for Tinymesh?
Communication range is governed by the laws of physics, where the output power of the radio transmitter, the sensitivity of the receiver and the transmission frequency are the most important parameters. Importantly, it also depends on the environment where the mesh is established; being indoors or outdoors, in urban or rural areas, vegetation etc. The signal attenuation and reflections depends on the environment. In simple terms, range is inversely correlated to communication frequency. In other words, the range is approximately twice as good at 433 MHz, as compared to 865 MHz, and 865 MHz will have a range that is almost three times better than a 2.4 GHz based system.
06What is the latency (delay) per hop using Tinymesh?
The typical delay per hop for packets with full payload contents, with default configuration settings, is approximately 100ms. Due to the mechanisms that handle Listen Before Talk (LBT), handshaking and re-transmission, the time is an average estimate. Time between two payload packets is on average two hop-periods, as a new packet may not be transmitted until the previous packet has travelled some distance from the originating Router. The Tinymesh frame format contains a two byte 'Latency Counter'. The Latency counter is updated at every 100ms interval, when a packet is buffered in a Router or Gateway device. If a packet for any reason should experience a delay in further delivery, due to poor connectivity or high traffic load, the Latency counter may be used by the external application to estimate the correct time for the event that caused the dispatch of the packet from the originating node.
07What is the difference between Tinymesh and other mesh networking stacks?
Tinymesh is an advanced mesh networking stack, utilizing all the familiar mechanisms for failsafe and reliable data delivery, such as automatic network forming, self-healing, encryption and error handling. Tinymesh is not bound to established standards, and has the benefit of being able to rapidly adapt to customer needs and requirements. Tinymesh may be ported to any RF-frequency band, and the RF bitrate and output power may be adjusted to meet customer requirements, country specific regulations, and optimizing range vs bandwidth. Tinymesh is designed and optimized to meet application requirements, from its ability for custom configuration of RF parameters, to the simplified commands for input / output control and device configuration on the fly. Tinymesh caters to the industrial engineering team that is looking for ways to get fast to the market with stable and reliable solutions that require remote control or data collection. The input / output control capabilities, and the simple command structure for configuration and control, enables hardware designs that in a multitude of applications may be implemented without requirement for a local MCU or device application programming.
08What is the data download speed using Tinymesh?
When streaming data from a router to the Gateway device, as when metering data is downloaded from an energy meter, the Router device will continuously receive data on the UART. Data will be transmitted along the established hop-path from the Router to the gateway. At every hop, there will be a short delay for handshaking and re-transmission of the packet. The typical delay per hop for packets with full payload contents, with default configuration settings, is approximately 100ms. Due to the mechanisms that handle Listen Before Talk (LBT), handshaking and re-transmission, the time is an average estimate. Time between two payload packets is on average two hop-periods, as a new packet may not be transmitted until the previous packet has travelled some distance from the originating Router. This means the maximum download speed is going to be approximately 200ms (three hops) per packet. With a maximum payload size of 120 bytes, the typical download speed will be 120/0.2 = 600 bytes/second (4800 bps). Except when downloading from a Router device that is linked directly to the Gateway device, number of hops will have little effect on download time. Routers that connect directly to the Gateway will however have shorter download time, as the packets are only travelling a single hop and are not redistributed after the first hop. Given above conditions, a typical download time for 2kbytes of data will be 1024*2/ 600 = 3.4 seconds when data is hopping in a network with reliable connections. For connections directly to a Gateway device, the download speed will be closer to 1k Bytes/second. For networks with poor connectivity, download times may be longer, due to retransmissions of packets.
09What is the advantage of a mesh network with respect to radio range and reliability?
The basis of mesh networking involves self-forming, redundant communication paths and self-healing. A mesh network gets stronger and more robust by any additional node that is included in the network. Each node will add new optional routing paths for safe connectivity and reliable data communication in changing environments.
10What is the ‘RSSI Acceptance Level’ configuration parameter?
The 'RSSI Acceptance Level' configuration parameter is the minimum signal strength that will be use when the mesh network finds a new path. It may be changed, to allow Router modules to be less selective in their choice of connections. The default setting is 190 (- 95dBm), meaning that a device that is received with a lesser signal strength will not be accepted as a reliable mesh connection. By increasing the parameter value (reducing the dBm value), the module will accept an invitation to connect from a device with lesser signal strength, as long as the invitation packet is correctly received and without errors.
11What is “link budget” of a Tinymesh module?
The 'link budget' is the difference in dB between your receiver sensitivity and the output of your transmitter, including the loss and/ or gain of your antenna. A low power Tinymesh module has a maximum output power of 10dBm, and an RX sensitivity of -99 dBm at the default RF bitrate for the sub- 1GHz modules, giving a total theoretical link budget of 109 dB. High power modules (27 dBm) will add 17 dB to your link budget for sub- 1GHz modules, for a total link budget of 126 dB at the default 76.8kbps bitrate.
12What can I do if the range between two Tinymesh nodes is not sufficient?
The first thing to do is to make sure the antenna is correctly designed and connected. Is the module and PCB layout correctly designed per the module datasheet? Special attention must be paid to proper ground plane and connection to the antenna. The antenna should not be placed inside a metal cabinet, and even a plastic cabinet can de-tune the antenna. Secondly, consider the power supply for the module. The power supply for the module must be designed to provide full power without voltage drop during the RF transmission peaks. This caution applies especially for the High Power modules which will require > 500mA peak during transmission. The transmitted RF signal will be distorted and not possible to receive if the supply voltage is unstable during transmission. When testing with battery driven demo boards, it is important to assure that the batteries in use are fresh and able to deliver sufficient peak power without dropping the voltage. Thirdly, the range can be increased by switching from the non-HP variant to the HP variant (if local regulations allow this). Finally, using lower data rate, or switch to t a narrowband module will improve the sensitivity and hence the range as well.
13What are the main value propositions of the Radiocrafts module with Tinymesh protocol?
Briefly, the main value propositions of the Radiocrafts module with Tinymesh protocol are:
-Shortened development time, no RF design required
-Lower design cost, no special RF design competence required
-Lower production and logistics cost. Single, pre-tested module vs chip and discrete components
-Lower production QC costs. RF-design is pre- tested
-Higher production yield. No fall-out due to critical failures in RF-design
-Shorter time to market
14What application layers are supported by Tinymesh?
The Tinymesh protocol is transparent to application data, and can therefore be used together with a range of application layers, such as M-Bus (EN13757-3), DLMS and other. It is also possible to use your own manufacturer specific application layer.
15We need to power end device from 3xAAA cell (4.5V). The maximum pulse current of RC1180HP-TM is 560mA. In this case we need to use LDO for such current and their Iq are big. Do you have any recommendations how to solve this. In this application we have no external processor, we would like to use only inbuilt features of the Radiocrafts.
4.5V is clearly too high, and you need a regulator. We do not have experience with such high current regulators with low Iq; but you could ask suppliers like Texas Instruments (they took over National Semiconductor).
16We need to burst data so that they can go back to sleep as soon as possible. If my payload is 10bytes and RF set for max range, what is the time it will take to burst to the gateway on a 15hop network and then receive the ACK before it can sleep again?
"Approximately 4-5 seconds under normal load conditions (Calculate 150ms per hop both directions as average figures using default settings for RF bitrate).
A 15 hop network may however not be optimum. Tinymesh networks allow you to introduce multiple gateways in the same network, for redundancy and load sharing. When multiple gateways are deployed, all data packets will be routed to the nearest gateway for fastest possible delivery to an external server.
'"
17We have to used Radiocraft tinymesh product such as RC1170/71HP-TM for street light application, Question : How to update SID after deployment for same sid for Gateway device? Our requirement is to update the RF parameter such as SID,UID,Device type and other parameter first time or after filed deployment. according to your configuration in OTA update, we are able to set first time and after deploymnet configuration for only Router device . we are not able to read Get status and configure Gateway device after deployment from over the air through RF device. Please tell proper suggestion, how to update Gateway device Configure SID from over the Air through other Rf same Gateway device.
The gateway is always connected to a network and the assumed process is:
- From the gateway/cloud.
o Change the system ID for all devices in network
- The change the System ID for the gateway itself through the ‘M’ command.
Note that the gateway must always be the source for that SET-CONFIGURATION.
18We are planning to power the device directly from 13Ah (or more) primary battery. Its nominal voltage in 3,6V (and open circuit 3.67V). Proposed type of the radiocrafts is RC1701HP-TM / RC1180HP-TM. The absolute maximum ratings of the RC are 3.9V. So I suppose there will be no problem?
RC1701HP operating range is 2.8 - 3.6 and absolute max is 3.8V, so this one should be fine.
The RC1180HP-TM operating range is 2.8 - 3.3 and absolute max is 3.6V, so this one is a bit more tricky. It "may" work at the slightly higher voltages, but we cannot make a guarantee, as this specification is based on the ratings given by the semiconductor suppliers.
19We are looking for ready to use and certified module on 868MHz band with embedded mesh stack
"The RC1180TM or RC1180HP-TM are the correct products for you (Europe CE)
The different is range and pricing. RC1180HP have up to 500 mW output power and can reach several km line-of-sight"
20Sometimes the allowed transmitting time is 10%. Is it handled by module’s FW or should it be handled by the external application.
| Pls check data sheet; https://radiocrafts.com/uploads/rcxxxx%28hp%29-tm_data_sheet_1_42.pdf page 35. It depends on what triggered the wake-up and if the end device can connect to the same router as before it went to sleep. The wake up time itself is in the range of microseconds. The wake up time depends of course on how much data the module shall send when its awake. |
21some breaks in data tranfer which can take up to 0,5 second. Transmition of 8kB file takes 10 minutes. Are you able to help somehow and recommend settings to speed I up?
| Place modules 10m apart (not closer, not too far so that link is unstable). Monitor CTS on a byte-vise basis at both GW and Router. This is a must. Then try again. |
22Ping of life – what is the best way to do this
Ping of life is an automatic function in the Tinymesh node, and does not require polling
23page 8 in the data-sheet lists HW and FW versions with 2 bytes length, but the corresponding config bytes are 4 bytes long. How are these values comparable?
| The config bytes are ASCII coded, while the packet data is binary |
24Our question is when the RSSI level is updated in case of End Device operation. It is quite unconvienent to satisfy only with the first RSSI during ED’s powerup. Basically when the ED will move around or the RF environment will change how we will know it without restarting the ED’s node.
I'm afraid this is how it works. As the end device does not continuously receive data or beacons from its destination node, and hence is unable to update the received signal strength value. For an end device the reported Origin RSSI is the signal strength detected when the End Device first made connection to it's destination node.
25One question for RC End device mode. We need to sense two edges of a limit switch. This limit switch has pushpull output and we would like to use sleeping radiocraft tinymesh without external uC. Is it possible to switch off internal pull up at GpIo and wake up on both edges to transmit message automatically?
Unfortunately there is no option to turn off the pullups when used as GPIO.
26Is there a way to see the hop path in the Tinymesh network?
Yes, you may use the Get Path Command. Refer to the Data Sheet for details.
27Is source code available for Tinymesh?
No, we do not provide the source code for Tinymesh protocol.
28Is it possible to use the system IDs to spread the network load, but terminate all Gateways to 1 server?
| Yes, you can manually spread the network to different gateways by using different system ID. IF you however use same system ID with multiple gateways, the network itself will reform the network automatically to spread the traffic to closest gateway to minimize network traffic. |
29Is it possible to configure the Routers in a Tinymesh network over the air?
Yes, the Routers in Packet mode can be remotely configured from the Gateway. Refer to the Data Sheet for “Over the air configuration”.
30In the recent datasheets I’ve seen (HP) TINY MESH modules. At some locations it’s likely that we’d install distant routers, i.e. in an apartment say the concentrator is at the 8-9thth floor and the router is at the basement. Can HP module be an answer for this? Or is it only a cure for long distance line of sight applications?
"The RC1180HP-TM will increase range by 15 dB improved link budget. Line of sight this is almost 6 times increased range, but in a building then a concrete floor might introduce 15 dB extra attenuation, so that
it might still not reach 8-9 floors, it heavily depends on the building construction.
"
31In the datasheet it says RTS signal may block the GWAY if held high too long. How long is that duration?
"If RTS is held high by the host, to signal unavailability, the Gateway module will stop sending invite-beacons ( HIAM packets) to the mesh network, and the Gateway will ignore packets that are being received from Router nodes by refraining from sending 'Acknowledge' packets.
- If the 'Connect Check' time of the router modules are set to the default value of 4 seconds, the mesh will start disconnecting after 4 seconds of inactivity from the Gateway.
- If a Router module attempts sending a packet to the Gateway, and receives no 'Acknowledge' packet in return, it will retry packet transmission 25 times (default setting), before disconnecting.
Avearge time between retransmits will be approximately 100ms, for a total of 2.5 seconds before disconnect.
Note: The packet will not be lost, but held by the Router device until a valid connection has been reestablished.
"
32I saw that the tinymesh modules support a range of frequencies (~15). Are these fixed (i.e. static) frequencies? Or the mesh protocol is able to hop between them?
The frequencies in TinyMesh are static in the way that it has to be chosen by the startup of each network, normally based on a channel scan showing which channel has least interference.
33I need an information about RC1160-TM module. I want to know if is possible to configure the module as a “repeater” of the input GPIO pin: fox example the change level of the a digital input pin of the transmitter, causes the same change in in the same pin (digital output) of the receiver.
"Each Repeater has configurable I/O-pins. The control and monitoring of those can be controlled from the Gateway, via UART. It is not possible to achieve toggling of pins at one Router causing toggling of a
similar pin in the “other end”; This can be achieved, though, via a small extern microcontroller reading the UART data and converting the readings to I/O control.
"
34I have a query regarding the tiny mesh 868MHz module. Due to the restricted dimensions of the enclosure we would like to use the radiocrafts module in, is it possible to orientate the antennas of the gateway and routers in the network horizontally? Ideally to minimize system cost, would having a length of wire (at the 1/4 wavelength of 868MHz) soldered to the RF o/p of the module which would be perpendicular to the PCB give good range?
"A quarter-wave length wire, approximately 80 mm, will work very well as an antenna and the radiation minor affected if you place it parallel with the PCB, as long as you keep the distance to ground > 10 mm. If this is not possible in the design, keep at least the tip (last 4 cm of the wire) as far as possible from ground cause this is the most sensitive part of the antenna.
We have seen PCB designs where the antenna is routed parallel to the GND plane but with distance around 10 mm to ground, and range is close to the same as our demo board, which is close to optimum for a board with the antenna mounted on one side of the board (optimum would be a circular board of radius > 80 mm with the antenna in the middle).
So connecting a wire directly to the RF-pin of the module, and having a GND-plane in the PCB as big as possible (the bigger the better radiation), and grounding the modules’ GND-pins (directly) to this plane, will give you a good radiation, close to what is optimum. The orientation of the antenna (vertical or horizontal) is only possible to detect when the RX and TX antennas are close (near-field effects). when they are in some 20-30m distance the reflections are so many so that the orientation does not change the RSSI (received signal strength) value. In theory, there are no connection if you place two antennas with the tip pointing towards each other but this is also not possible to see in the far-field (long distance). Which is good as it gives more flexibility during installation
Also keep the tip of the antenna away from plastic (some mm) as the plastic will also de-tune the antenna slightly.
"
35I am currently developing a new product using your RC1180HP-TM module and after scanning the entire datasheet, I couldn’t find specific information regarding some RF parameters, namely: modulation, bandwith and frequency deviation. I have configured the module to operate in channel 13 at full power and data rate of 76.8kbit/s.
| Data rate (kbaud) Deviation (kHz) RX BW (kHz) 1,2 5,2 58 4,8 25,4 100 19,2 19 100 32,768 50 232 76,8 32 232 100 47 325 250 127 540 |
36I also would like to get more information about TinyMesh performance. Could you provide a comparison between TinyMesh and ZigBee Pro?
"ZigBee is mainly at 2.4 GHz, which has reduced range compared to sub 1 GHz operation. ZigBee requires some basic skills if you want to interoperate with other equipment which makes it more time-consuming with respect
to development time.
TinyMesh is up to 255 hops and has 4 bytes addressing, the number of nodes are “unlimited” and the time-to-market reduced compared to ZigBee. TM is available at all frequencies, also sub 1 GHz, and has all the features of ZigBee with
respect to LBT, acknowledge on each hop, re-tries and self forming and self healing of the network.
If interoperation is not an issue for you, TinyMesh will give the shortest time to a working solution"
37HP moduleas communicate with LP modules onlty when AES is not used
| HP modules always communicate with LP modules but it is not recommended to do so, cause range will be like with non-HP modules (as it is ack and re-transmissions, so the link must be symmetric) |
38How many nodes can it be in a Tinymesh network?
The maximum number of nodes depends on the usage; how often transmissions are done, how many bytes and the data rate (channel occupancy). In general a network of few hundred nodes is possible if the data throughput is low. Another way to increase the number of nodes is to do polling from the gateway.
39How does the @TM command work for a Tinymesh module?
The @TM command will reset the configuration parameter setting to factory defaults. However, the AES key is retained. But the Unique ID and System ID will be reset.
40How can we save battery power using Tinymesh?
The Tinymesh module can be set to Sleep mode to reduce the current consumption. But do note that in Sleep mode the node are not able to be a part of the mesh network. The node can also be configured as End Device. Also, the End Device does not take part in the mesh networking; it will only talk to its parent when waking up polling for data.
41How can the Tinymesh module be woken up from Sleep mode?
The Tinymesh module can be set to Sleep mode and woken up from Sleep mode using the RTS/Sleep pin. But this functionality has to be enabled in the Configuration memory (setting address 93 to 1).
42How can I use Tinymesh with pulse counter?
For pulse counter see page 36-37 in the Data Sheet. You can setup the IMA message to be sent regularly based on a timer (Configuration address 85) and you can set the IMA message to include the Pulse counter bytes (Configuration address 106).
43How can I improve the robustness of the communication links in Tinymesh?
You may adjust 3 parameters:
RSSI_ACCEPTANCE_LEVEL @ addr. 4: increase the RSSI level in dBm. This will avoid creating a very poor link which leads to the reconfiguration.
CONNECT_CHECK_TIME @ addr. 8: increase the time, so the system will less often reinitiate itself.
CONNECTION_CHANGE_MARGIN @ addr. 98: increase the margin.
44For debugging can I use a GW with the same DeviceID as our servers GW. (Both 0.0.0.1) most of the time, so both GWs get all data packets.
| In general, having 2 devices within the same network having same UIDs will cause unpredictibale behavior and shall not ever happen, neither during testing and definitely not during any installations. |
45For compliance testing, does Tinymesh provide a test mode with “continuous transmission with 100% duty cycle?
Yes, both test mode 1 and 2 provide continuous transmission. Test mode 1 use un-modulated carrier, while test mode 2 use a modulated carrier (using a PN9 random sequence for the data stream). The RF_DATA_RATE setting also apply in the test mode.
46Does Tinymesh support multiple gateways?
| Tinymesh supports multiple gateways. They must of course have different UIDs, all devices must have different UIDs. And the packages might arrive at different GWs at different times, as this is how the network is optimized. |
47Does Tinymesh support more than one gateway?
Yes, more than one gateway can be used to create redundancy in the system so it does not have one single point of failure. One of the great features of TinyMesh is the ability to distribute traffic between to gateways in the same network. And it 1 gateway dies, all traffic will automatically be routed to the other.
48Does Tinymesh support encryption, and can I have a DLL to decrypt the messages?
The Tinymesh modules supports encryption using AES-128. The encryption and decryption is handled internally by the module. We do not provide DLLs for decryption.
49Does the RF bitrate of the Tinymesh module affect the RF sensitivity, and hence the range?
The 'RF Bitrate' parameter may be reduced, to increase the RF sensitivity of the device. But the effect of modifying the RF bitrate is not dramatic, and will slow down the data throughput in the system. An improvement in the link budget of 5dB may be expected by reducing the RF Bitrate to 19 kbps. Please note that the 'RSSI Acceptance Level' parameter should also be changed when 'RF Bitrate' is changed, to allow the module to utilize the improved sensitivity of the radio.
50Do you provide Tinymesh on CC13xx family from Texas Instruments?
No, we currently do not provide Tinymesh on CC13xx.
51do you have any application that you know that someone used this Mesh to transfer Audio?
"- Analogue audio cannot be used directly with the module
- you must use a codec and digitize the audio and enter on the serial interface
- I am not sure if somebody has successfully implemented Analogue audio in a mesh network"
52data needs to be received without delay
Latency is typically in the range of fractions of a second.
53CTS pin is recommended to be observed before UART is driven on a byte by byte basis in tinymesh documents. Some other paragraph tells as if it is unnecessary and only two pins are enough. How critical is that issue?
"The communication will work without monitoring CTS, but in order to achieve minimum packet loss it is recommended to monitor CTS so your host MCU will be notified (and stop UART data) when the module (either Router
or Gateway) is busy doing transmissions (in a mesh network) or doing network maintenance, which is happening on a regular basis (automatically, to decide the optimum network configuration at any time)
"
54Certain data is priority, how can I quickly stop a busy network of nodes sending other data to stop while I poll for the important alarm data every 5 secs?
Polling is generally not a recommended communication strategy, as the poll packets will take up valuable bandwidth. Unless you have system constraints we are not aware of, I would strongly recommend a regime of automatically generated I'm Alive messages from the network devices.
55Can we use the Rc1780HP-TM and the RC1180HP-TM itogether
| The RC1780HP-TM does not connect with RC1180HP-TM of any revision - the RF link is different |
56can we mix HP modules with normal modules in a network?
HP- and non-HP modules should not be mixed in a TinyMesh network, cause the mesh-forming will be “wrong” (its a bit complex explanation to this)
57Can we add an external Power Amplifier to the Tinymesh module to increase the transmission power?
As long as the local radio regulations allow higher output power, and external power amplifier can be used together with RC17x0HP-TM. Pin 37 can be used to control the external PA (high when transmitting). Any CE marking or FCC certification is void when using an external PA, and a new compliance test must be done for the complete system.
58Can I use directive antennas to improve range for Tinymesh?
There are high-gain antennas available that may improve the link budget. But directive antennas should be avoided, as they may not work well for making alternate connections (redundant connection) in situations where the primary connection should fail. High gain antennas should be omni-directional. Collinear antennas may be an option, as they provide same performance in all directions.
59Btw do you have any field experience about wave propagation in mining.
| No experience in wave propagation in mining, but generally better range with lower RF frequency and RC Data rate. They should do field test with Radiocrafts demo kit to verify range and system settings. |
60Are the GPIO pins of the Tinymesh module available on the Development Board?
The schematics for the Development Board were made before the TinyMesh module existed. So the push-button on those boards does not necessarily fit with the GPIO pin of RC11xxTM module. But all GPIO is available on the connector pin holes.
61AES 128 bit in RC1180 (low power) works only without password
| There is a default encryption key in the FW. It can be changed. Encryption is enabled/disabled (configurable), and when enabled at both source-Router and GW, plain text will come through |
62About compatibility of the high power and lower power nodes. Please can you explain in more detail what problems I may encounter with the 2 types, as I only see that I will loose the ACK which your data sheet explains as being present on each hop?
The TM protocol support configurable retries if you lose ACK. If selecting the option not using ACK, you also disable this feature for the network to ensure link completed with success by using retries.
63a proof of life is required regularly.
Any device may be set to periodically send 'I'm Alive' packets. Time between dispatch is configurable.
64A poll revolution of 5min or better is required.
The system is based on CSMA /CA network access, and does not require polling. Devices will transmit when there is data to transmit. The CSMA /CA mechanism handles collisions and re-transmission.
65We want a RC1740TM-DK but I doesn’t found this article in your price list. On your web side stand >>> contact Radiocrafts” – what does this imply?
| We do not have non HP demo kits in the RC17xx(HP)-series. The customer can perform test with HP demo kit. |
66We have to develop a system that it can to locate people. I have thought to use RC tiny mesh using the RSSI level, but I would need to know what router I am connected and the RSSI of that router (not all the net). Is that possible?
"There are several options for you to identify the path of each received packet in a Tinymesh network (packet mode only);
- in packet mode, the path is identified in the packet header upon reception of a sent packet
- Or you can ask the Router “Get_Path” commando to a Router, and it will respond back with its connectivity to the Gateway
- Alternatively, you can enable the Locator function in Tinymesh, and it might be the most useful one;
With locator function, you can identify the closest Router to any moving device in the network, and it will give you an approximate location.
You must set the I am alive packet to be sent on a regular basis as the moving node moves through the network. By default, this parameter is set to “never”.
"
67We have a doubt about the connections dynamic and network architecture. Consider the image below: 1 – Gateway, Router and End device ar configured with the same RF Power 2 – Gateway signal can reach directly to End Device 3 – Router can reach to Gateway and End Device 4 – The End Device only can reach the Router when transmitting, but receive the signal from Gateway directly Although the end device can receive the signal from the Gateway (above RSSI acceptance level), once the End Device can’t reach the Gateway directly, the connection is never established and the second way through Router is never choosed. The tiny mesh algorithm favors the shortly way to gateway if the rssi level is above acceptance level. If the end device receive the signal from Gateway above acceptance level, but is not able to reach the gateway directly, even if we have a router between Gateway and End Device the connection is never establish. Do you have any explanation to this behavior and a way to improve and avoid this kind of scenario?
"Up- and downstream transmission in the network follows two different principles:
1. On transmitting from a Gateway, the receiving device is allowed to receive and act on a packet that is received with valid CRC regardless of whether the packet is received from the Gateway device directly, or if received from the router device that is the normal transmission path.
2. On transmitting to the Gateway, the path is determined and may not be circumvented.
As a consequence of above, you may sometimes observe the below pattern. The Gateway is able to communicate directly to an end device / router, whereas the communication in the opposite direction always goes through an intermediate router.
The RSSI acceptance level controls the minimum signal strength required to create a link in the network. By increasing this level, you will increase the likelihood that a Router will connect on fewer hops / connect directly to the Gateway. On the negative side, this will tend to reduce network stability.
By setting the End device to transmit in 'walk by' mode, the End Device will not utilize the normal hop path, as it will not be expecting an ack from the receiving node. In this mode, you will probably experience that in most cases, the End Device packets will directly reach the Gateway device in both communication directions ( up- and downstream)
"
68How can I understand, when the CTS goes low, if the data have been delivered or not? If you have an alternative way to understand if the data have been delivered or not, please let me know (data going from the routers to the gateway).
"CTS goes low after a link level ACK has successfully been received from the next (link) level in the mesh (whether this being a Router or a Gateway), and is a positive acknowledge that the data in the buffer has safely been delivered to the next level of the mesh.
If no ack is received after depleting the configured number of retries, the router will attempt a new connection and continue trying to deliver the data until successful.
CTS will stay high until data has been successfully delivered to the next receiver. If the Max Packet Latency time has expired before the packet reaches the gateway, the packet will be discarded.
There is no end-to-end acknowledge when transmitting from a Router to a Gateway. If such function is required, it must be implemented by the external host, as e.g. a 'Serial Out' packet that is transmitted from the Gateway to the Router in question.
"
69How can I understand, when the CTS goes low, if the data have been delivered or not? If you have an alternative way to understand if the data have been delivered or not, please let me know (data going from the routers to the gateway).
"CTS goes low after a link level ACK has successfully been received from the next (link) level in the mesh (whether this being a Router or a Gateway), and is a positive acknowledge that the data in the buffer has safely been delivered to the next level of the mesh.
If no ack is received after depleting the configured number of retries, the router will attempt a new connection and continue trying to deliver the data until successful.
CTS will stay high until data has been successfully delivered to the next receiver. If the Max Packet Latency time has expired before the packet reaches the gateway, the packet will be discarded.
There is no end-to-end acknowledge when transmitting from a Router to a Gateway. If such function is required, it must be implemented by the external host, as e.g. a 'Serial Out' packet that is transmitted from the Gateway to the Router in question.
"
70- Are all RC2500(HP)-TM compatible to each other? – Is there a combination of RC2500(HP)-TM which cannot communicate with each other?
| Do not mix HP and non-HP in same network, it will work but the mesh-will be assymetcial on each hop if there is one HP trying to connect to a non-HP and vice versa (the hop must be symmetrical). |
71[TINYMESH “We would like to make application when one measured parameter (I.e Tempearture) will be transferred in 11 floor building to basement where GSM concentrator is installed. Measuring device should transmit every 15 minutes and need to live on battery minimum 3 years.
| Range: 11 floors in one hop is challenging. It depends on if the RF can travel in the stairs or through windows, its hard to tell. Power; Assuming sleep < 1 uA, and TX around 500mA peak, packet length 50ms, then average current consumption is 500mA * 50ms/60*1000*15ms= 28 uA average. So one 16Ah battery will last: 16/28uA=571k hours = maaany years. |
72Can the END point transmit data at any moment after wake up by external trigger (i.e GPIO), can END point initialize communication?
Yes - this is the default behaviour of an End Device.
When waking up from internal IMA timer, external GPIO, or serial data input, the device will first dispatch a packet as dictated by the trigger condition, then return to sleep.