My advice? anyway, I updated the code here and the basics still seem to work, I didnt do any more testing than that - I did note they single_pkt_fwd_v003.hex code didnt change the version number reported by the internal web page, in fact I dont think they changed the old version in the source code
Playing with single channel gateways just reminded how incredibly limiting they are sadly - its back in the cupboard for now
Hello @HaSch
I’m trying to build a gateway with Raspberry PI3 and Dragino Hat, which allows downstream messages.
Looking in the forum, I found your post in which you claim to have tried the code this code: https://github.com/bokse001/dual_chan_pkt_fwd/tree/dual_chan_pkt_fwd_up_down
and after some changes you are able to make it work.
I’m not able to find other posts on the subject, being the post dated,
I ask you to confirm if it works and allows the downstream messages.
Thanks
@Batigolle
I can confirm that Pi 3 with Dragino Hat works with the modified boksem code as I described with up and download.
Thanks HaSch
I will try this code with your changes
Has anyone done any dragino + mqtt direct application? the dragino firing the packages to the server on a normal pc via mqtt?
Hi all
I did the test with Raspberry PI3 and Dragino Hat v1.4 and
I confirm that with the changes suggested by @HaSch ,
it works
by also receiving the Downstream Messages !
I made a further modification to the global_conf.json file
For the test I used a sensor with the code .ino taken from the examples folder of tftelkamp / single_chan_pkt_fwd.git,
subsequently modified, to transmit, only on channel 868100000
The default installation on the raspberry, / bokse001 / dual_chan_pkt_fwd
receive the messages only on channel 868300000, so I modified the global_conf.json file
by inverting the values of the two freq and freq_2 fields
from
{ “freq”: 868100000,
“freq_2”: 868300000,
…
to
{ “freq”: 868300000,
“freq_2”: 868100000,
…
Finally,
in the sensor code, to receive the DownStream message,
I added the following line of code, inside the setup () function, before do_send (& sendjob);
// Let LMIC offset for +/- 1% clock error
LMIC_setClockError (MAX_CLOCK_ERROR * 10/100);Hello. Using my LG01P gateway, I am not able to transmit the incoming data (via LoRa) to the server. Someone with similar problem? Each time you transmit different, always forward the same value to the server
Hi all
to implement, a gateway with Raspberry PI3 + Dragino Hat v1.4, which allows to use the Downstream messages, I opened a new Topic where I gathered all the information
LINK TOPIC
Hello Everyone, I’m from India and ordering A Dragino Gateway with 868 Mhz option.
But my node SX1272 sends payload from 865 to 867 Mhz Frequency.
Does Dragino scan the spectrum from 865 to 868 Mhz ?
We have already tested successfully our node device with Kerlink and MultiConnect Conduit with 868 Mhz as they are able to scan and receive from 865 to 868 Mhz range.
And will I be able to receive the data with Dragino 868 Mhz ?
hallo, plz help me, i use lora mini dev + Lora GPS/Hat at same freq (868mhz), and i use sensor node dht 11 humidity, i just can recieve data from lora mini with serial to my laptop, i don’t know how to connect lora mini to lora hat, lora hat is actived and connected to TTN, i use single channel pkt fwd, please help me give me a sketch or anything how to connect lora mini + lora hat and get the sensor data…
Hey, I managed to solve this issue by resetting the frame counters on the device settings in the TTN console (Overview tab). After the counter reset, the node status changes and the TTN begins logging the payload data once again.
Hi Everyone, i have build a Single Chan Gateway with the Dragino Lora GPS Hat and the Packet Forwarder by Telkamp (https://github.com/tftelkamp/single_chan_pkt_fwd) and connected it to TTN. (I know this forwarder is deprecated) Im receiving packets from some Node, but on the TTN Console it doesnt show any transfered Data in the “Traffic” Section, it is empty.
I already checked the UDP connection, which seems to be fine. TTN is definetly getting the status msgs with the gps data. (Shows the location of the Gateway on the map, at least on the TTN mainpage https://www.thethingsnetwork.org)
The “Received Messages” counter on the console only shows 2, even though I received much more packets with the gateway.
Does anyone know why there is nothing listed on the “Traffic” section on the TTN console?
And does anybody know how to fix it?
Thank you guys very much.
How are you sure you are actually receiving more packets with the gateway than the 2 Received Messages that your counter shows? If you are referring to the output that you see in the terminal after starting the Single_Chan_Pkt_Fwd routine on your RaspberryPi that isn’t always packets being received. I don’t have access to my Pi at the moment but you will see periodic updates in terminal that are just the Packet Forwarder routine running through it’s loop but unless you’ve actually received something it won’t show up as traffic on the Console.
Yes, I’m pretty shure about that. 
Ok, so you’re using the dual_chan_pkt_fwd now and not using the single channel packet forwarder you alluded to in your other post. It could be the problem here if things weren’t set up right but you are still right that you have apparently received packets. Are you using the Dual Channel setup that Batigolle has used?
The next assumption is that the reason you’re not seeing it in TTN is that the packet is not meant for TTN. I pick up random packets here in Montreal that I know do not show up in my Gateways count, as I can pretty much guarantee that that count number I see are all messages from my sensors. At least on my test gateway as it’s not that high of a number.
Thanks a lot for your concerns. Right now Im using the Dual Channel Packet Forwarder that Batigolle introduced in the forum, but its based on the Single Channel Packet Forwarder by Telkamp.
I thought that unknown Packets from different Networks than TTN are also received and processed by the servers and then dumped.
I’m wondering why the TTN Console shows 2 received msgs but doesn’t show any information in the Traffic section.
Next week the hardware for my node and a real LoRaWAN Gateway Module should arrive, then I can continue testing the TTN.
Ok good luck, I had the same issues at first with my LG-01 that I had bought initially but was able to make it work well enough. Haven’t had this issue with the LoRa Hat that I had tested though. Hopefully with your node and real Gateway you’ll have an easier time.
Hello, I’ve created a loRaWAN Gateway using a Raspberry Pi 3 and a LoRa Sheild, it works fine. Then I tried to send data to this gateway using a node made of: Arduino, Lora Shield and sensors (DHT22 and tsl2561). First, I send a basic “Hello World” message using this code (https://github.com/matthijskooijman/arduino-lmic/blob/master/examples/ttn-abp/ttn-abp.ino). It worked fine. But, When I tried to send DHT22 data (temperature and humidity) I couldn’t. The last thing I tried is to use this code (https://github.com/goodcheney/TTN_Mydevice/blob/master/DHT11_Mydevice), I’ve made some changes (the DHT22 declaration and the reading). But I’ve always that payload: 01670000026800 which is not the data I’ve wanted. What is wrong with my code? Is there any other way to send data properly to the gateway? Please, I need your help. Thanks.
Hi @airichi
did you change the decode code, to read the hexadecimal string and convert it back to numbers, on the application where the node is registered?
defauly the decode code in payload formats, reads a hexadecimal string and converts it to text
That hex value is in your code you linked to on line 18, if you remove or comment out that line what do you see from your node? Remember to make sure that the rest of your mydata lines are appropriately setup properly if you do that.
I’d also suggest maybe looking at this code, to see how he uses a DHT sensor with the LMIC library. Even though it’s not the same device the code might be helpful to you.