I have already referred the document and i tried to send the bytes,I am supposed to receive the reply from the device as “mac_rx “”” but i am receiving just “mac_tx_ok”
what would be the reason for not receiving the data. i have looked in the community discussion. many have faced the problem but i have not seen any solution for it.
Excellent - because that’s how it works.
You send your uplink with mac_tx and if there is a downlink, you will get back a mac_rx with the port number and the data as hex. If there is no downlink, you’ll just get mac_tx_ok
Which means it’s working as expected.
What is the issue again?
Iam sorry it was a typo.
it has to ve mac_tx_ok not mac_rx.
sorry for the typo
I don’t understand, the documentation is clear, you get mac_tx_ok if the Tx is OK and mac_rx with data if the Tx was OK and you’ve got a downlink.
If you don’t get a downlink or it doesn’t hear the downlink or you haven’t scheduled a downlink, you won’t get a mac_rx response.
can you please help me to know how would i schedule the downlink.
I am facing a issue in hearing the downlink
You won’t hear a downlink unless you schedule it. The downlink is documented - follow the link in the bottom right of the console.
I hope you are speaking about this documentation. I have tried using this. I have send the data packets also. But the response from rn2483 is same .
What does this mean?
If you’ve tried the encoder which is for encoding the downlink, it does not actually create one and if it hasn’t worked in creating a downlink for you, does this indicate that it’s not the right thing?
What do you get when you search the documentation for downlink???
https://www.thethingsindustries.com/docs/integrations/payload-formatters/javascript/downlink-decoder/
this is the documentation i have gone through.
Or you need to configure your backend to send, via mqtt, webhook or one of the other intergradations you use.
If you look in the documentation under each of the integation mentored, there are info on downlink.
You can manually send via the console.
I have tried this method also.But I am getting the response from the device as mac_tx_ok instead of mac_rx.
This is my exact issue
Is this in the TTN console or device debug?
Not TTN console,the device . I have interfaced esp32 with RN2483 lora module to it.
If the data was sent from TTN server, then the lora device would have replied as mac_rx_portnumber_data.
OK, two things going on here:
- You need to look at the options you have in the console - like getting in a new-to-you car - you figure out the basic controls before pulling out in the traffic.
- I hadn’t realised that the documentation search didn’t include the messages section for the device, so I apologise, but hyper-focusing on the first entry that comes up in a search rather than looking around is a questionable strategy.
You need to go to the console entry for the device and then click on Messaging on the horizontal menu bar and then choose Downlink which will then let you send a downlink.
There is not much information I can find MAC
MAC Settings
So looks like you are going to need and dig for information, I have looked before and only limited information.
You need to look at the RN2483 data sheet and there you will find those listed codes are responses issued by the module after a transmit command.
Show us. If you schedule a downlink in the console you should see an entry in the device live data with the text ‘Receive downlink data message’. Show us a screen shot of such an message please.
1 Like
Your screen shot shows a downlink RX1 delay of 2 which is extremely uncommon. Why are you not using the default value of 5 seconds? (After changing this you must reset and rejoin your node)
how would i change the delay time ?
Advance MAC settings for the node
