Wireless M-Bus Q&A
Enter your keywords to find answers:
Technical questions from customers, answered by Radiocrafts' support engineers, about Wireless M-Bus modules.
No questions match your filter.
01Does the Zigbee module such as RC2400-ZNM have the same footprint as the OMS \RC1180-MBUS3? If yes, is our OMS board could be used also for the Zigbee module?
The footprint / size is the same, but please see the detailed pinout in the datasheets for the two modules. For example, the ZNM module may also use SPI which is not available on the MBUS3 module.
02regarding the M-Bus packet frame, there are two fields named C-field and CI-field, for which I could not find explanation from Radio Crafts M-Bus user manual. Please send us the details of the documents explaining C and CI fields.
"In order to understand the details about the packet format to be OMS and wireless MBUS complient using the MBUS3 modules you need the OMS specification.
http://www.oms-group.org/en_downloads.html
This specification informs about the C and CI field and also gives you some packet format exsamples in the appendix.
"
03The W MBus network will contain repeaters to transmit data from 868 MHz to 169 MHz. We want repeaters in Battery operated mode. 1. We plan to put Repeaters in long sleep mode and arrival of packet from nodes would wake Repeater. This design would be similar to Data collector/Concentrator design envisaged in Wireless M Bus specs. Alternatively we can design time synchronized wake-up algorithm so that all nodes wake up at the same time (including repeater) and after data transmission, all nodes go back to sleep mode. What would you recommend?
The MBUS3 module from Radiocrafts supports one way repeater functionality according the OMS. The repeater must be active all time to comply with OMS and battery power repeaters (sleeping repeater) is not part of the wireless standard yet. There are working tasks in the standardization group to include two way repeater functionality and even sleeping slaves, but for now only one way solution is supported by the standard. The Radiocrafts modules (MBUS and RC232) do however support sleep mode and wake-up commands, and you can as you suggest implement your own proprietary synchronized wake-up algorithm if needed. You cannot wake up a sleeping module by RF signal so the first approach is not possible.
04We have a board for Wireless M-Bus which is connected one of the UARTs at the Arm Cortex A5 which we are using. Now we have had some units which have stopped working. We got one to the office last week and this one seems not work at all. We could not send the configuration commands etc.
If devices work at startup, but after a while all UART ocmmunication stop to function, then our first suspision is always that customer has un-intended entered config mode and changed configuration.
05would it be possible for us to know what modulation technique does rc1180-MBUS use?
| The RC1180-MBUS modules use FSK modulation according to the wireless M-Bus standard (EN13757-4). |
06Why is the RC1180-MBUS3 module sending «=» (or 0x3D) on the TXD line?
This is a special interface protocol that have been (accidently) activated. Please check the DATA_INTERFACE parameter (at address 0x36). It may be an indication of the configuration memory has been corrupted when using the “M”command. Please ensure the re-configuration command is completed (prompt on TXD) before removing supply power or resetting the module.
07Which Wireless M-Bus modes are supported?
MBUS3 support S1, S2, T1, T2, C1 modes. MBUS4 supports N1 and N2. The mode is set by configuration register 0x03 (MBUS_MODE). Also note that the module can be configured for receiving T and C mode in parallel, that is, the module will detect the mode and decode the message accordingly.
08Which module should I use for Russia?
RC1160-MBUS3 and RC1160-MPC1 is made for compliance with Russian regulations.
09Which module should I use for India?
RC1170-MBUS3 and RC1170-MPC1 is made for compliance with Indian regulations.
10Which module should I use for Brazil and other countries outside Europe using 433 MHz?
RC1140-MBUS3 and RC1140-MPC1 is made for compliance with Brazilian regulations. It can also be used in other countries where 433 MHz is a license free band, such as in the Middle East, Australia/NZ, and some African countries.
11Which module should I use for a meter with pulse output?
If your meter provides a pulse interface, you may use the MPC1 module. This is an M-Bus Pulse Counter application that does the pulse counting, data management, and transmission scheduling. Up to two pulse inputs and a tamper signal can be used, in addition to temperature and battery voltage monitoring. It is possible to configure how often the module will do an RF transmission. The MPC1 can be configured over the air.
12Which mode is recommended to use?
The mode to use depends on the desired system solution. For water and gas meters often deployed in pits or basements, mode N is preferred due to the long range. For shorter distance (in house/building), walk-by or drive-by systems mode T and C is preferred.
13Which mode is recommended for lowest current consumption?
All modes support battery operated devices. Even mode N using high power (500 mW) at 169 MHz can be used for smart meters with 15-20 years battery lifetime, as the number of transmissions per day is normally limited to less than 10. In drive-by or walk-by systems where transmissions are much more frequent we recommend to use mode T or mode C. The mode C use NRZ coding, and with frame format B, it will give the shortest transmissions and hence the lowest power consumption. You may also use the AES-128-CTR mode and compact frame format to further reduce the application layer data.
14What kind of encryption is supported in the Wireless M-Bus modules?
Currently the transport layer mode 5 (AES-128-CBC) and extended link layer encryption mode 1 (AES-128-CTR) is supported. New encryption modes are added as the Wireless M-Bus standard develops.
15What kind of CSMA algorithm your module uses? We are worried about compatibility with a 802.15.4 network which should coexist with your module (MBUS3). Will the module detect traffic on the same frequency, and avoid sending at the same time when other two devices communicate? We are not sure about vice-versa also, and we use Atmel at86212 CHIP, on 868 Mhz. (868.3 Mhz, BPSK 20 kbps)
The Wireless M-Bus standard does not apply any CSMA algorithm. The Multical21 is a pure transmitter using C mode, like “transmit and pray”. But it transmit very often, so the probabilty is still very high to receive it, because of the limited duty cycle of the transmitters. The RC1180-MBUS3 can be jammed by strong transmitters at same frequency using 802.15.4, but the module will not receive or decode such data as the preamble and synchronisation word is different. The frequency you mention is same as wMBus mode S, and the concentrator to meter communication for mode T2. But mode T/C from meter is 868.95 MHz, so there will not be a direct collision.
16What kind of antenna can I use with Wireless M-Bus?
The antenna is usually integrated into the plastic casing of the meter. The best size and shape depend on each application. The Radiocrafts support team can advise on the best solution from in each case.
17What is Wireless M-Bus?
Wireless M-Bus is a European Norm for utility meter communication. It is standardized in EN13757-4. It is widely used for electricity, gas, water, heat meters and heat cost allocators. It also supports other types of environmental sensors.
18What is the standard output power of the module? Can they increase the output power ? How
"If they have the HP variant, as marked on the top of the module, it is 27 dBm / 500 mW.
This is the default value from factory.
The output power is configurable, see User Manual for details.
"
19What is the range of Wireless M-Bus?
The range depends on the mode and frequency, and of course the environment where the radio is used. In general low frequency and low data rate gives the longest range. Hence mode N at 169 MHz provides the best range. Line of sight communication range can be more than 5 km. Deployments in urban environment achieve typically 1-2 km. Mode S, T and C at 868 MHz can reach few hundred meters LOS, and typically 50-100 meters in buildings. At 433 MHz the range will be somewhat longer due to the lower frequency.
20What is the difference between MBUS3, MBUS4 and MPC1?
The MBUS3 and MBUS4 protocols act as Wireless M-Bus modems with a UART command and data interface. The MPC1 provides a pulse counter application on top of the Wireless M-Bus protocol and can therefore be used as a complete and autonomous solution for any meter that provides a pulse output.
21What is support for linux driver?
| The interface to the module is standard UART, and Linux supports a UART via any COM-port, like RS232 or USB. In this case an external level-shifter will convert the RS232 or USB to UART. The demo kit comes with FTDI USB-UART chips, and there is USB drivers for Linux available from FTDI |
22What is OMS (Open Metering System)?
OMS is an association of companies using Wireless M-Bus, and has defined a set of specifications for interoperability. Radiocrafts is an active member of the OMS working groups maintaining and developing the standard.
23What is CIG (Committee Italian Gaz)?
CIG defined a national standard for using Wireless M-Bus mode N 169MHz in Italy for gas meters. The RC1701HP-MBUS4 module and protocol by Radiocrafts is compliant to this national standard.
24What I’m searching for is this switch to turn off the transmitted ID of the module. I want to add this MBus-ID within my µP and send it via UART to the module. The reason is, that we probably need to send some MBus T1 pakets with different MBus-IDs.
"To change the ID you can use the 'T' command. This only change the ID used in the TX packet and do not change the setting in the configuration memory.
To change the ID before TX you do the following:
1. send 0x00 and wait for '>' (enter config)
2. send 0x54 and wait for '>' (T command)
3. send 8 byte ID and wait for '>' (T command Argument)
4. send 0x58 (Leave config)
5. Send packet on UART
It is no support for disabling the first header ID n the RF packet.
"
25What happens if there are two MBUS masters in the range of a slave?
If both Masters are configured to accept all messages they will both receiver the same message from the slaves. Note however that the installation feature in RC1180-MBUS2 to bind slaves to a master. If you do this you can change the Master mode to only accept installed slaves. This is described in details in the MBUS User Manual.
26What are the wMbus 169 TX specifications like duty cycle and data rate(s)
"For meter reading application(I assume this is the case) in the 169 MHz band the max duty cycle 10% with max output power of 500 mW.
According to regulation the max channel spacing is 50kHz
Wireless M-Bus @ 169 (mode N) includes 3 data rates.
2.4 kb/s
4.8 kb/s
38.4 kb/s"
27What application layers are supported by Wireless M-Bus?
The Wireless M-Bus standard can be used together with a range of application layers, such as M-Bus (EN13757-3), DLMS and SML. It is also possible to use your own manufacturer specific application layer.
28We want to test MBUS protocol. It´s not for metering. If weuse MBUS protocol , must we follow the protocol for wake up/ sleep?
"If you do not need to follow the OMS system specification they can implement any proprietary wireless solution benefit by using the Wireless MBUS module from Radiocrafts. They are free to use the module as they like, as long as they take into account the regulatory requirements on TX duty cycle. Other than that they can wake up the Module as much as they like and transmit MBUs packets. The 15 min period I mentioned to you was if you follow the OMS, and this period enable 15-20 years battery power metering systems.
The Wireless MBUs is described in en European Norm EN13757:4 (Wireless Meter readout) and EN13757:3 (Application layer). In addition you can download the OMS specification for free
"
29We have an issue with the UART communication
Without RTS/CTS you have the risk of getting out of sync. This must be handled in your hos controller.
Meaning:
If you receive a packet on RF and the host controller start to send on UART in the same timeframe, then module can receive RF, print on UART and then starte listening on the UART port.
This might be in the middle of a UART frame from host controller.
I think the statement that you sometime have to reset module is interesting. I think that could be because you enter config mode in normal packet mode.
If module receive an ‘0x00’ on UART as first byte this might be what happens.
Running a module in config mode and sending packet through UART is a recipe for strange behaviour.
30We are working on the RC1701(HP)-MBUS4. We are using the MBUS packet sniffer in the MBUS Demo application. Is possible to get better resolution of the timestamps in the demo application. Is it possible to get microsecond or millisecond granularity instead of full second?
The timestamp is taken for the system clock of the running PC and not from the Module. Improved resolution is not possible as the application is implemented now. It is related to the USB to Serial driver and inbuilt thread handling in Windows. If time critical resolution is needed you might find other RS232 terminal windows application to fit your need better. Any RS232 terminal window application can be used with our Demo boards.
31We are using RC1180 HP WMbus module. We are using S1 mode and we are considering moving also to T1 mode that the module manage. Can you please confirm that dataframe between S1 & T1 is the same
Dataframe on UART is identical between S mode and T mode.
32The W MBus network will contain repeaters to transmit data from 868 MHz to 169 MHz. We want repeaters in Battery operated mode. Do you have module satisfying our repeater requirement?
The MBUS3 module from Radiocrafts supports one way repeater functionality according the OMS. The repeater must be active all time to comply with OMS and battery power repeaters (sleeping repeater) is not part of the wireless standard yet.
33The MBUS3 or MBUS4 module stopped receiving data and seems to get stuck, what shall I do?
a. The most probable reason is that the module entered Configuration mode. This can happen if the timing of the UART interface is not respected, or data is sent to the module while it is busy, and the module then accidently receives a “0x00” command. To prevent this it is recommended to use the UART handshake signal CTS.
b. It may also be that the Reset pin has been trigged accidently by noise or some other uncontrolled event. Make sure that the Reset pin is connected as shown in the data sheet, using a low impedance driver for the signal.
34Since the user manual aslo states (again at pag. 4) that “When blue data appears, it doesn’t guarantee that this data has been sent over RF, it has been sent into the serial port only, as this depends on the state of the RF module”, I suspect that the RF module can be in different “states”. Is it true? Wich are these states? How can we handle them?
I would recommend to use the MBUS-DEMO in the start instead of MBUS-CCT. Please also ensure that you power the boards using the DC jack. The USB cable is for communication and is not able to provide required power for the transmitter. Also ensure that the boards has Antenna connected and that the boards are separated enough so the receiver is not reaching saturation due to strong signals. A few meter distance should be sufficient.
35Should I purchase the standard wireless Mbus Should I purchase EN13757-4:2005 or EN13757-5?
EN13757-3: Dedicated Application Layer
EN13757-4: Wireless Meter Readout
EN13757-5: Repeater functionality.
The Wireless MBUS module support the EN13757-4. In addition you will find relevant information about the application data frame format in the EN13757-3. EN13757-5 is not relevant as the repeater functionality is implemented as described in OMS specification.
36Say we have 1 central unit with 1 wMBus receiver and another wMBus device with bi-directional communication, can the central unit operate in T2 mode and communicate with both types of end devices?
Yes, the Master / central unit can be T2. It still listens to the same frequency as for T1. But transmissions from the Master are on the “S” frequency, because the Slaves / sensors will listen on the “S” frequency. So you can easily migrate from a one-way to a two-way system.
Using Master in T2, you will need to use the auto messages generation, as the master must send a message in 2-3 ms after it received the messages from the Slave. See the MBUS User Manual for how to use the T2 mode and “auto message generation”.
37it seems that collisions between slaves create sometimes bit errors and the correction in your Errata Note 4 seems to solve it. However we are surprised that because of bit errors are present in a radio frame, this frame is not rejected (wrong checksum for example) and it is still analyzed (and in this case to find a non-supported encryption mode). Why ? Is there a risk to receive a frame from the RC1180 radio module with wrong data due to collisions ?
| The module will reject the packet if the module calculate wrong CRC check sum of a block due to bit errors. The CRC is calculated Block per Block and rejected when the block is received and analyzed in order to perform CRC checksum calculation. The Errata 4 issue is in this block receiving phase already initiated even if CRC checksum gives wrong CRC and the packet is rejected at the end |
38Is there any way to check the reliability of communication ?
| If you enable RSSI append you will get the signal strength of the received packets. This will inform if you have margins to the sensitivity limit. If you place the two boards to close together your receiver will reach saturation due to strong signals from the transmitter. This will give packet losses. Try to use at least one meter between the boards and repeat the test. |
39Is there any other “Trick” that you can explain to me like the existence of the “s” command
"- You use the ‘s’ command in the same way as ‘S’ command. ‘s’ command has faster response since it is instant RSSI, while ‘S’ is adding delays due to averaging and longer measuring time.
"
40Is there any of your MBUS radios that supports repeater functionality?
All the MBUS3 and MBUS4 products are supporting repeater (single-hop) functionality.
41Is there a way to configure the RC1180-MPC1 for half litre pulses? If not can the firmware be updated to have a setting for this?
Half liter pulse is default. This is feasible in a FW change.
42Is the firmware included in module? Are there are any additional cost regarding firmware?
| The embedded firmware fully supports bidirectional wireless communication according to the open standard. No extra license applies. |
43Is it somehow possible to set the 4 Byte DID just like the 1 Byte DID in the volatile memory?
4 byte dressing is supported by the T command if ADDRESS_MODE=8. Note however that the module reply with prompt (>) for each byte you send.
44Is it correct to configure the M field and the A field with the same value for both repeater and concentrator, if not what is the suggested configuration
"All units in a Wireless M-Bus network should have unique address.
M = Manufacturing ID.
A = Serial number
V = Version (revision of product)
T = Type of device (Repater or Concentrator)
In a real deployment CPL need to define their own unique addresses, not use the default address of the module as this could lead to multiple units with same address in the field.
Use different values for Concentrator and Repeater.
"
45In your RC1180-MBUS datasheet, we can see that the frequency tuning can change between 2 channels in mode S and T (868.3 and 868.95MHz). We chose the 868.95MHz for our transceiver and I would like to know for our test after the production what is the frequency tolerance and if there is a frequency calibration.
The frequency accuracy is measured in the production test and the limit is +/-10 ppm. We also have support for initial tolerance adjustment in the production tester, but due to the low initial tolerance of the module we have not used this tolerance calibration feature in the production tester.
46I would like to know what is the exact configuration and settings on the MBUS Demo tool to setup a repeater between a slave and a master?
The repeater must be set in S-mode or T1 mode and it will only repeat SND-NR or SND-IR messages according the OMS. Try to repeat your test in T1 mode and verify that you send and SND-IR or SND-NR. If you still get it to work only in ‘accept all’ mode for the master it may be that you have installed the slave address incorrectly. Check Most significant byte vs Least Significant Byte order for the A-field and M field.
47I would like to ask you, if the 1701HP uses 5V or 3.3V logic level for the I/O’s (CONFIG, RESET, etc.)
Thank you for your interest in our RC1701HP. VCC and VCC_PA use 3.3V as stated in data sheet. In general you should use the same level on your CPU as for the Module in order to connect the I/O without level converters.
48I understood that RC1180 mbus3 is the RF module to attach with the meter to get the meter reading remotely. Can we attach this to all types of meters (existing meters)? Or it requires the meter to be replaced with a new one?
| The module can be retrofit if there is plug in option on the meter. Optionally the module can be designed directly on your existing PCB inside the meter. The module has a UART interface, and we have developed a module with a pulse interface. |
49I sent a OMS telegram (A) to RC1180 and I tried to view data telegram with MBUS Demo Snifer ( MasterMBUSReveive.jpg), but I don’t found any CRC.
The CRC check is done internally inside the module, and you will for this reason not see the CRC un the UART message.
50I need to realise a smart metering network using 169 MHz and WMbus standard. What option do you have?
The RC1170Hp-MBUS4 is a 169 MHz including full Wireless MBUS stack. You configure and communicate using the same UART interface. We have demo kit available to test functionality even without assembly your own PCB.
51I have one development board Wireless M-Bus (RC1140) that we got in 2010. HW version 1.2. I’m pretty sure this is out of date in software revision. Could you please advise latest FW revision and procedure to upgrade?
Please check the FW revision by using the MBUS-CCT tool. Plug it in the USB, connect and read back the configuration. The FW revision shall then be listed. Probably 3.14?
52I have another question, there is a command to use to read the key of one of the installed slaves (set with command 0x4B)?
| For security reason there is no command to read the internal encryption key. |
53I have a question about version protocol. Wet uses the old version of the protocol, is this compatible to the new version?
"The firmware in the module is always backward compatible, so old modules will always talk with new modules. However, new modules have more features which can
be enabled. "
54I am asked to login for the MBUS User manual. Is there anything different about this manual or is it the one we already have ‘Manual Demo MBus’ ? If it is different, could you please forward it to me ?
The MBUS User Manual (described the embedded protocol inside the MBUS module) is different from the MBUS Demo User Manual (Describes the MBUS-DEMO windows application tools to be used in combination with Demo boards).
55Howcan I reset the module?
To factory reset the module from the MBUS CCT select “Load Factory settings” in the file menu. You first need to connect to the module and read back the status of the module in order to factory reset from the menu. An alternative approach to factory reset the module is to send ’@RC’ to the module while CONFIG is low. This will force the module to factory reset itself. I hope this will help you out.
56How many times can I write a KEY to the MPC1
The max write cycles is 1000,
57How many meters (slaves) do the MBUS3 or MBUS4 support?
The MBUS3 module supports 64 slaves to be registered in the module, all with a unique encryption key. The MBUS4 supports 256 slaves to be registered in the module, but more can be supported through the external interface. See the data sheet for details.
58How is TX and RX synced in Wireless MBUS
"The timing for RX after TX in slaves/meters is given in the standard. EN13757-4. And these timings are all handled in the module!
You can wake the module up from sleep to RX, and the master will expect a TX first from slave. This is how the master can know when the 10 ms window is.
This is the reason why wireless M-Bus is built after the principle that the meter/slave always initiate the communication.
Our master have a patented mailbox system. It can store message to different slaves.
In order for the slave to receive these, the slave MUST send a short ""dummy"" message each 10 minutes and the modules will then automatically
transfer the waiting message in master mailbox. The ""dummy"" message from slave is the only way to let the master know the RX-window is open, even if no transmission is .
needed for other purposes."
59How is the RSSI byte value transformed into an attenuation/signal strength value?
The received power can be calculated as this P = - RSSI / 2 [dBm]. RSSI = 0-255
60How do I install a meter using the CCT
| Here is an example on how to install a meter using MBUS-CCT:
Meter Address: Install meter in MBUS-CCT: Reading a installed meter in CCT: |
61How can we define, where a data package (sending out of the module) starts and when does it stops.
"on the air: the preamble defines the start. The end is simply defined based on the length byte sent in the beginning of the messsage.
On the UART (from the module): The first byte is the length byte. Again is defined by this length byte.
"
62How can I save power by setting the module in Sleep mode?
The MBUS3 and MBUS4 modules can be set in Sleep mode by using the “Z” command. It is also possible to configure the module to automatically return to Sleep mode after transmitting data. Another useful feature is that the module can be configured to return to Sleep mode after a timeout, as a power saving safety mechanism. The MPC1 will always return to Sleep mode after the scheduled transmission.
63How can I do two-way communication using Wireless M-Bus?
Wireless M-Bus is optimized for battery supply, therefore the module (Slave in the meter) will only listen for a short period after a transmission. In mode T the listening window is from 2-3 ms after transmission; in mode S it is from 3-50 ms, and for mode N it is a short window afer 100ms or 1.1/2.2 seconds depending on the data rate. The master module must therefore transmit any message to the Slave within a very precise time window. The MBUS3 and MBUS4 modules has built-in support taking care of this timing using a mailbox and an intelligent message generator.
64For RC1180, we need to be sure it is WMBus compatible and have the standard and HP versions. I understand the legal restrictions and we will probably use the standard but need to ensure the hardware is compatible with higher version in case we need to use them?
RC1180-MBUS is not available as HP since the wireless MBUS specification not use the 500 mW sub-band. RC1700 is available in HP and low power and all information is given in the RC1700HP-MBUS data sheet.
65Explain how interference occurs in the license free bands?
Radio regulations allow ALD in the same band as wMB at 169 MHz would use. It is typical for license free bands that applications share the same band. Interference may therefore occur.
As seen from ALD it would mean that they may be disturbed by meter transmissions, but as meters typically transmit for only 100 ms or so, it will not completely block the audio communication, but you will hear a “pop” or silence for a short moment. It can also be mitigated by forward error coding in the audio data stream.
As seen from the metering system, a strong ALD may block the communication for some time (as continuous audio transmission is allowed). This is mitigated in several ways:
-redundancy in the transmissions. Typically the same data packet is transmitted 2-4 times randomly during the day/night
-redundancy of meter data in each transmission. Typically the meter index from previous days (1-2) are sent together with the new index.
-finally, if any missed data (if the channel was blocked for a few days) it is also possible to ask for historical data that has been stored in the meter, when communication is established again.
Together these techniques will increase the likelihood of receiving the metering values at least once to a sufficient level (say 99%), even if several transmissions are blocked/lost.
66Does your device support both AES-CRT and AES-CBC. If it does do I have to make any special setting to choose either of them or will RC1180 automaticly decode the data using the information how to decrypt the packet using the MBUS status-byte?
Yes, the module support both encryption modes and detect mode and decrypt automatically based on the format of the received packet.
67Does the Wireless M-Bus modules support DLMS/COSEM application layer?
| Yes, he MBUS3 and MBUS4 modules do support DLMS/COSEM in the same way as it supports M-Bus application layer. The application layer to be used is signaled by the CI-field. The actual data points in the application layer must be provided by the application controller (external MCU). For example, in the M-Bus application case, the data points are described by DIF/DIFE, VIF/VIFE and the data value. Several datapoints can be sent in one message. |
68Does MBUS3 or MBUS4 support over-the-air FW download (OAD)?
Currently OAD is not supported in the standard products. But a manufacturer specific OAD solution can be provided.
69Does MBUS support repeaters?
Yes, single hop repeaters are supported according to EN13757-5. The module can be configured to be Slave, Master or Repeater. When configured as Repeater it will autonomously repeat messages after 5-25 seconds (random delay to prevent collisions).
70Does any MBUS protocols support multihop?
Our MBUS products do not support multi-hop repeating, and as far as I know, it is not part of the actual standard either.
71Do you erase between every parameter we send in one go during ‘M’ operation or does it depend on where the parameter is located in memory?
To change one byte in the config memory we first need to erase the whole config memory, and then write to all location. This proses is done using M command and changeling one byte or 10 bytes will only initiate one page erase.
72Do our modules implement all the 13757-4 MAC & PHY features including all modes ?
| The RC1180-MBUS includes MAC & PHY layer.
Application layer is included, customer only need a external MCU to control his system. Module generate the full WL M-Bus packets to be sent over the air. Temperature and some other features can be included also inside the module. Everything according to the 13757-4 is taken care of by the module. |
73Do modules support two way communication in T2 mode
Yes
74Do modules support AES 128 – I assume yes
Yes
75Do MBUS3 and MBUS4 support multi-hop repeaters?
No, multi-hop repeaters are currently not supported. Using MBUS4 at 169 MHz repeaters can in general be avoided due to the long range of the narrow band radio.
76could you see a problem in module sensitivity without power on VCC_PA Pin?
| You can leave the VCC_PA unconnected if you only run the module in RX mode without any sensitivity degradation. |
77Could you provide some information about “Mode C” on RC1180-MBUS3 if it’s actually supported.
| RC1180-MBUS3, as well as RC1140-MBUS3 (433 MHz for some markets), supports C-mode;C-mode can be configured together with T1 or T2-mode, as the module then will receive meters with any mode C- or T. |
78Can you provide the EN13757 standard documents?
No, the standard documents (EN13757-3, -4 and -5) can be purchased as a personal/company copy from CEN or your local standardization body (such as DIN, BSI, AFNORetc).
79Can MBUS3, MBUS4 or MPC1 be configured over the air?
MBUS3 and MBUS4 cannot be configured over the air. MPC1 supports configuration over the air, provided it has been enabled in the module. In this case, when the module CONFIG pin is activated, the module will transmit the current configuration setup. A response to this message will reconfigure the module with the new settings provided.
80Can I use Wireless M-Bus outside Europe?
Yes, Wireless M-Bus is also being used more and more outside Europe, even if it originally is a European standard. It was developed to be compliant with the license free bands in Europe at 868 MHz and 169 MHz. The OMS group has later defined new operating frequencies in order to comply with local frequency regulations about the world. For example is the OMS specification covering Russia (868 MHz), India (865 MHz), Australia, New Zealand, Brazil, Middle East (433 MHz). There are also some proprietary implementations on 915 and 923 MHz for USA, Mexico and Australia.
81Can I buy MBUS1 or MBUS2 modules?
No, these are obsolete and replaced by MBUS3.
82As far as the data format is concerned, the “”MBUS-CCT user manual”” states: “”To send ASCII characters, type them in and hit the enter key or click on the send once button””. In case bytes have to be sent, we know that te first byte should be the Length byte. We tried to transmit the same bytes sequence shown as an example in the user manual (pag. 4): ‘5 0x33 0x25 6 78 7’. In both cases (ASCII and bytes transmission) nothing is transmitted across the link (or at least nothing appears at the receiver side). Comments?
IT is OK to send ASCII strings but still you need the length byte correct. To send "hello" you must type: '5'hello
83About the sniffer: when I configure the Sniffer as a slave, should I see all master messages to all slaves (independent of the address configuration)?
You will see all Master messages for the same mode as long as the Slave is not configured for Sleep mode and that you have configured the Slave for accept all messages.
84When I activate UART_FLOW_CTRL = 3 (CTS/RTS), I didn’t succeed to receive & send datas with the RC1180 when I activate RTS/CTS on application side.
Please verify by a oscilloscope that the application side use UART handshake as required by the Radiocrafts module. Specially look into the polarity etc.
85What happens with frames, that are received while transmitting another frame? If I understand this correctly the module returns to idle state after the frame is sent to the uart. That means, if a frame is sent, while the module is not in idle mode, it can’t recognize the second frame. Right?
Your summary is correct. The module can’t receive another packet if it is not in IDLE. If a new packet is transmitting from the meter while the Master is occupied sending last received packet out on UART, the new packet will not be received. Increasing the UART baud rate to max will mimimize the likelihood of this incident.
86we have an issue about the use of the 169 Module RC1701(HP)-MBUS4 fw ver 1.10 (see the attachment) We see that we can receive up to 124 Byte while we are sending 240 byte. There is some setting we have missing somewhere?
Max packet length (L=F6 gives 255 byte including header) is supported, but you need to increase the UART baudrate >= 56700 baud. For N mode using low RF Data Rate the module will not complete the packet transmission before internal timeout (default 2 second) takes place. Increasing UART baudrate ensure that the module have time to complete the packet TX before timeout.
87we have a problem with the configuration of RC1700HP(MBUS4). We start our micro and we start the comunicacion for the uart with the radiocraft RC1700HP likewise with the RC1180 MBUS3 (with a low level in the nConfig pin) but the Radiocraft RC1700HP don’t responde (with the symbol >). We watch with the oscilloscope that in the pin RTS/SLEEP in this case we have a High level and in the RC1180 we have a low level, could be this the problem, you know why can be? The supply that we use for the RC1700HP is Vcc = 2.5v and Vcc_PA = 3.6v. Is this ok?
"If the config-pin is asserted low twice, it will not give prompt the second time. So if the module is already in config-mode after power-up sequence (if config-pin voltage raise slowly compared to VCC), then it must have a Reset low before
config can go low again and module will give new prompt. If you try Reset + config in a sequence from a controller (or manually), then you should see prompt ‘>’ for each config low.
It can also be a problem if the RXD pin is floating during your tests; Then the CMOS input might cause a lot of characters to be sent, and then I am not sure how config-mode will behave. So during all tests, use a maximum 8k2 ohm resistor as pull-up to
VCC.
Your voltages are ok, the module should work fine.
The RTS/Sleep pin does not matter unless the module is configured for using this pin, but in the default mode it is not used
"
88We do the test you proposed (DTR signal to a fixed voltage) but needs more details on how to do it. Could we set the DTR to 1 using the configuration program or must vie done in hardware?
"DTR must be connected to ‘1’ in hardware. You have no option to do this in the configuration program.
For module configuration you should set the UART baud rate according to the flonidan meter and try with different combination of PACKET_TIMEOUT and PACKET_LENGHT. Best guess is PACKET_TIME=1 and PACKET_LENGHT equal to the longest packet frame from the flonidan meter.
"
89We did configure one module in Sniffer mode and the other one in continuous data packet transmission. Whatever the transmission mode selected ( T2 or T1) the sniffer sees datapackets in 06 mode meaning T2 configuration.
"it seems like you have chosen Packet = Access Demand Install in the MBUS-DEMO tool, hence the C-field is 06 (see the field shown to the lower left of the window). You can edit the C-field, or you can choose another test packet.
The C-field value is not determined by the mode (T1 or T2), but by the configuration of the C-field (using the ""F"" command). The MBUS_DEMO tool configure the C-value according to the setting in the ""MBUS C-field and UART packet"" window.
"
90We are using Radiocrafts MBUS3 and MBUS4 modules. Initially we are configuring the parameters like network address , mode in the internal Memory. In few cases the module became non responsive and if we try to read the values it returns 0xFF or does not respond . After this we cannot use the module. We not modifying the baud rate or calibration value of the module.
If you get prompt when CONFIG goes low you can rectory reset the module by the ‘@RC’ command while CONFIG is low.
91We are interested in using Radiocrafts modules in our product. We need to install around 150+ sensors per house which are connected to one concentrator (master) device. Sensor are small and therefore using external antenna is not an option which may be problematic when using 169MHz? Those sensors are installed into houses with concrete walls and range requirements are therefore at least 150+ meters in NLOS situations. We are considering to use Wireless M-BUS protocol or some similar which do not require acknowledgements from the sensor. We prefer sub 1-GHz radio because of coverage. Could you suggest some of your modules which support 150+ slaves in one network and extended range at least 150+ meters in urban area? Please also take into account our antenna limitations.
"You could use the wireless M-Bus protocol which supports hundreds of nodes pr concentrator. How often do you need to transmit from each sensor?
I would advice on 433MHz which will give you better range with same output power. The 433MHz requires a longer antenna, but usually 433MHz is no problem to make a good antenna even with limited space. 169MHz is more difficult as you write.
Are the sensors battery operated?? Then a mesh protocol is limited value, unless you can use repeaters?
The wireless M-Bus protocol includes a repeater, which should extend the range for the sensors with the longest range.
"
92We are going to use RS1180-MBUS modules in our project. Please tell me how it works in a network in repeater. Is it possible to use routes in a network?
Wireless M-Bus supports 1 repeater (total of 2 hops) but not multi-hop or mesh. The protocol is an open standard which is intended for local area networks.
93We are going to use RS1180-MBUS modules in our project. Please tell me how it works in a network in repeater. Is it possible to use routes in a network?
Wireless M-Bus supports 1 repeater (total of 2 hops) but not multi-hop or mesh. The protocol is an open standard which is intended for local area networks.
94We are following observations on the MBUS3 repeater 1. Repeater repeats the message after Random delay we have observed it as up to 20 seconds. 2. Repeater does not repeat the message in the sequence it is received . 3. Sometimes message does not get repeated. We have tested this when with the Transmitter transmits every 3 seconds and at the receiver it is replied within 500 mSec of received message. Can you please give your comments on these observations.
Please see MBUS User Manual for details about the repeater functionality embedded in the module. You will see that there is a random delay before repeating the packet to avoid collision. This is also the reason that the repeater stores the incoming packets and repeat them in a random order. It is only SND-IR and SND-NR packets that are repeated.
95Under which circumstances does the Radiocrafts module filter out messages ? Is it based on the C-Field on the data link layer and the CI field on the application layer ? If so, is there a way to switch this off ?
| The C-field is used to check if it is an installation request message. (in installation mode) When all messages are accepted this will mean the the master will receive all messages. Slave will still only receive massages addressed to it selves. There is no other filtering. |
96There is something I do not understand. In the 169 Mhz it is allowed to transmit at 500mW or +27dBm. This is specified by the module if a power supply of 5V is used for the power amplifier. However , if you want to transmit at +27dBm this means a Vpp of approximately +14.1 Volt . Is there a DC-DC convertor on board of the module ?
| The module transmit +27 dBm (500mW) when transmitter part is powered with 5V. No additional DC-DC externally is needed. |
97The WM-Bus module on my PoC unit sometimes stops sending serial messages (eg overnight). The Radiocrafts Demo PCB continues to receive OK, so it’s not the radio signal stopping, it’s the module serial output stopping. It starts again after turning Vdd off and on. This could be radio interference on the PCB wires perhaps, eg insufficient filtering on the serial data wires or Vdd wire, so I will improve that on the PCBA.
"I am not sure if I clearly understand your test setup, but there are two things which can cause the module to behave strange;
- RXD-pin, into the module: If your PIC at any stage (during sleep or startup) does not drive the RC1180 with push-pull output, insert a 8k2 (or less) resistor between the modules RXD-pin and VCC. The CMOS input is quite shaky and need
distinct high and low voltages
- Reset: Same issue here, it need to be either well filtered or have low AC-impedance to GND (or VCC). So best solution is to short-circuit the Reset-pin (pin 12) to VCC. This must be removed before any re-flashing of the module, but is no
topic right now
Apart from these, no other issues are noted which can cause the module to malfunction.
"
98The configuration process with bus-CCT v1.02 will work fine. The problem is that they can’t send and receive data The T1 mode is their priority – RF_Channel = 12 – RF_Data_rate = 3 – MBUS Mode = 1 A test with a spectrum analyser will show no transmission. A test in reception mode does not show any reception.
In configuration mode it is important to enter test mode 3 before you go back to normal operation. Alternatively you may also reset the module after leaving configuration mode. You should now be able to send MBUS packets as long as you follow the guideline on how the UART packet format should be. That is you need to start the UART message with the packet length as described in the enclosed quick start.
99Sometimes RC1180-MBUS3 stops responding and we found that the configuration registers in module’s flash are damaged (FFs instead of meaningful values). Do you have any suggestions what should we check on our side? Any ideas what could be the reason of the configuration lost?
"The most likely reason for corrupting the configuration memory is when using the “M” command, and the internal re-flashing sequence is interrupted. When using the M-command, please make sure to wait for the prompt (>) after you send the last 0xFF, before removing power or resetting the module.
Also avoid using the M-command if not required (check if value is actually different before writing, or use volatile memory command instead if possible (P, C etc)).
"
100So, does this USB stick and the PC software come with open software so we really understand what happens between the PC and the USB (RC1180-MBUS3). Which we can use to make our own implementation in our Gateway?
"The PC software will show the packets, information in the packets, decryption etc.
It is a packet generator, a packet sniffer, and encryption handler to help you start.
This is a very powerful tool for your development and implementation in your gateway.
I am sure this is the tool which will help you understand how the module works and how to interface with the module.
"
101Regarding the modulation, I have a question about setting the modulation method. In my measurements , I changed the RF frequency with the volatile ‘C’ command. There is no volatile command to change the modulation method, so I left it at default. Then I find that the message transmission time at RF is the same for all channels, suggesting that the modulation scheme is the same. Is this the case, and is the default modulation valid for all channels? I need not be compatible with strict EN 13757.
"When it comes to modulation method it can only be set in non-volatile configuration memory and by choosing the right data rate: So RF_DATA_RATE=0x04 = 19.2 kbps is with 4GFSK while 2.4 and 4.8 kbps is with GFSK.
Unfortunately you will have to change the RF data rate in non volatile memory at the same time you change the channel number."
102In your mbus manual wrote (pag 4): “”In OMS (MBUS3) the master sends a command with its own address as Link Layer Address, and the slaves address as Application Layer Address.”” You mean that only long Appl header (12 byte) containing the slave address is granted ? If I got it the MUC and slaves have same link address (i.e MUC address) .. is it correct? Does your mailbox feature use this format ?
| Yes, the application layer is only used for long header (12 bytes).If long header is used the slave address is used as the application layer address, and used for identification. The mailbox support application layer. If the mailbox message is intended for one slave only you can add the slave address into the mailbox message after CI field. If however the message is intended for several slaves you can use a template by using 0x00 for all application layer address bytes in the mailbox. The Master will in this case auto replace the 0x00 bytes with the slave address from the incoming slave message on the mailbox reply. |
103in order to assess the SNR threshold of my RC1700HP-MBUS device, I’m mixing the signal from the 169 MHz gateway to the Meter with a white gaussian noise signal. In order to compute the actual received noise power, I should know the amplitude of any filter present in the receiving stage. According to the standard, channels 1a/b, 2a/b and 3a/b have a width of 12.5 kHz and therefore I’m simply supposing that a filter with a bandwidth approx. equal to 12.5 kHz will be present somewhere at the receiver. Could you please confirm my assumption?
Yes, your assumption is correct. Receiver filter is 12.5 kHz.
104If they use MBUS protocol , must they follow the protocol for wake up/ sleep? They will connect the slave with a Micro so the slave will be awake by the micro. In this case can the customer control the transmission times from the slave without following the protocol.
. If they do not need to follow the OMS system specification they can implement any proprietary wireless solution benefit by using the Wireless MBUS module from Radiocrafts. They are free to use the module as they like, as long as they take into account the regulatory requirements on TX duty cycle. Other than that they can wake up the Module as much as they like and transmit MBUs packets. The 15 min period I mentioned to you was if you follow the OMS, and this period enable 15-20 years battery power metering systems.
105I’m doing a reasearch for our new project involving AMR readout of gas/water/elektricity meters. I’m looking for a device that will be capable of reading pulses from a meter and send them wirelessly to local data logger. This has to be standalone solution as receiver has been already chosen. Do you have such device in your portfolio?
| We can suggest the RC1180-MPC1 (at 868 MHz) and RC1701HP-MPC1 (at 169 MHz). These modules have integrated an Pulse Counter functionality. |
106I’m currently working on a wireless M-Bus project, and I try to run the developement kit with meters. In fact, I get to receive a frame sent by a counter, but I can not return it even if I put the module in “”Repeaters Mode
If you try to receive meter packets using our module you must configure it for Master mode. Unless you install the meter in the master you must configure the module for accept all packets (INSTALL_MODE). His will enable the module to receive all wireless MBUS compatible packets. Also make sure you use the same mode (S or T) as the meter. For details about configuring and using the RC1180-MBUS modules please see MBUS User Manual
107I were unable to made RC1180-MBUS3 modules work in REPEATER mode using T frames. I have programmed the module following the User Manual procedure, show below NETWORK_ROLE = 0x002 MBUS_MODE = 0x001 Using the “”M”” command to record the non volatile memory. But it doesn’t work.
Your Repeater configuration looks OK. Note that the Repeater only repeat valid SND-NR and SND-IR messages that has Hop-Cout set to 0. The Hop counter will be incremented to 1 on the repeated message. For details please see MBUS User Manual page 35.
108i tried to use with 2 demo boards the mailbox feature on a master but I failed , I didn’t see any reply fom master to slave in packet sniffer. Is it implicit ?
| ) Select a CI field that require 12 byte header and use the template option when writing to the mailbox. This will take out any uncertainties of typo in the mailbox application layer. For simplicity also uncheck all flags in the MAILBOX (0x16) location of the configuration memory. See MBUS User Manual page 34 for details. Un-checking all flags ensures that the master replies from the mailbox on each salve message (no auto clear of flag register), and that no additional validation are performed on the last 4 bytes of the 12 byte application header prior to the reply. If you user MBUS-DEMO you will find the MAILBOX flags in the 'Module Quick setup' tab. Note also that before you can use the mailbox you need to install the slave to master, and set the correct mailbox number in the flag register for this installed meter. In MBUS-DEMO you will find the 'flag register' tab in the 'Concentrator Install Emulator'. The flag register is set by the 'A' command as described in the MBUS User Manual. |
109I need to sniff traffic from a master (electricity meter). So in T2 mode I need to configure the sniffer as slave, so I can see traffic from the electricity meter. But, it appears the MBUS-DEMO doesn’t support this mode?
Configured as Slave you will not listen for packets. It only listen in the OMS defined listening window after transmission. You should be able to sniff T2 Master packets if you configure the module for Master S.
110I know by using Zigbee module that even if they use an “”open protocol”” it doesn’t mean you can be fully compatible with other manufacturers (aka ZB home profile, …). Is it still the same with Wireless M-BUS? Is it all about Application layer?
Yes, its more on a system level / application layer that you have to make sure to USE the wMBus standard in a certain way to be interoperable. But compared to ZigBee, wMBus is “easier” to play together.
111I have two more questions: – If I send a CNF_IR (or a REQ_UD2) as automatic reply, the status byte is automatically set to the RSSI value, but I want to send 0 (zero). How can I do this? – If I send a CNF_IR (or a REQ_UD2) as automatic reply, the signature is automatically set to 0xC000, but I want to send 0 (zero). How can I do this?
When using the Auto message generator the master reply will comply with OMS packet structure including RSSI and Signature info. To manually set the master ack packet frame you should use the mailbox.
112I have been asked to evaluate the possibility of incorporating a wireless MBus solution into an existing wired MBus device and came across your products in a technical magazine. What other additional devices, other than the module, may be necessary to create a small scale network. We are familiar with all aspects of electronic design so need only the basics.
"The module is a complete embedded RF unit, with all the wireless M-Bus protocol embedded inside the module.
The module can act as a master, slave repeater and consentrator. This is specified in the user manual for module.
The module is also available with pulse interface option, then the module can read the pulses directly.
You can use the demo board or the USB kit as a reader/consentrator. I recommend the USB demo board since this has quarterwave stub antenna and has a more real performance of a consentrator. The PC software has a packet generator and a packet sniffer, to make your development easier.
"
113I have a RC1180-MBUS3 and I want to read an encryption key in the register 1, registered with the ‘K’ command. Is it possible? How I can do that ?
For security precaution we have no commands for reading the encryption key.
114I configured the MBUS radio to use the UART flow control using the CTS/RTS pins. When the host processor wants to send an MBUS message, it pulls the RTS pin low and waits for the radio to pull CTS up. The processor then sends the message. But this gives strange results, and sometimes it just fails to send the message. I also tried using only the CTS pin, where I wait for the pin to go high before sending the message. Again, this does not always work. Are the CTS/RTS pins exclusively for controlling the flow over the uart connection (host processor to radio) or are they meant to indicate when the radio can send another message ? If so, how should I use them ?
CTS informs that the module is busy when it is high. It can be busy if it receives a packet over air or if it transmit a packet. Note that it is busy and CTS is high both during the actual reception/transmission and during baseband handling of the data to/from UART. I have enclosed a time plott when the slave send 5 bytes over UART and the master receive the Header + 5 bytes. CTS is enabled and informs when the module is busy.
115I activate the reception of the entire frame (start, header, rssi, crc & stop) using DATA_INTERFACE = 12. I wonder how to calculate this CRC? Is it a arithmetical sum of the following data : C field, Header, Ci field & payload as it is specified in M-bus documentation?
"The UART CRC when enabled in DATA_INTERFACE is calculated from and including the original length byte (excl the two CRC bytes), to and including the RSSI append byte (if enabled). Start/stop bytes (if enabled) are not included in the CRC calcalcution. The Wirless M-Bus type of CRC is use (init value 0x0000, polynom 0x3D65, result inverted). LSByte is sent first.
The algorithm to check the CRC would be:
-Remove the start/stop byte
-Remove the two CRC bytes and reduce the length byte by 2 (maybe this was the problem?)
-Then calculate the CRC over the remaining frame (including any RSSI), starting with the length byte Invert the result
-Compare with the received CRC.
"
116How can I make a mobile readout device with RC1180-MBUS3 (…reading heat meters from car or by walking)? How can I setup up a module? Must I use „install mode=accept all”, or should I every time before I want to collect data from heat meters use The install mode, after install mode master keys settings…?
"In this case you would use the “accept all” mode and decryption off.
Then you would do back-end decryption based on EN13757.
"
117Dear Radiocrafts team,, would you have a solution as to where we could take a wired mbus connection from meters and convert to wmbus or a radio signal enabling us to read the meters remotely?
"Wired Mbus to wireless is a challenge from power side of view.
A wired MBus meter is a slave and the is powered through the wired Mbus cable.
Thus for a “dongle” to power up the slave MBus, read over Mbus and then send over wireless Mbus requires much power.
So either the dongle will have very low battery lifetime or mains powered.
All the business cases we have seen on over the last years for this has collapsed due to the power supply issue.
"
118Could you tell me if it’s possible to filter Wireless M-Bus frames on RF to accept just frames which comes from the slaves registered in the master with RC1180-MBUS3 ?
Yes this is possible and is configured by the INSTALL_MODE. See MBUS User Manual page 38 for details.
119) I read OMS specification and now Data application Layer is much clear to me. Our goal is to use DLMS/cosem application layer over mbus. I saw in OMS specification that there is a correlation between VIF/DIF and OBIS code …but information about that are very weak. Have you got frames’ examples of DLMS Application in order to understand data exchange?
| You will find a list of OBIS Codes for Basic Meters and OBIS Declaration via MBUS in OMS spec Vol 2 Annex A and B. Additional information about DLMS is described in EN13757-1 Data exchange. |
120After different test, it seems that ‘s’ command works only in ‘RX only’ mode (test 3). Is it normal?
Yes, you must force RX mode before using the ‘s’ command.
121The modules we have are with memory for up to 64 devices (8 bytes for each device), binded in RC1180 internal non-volatile memory. Do you have update with more memory for this purpose?
The standard MBUS3 support up to 64 slaves per Master. If you need more devices it must be handled as a costumer specific variant of the MBUS3 firmware. Alternative approach if you need more devices is to configure for accept all and handle the filtering in the host controller.
122I would like to kindly ask you some information about: – the best Software Tool I should use for RC1700DK-MBUS4? The availability of the Demo Software Tool? The updated list of accepted Operating Systems?
RCTools-MBUS (including both MBUS-CCT and MBUS-DEMO) from our web is the PC tools to install for your RC1700HP-MBUS4 kit. The package on the web is the latest and support all available versions of MBUS modules from Radiocrafts.