are you sending to fast ?
how big is the payload then in total ?
I don’t get it why it skips exactly 8 frames everytime… must be something in your code
Single Channel Gateway maybe?
@BoRRoZ
I am at the first attempts of operation with Esp32 Heltec
I am only installed the library https://github.com/matthijskooijman/arduino-lmic
and I using the sample ttn-abp.ino sketch in the library
I have not modified anything in the code, except the fields NWKSKEY, APPSKEY , DEVADDR and correct the lmic_pinmap.
I’m using Single Channel Gateway Raspberry + LoraBee
I did a test (do not ask me why I did it … I do not know, just a test), but the result is strange
I commented on the following lines
I went from 8 frames to 3
Not doing any configuration will make your node use the 3 default channels. The single-channel gateway will be listening to one of them, so on average you’ll get one-third of the messages.
(To make a test node only use one channel, see Can LMIC 1.6 be set up to use a single channel and SF?)
Problem of transmitted frames lost: SOLVED
Following the instructions suggested by @arjanvanb …
Thank you all for your help
But remember: having a node sending on only 1 channel is outside of LoRaWAN standard and not good for the network / gateway capacity.
You’re right … I’m making gateways and sensors as cheap as possible, for hobbies.
If the experimentation is successful I will switch to something standard Lorawan
For the ESP32 versions of SCG which of the DIO pins of the LoRa device are needed, or does it just vary with the implementation ?
I have seen the ESP8266 SCG and that needs DIO0, DIO1 and DIO2 in a diode OR arrangement.
I also note that one Pi SCG uses only GPIO0 and another that appears to uses GPIO0, GPIO1 and GPIO5.
The use of DIO0 and DIO1 I can understand (also used for LMIC nodes) but DIO2 is FhssChangeChanel in LoRa and direct modulation in FSK so is that being implemented in the Gateways ?
Just joined the community. This is my 1st contribution.
I’ve designed a 3d Printed Case for TTGO LilyGO V2
Here’s the link:
Feel free to comment. I will try to fix eventual errors.
A suggestion: It would be great if there would be a 3D Printing thread/category.
welcome… and you can start a 3D printing thread if you feel like it.
printertypes , tips and tricks, models related to TTN ect.
The reason for asking the question is that the ESP32 has just enough I\O pins to allow for it to drive 3 SPI LoRa devices such as RFM9x, so a 3 channel receiver ought to be possible. Not sure if its practical though.
Cool. Interesting project btw!
ordered 1 piece via thingiverse / Treatstock print service.
Hi,
i did a little rework of the pinout for TTGO V1 (V1 mirrored) and V2.
I would like to share these and will attach them to this post.
it would be nice if someone can check the pinout and give me a short reply if there is something thats wrong or could be done better.
Thanks in advance - have a nice day
Andreas
Update: V1 mirrored removed permanently as a request from bluejedi. V2 removed temporarily for further research.
The V2 board looks pretty good to me.
Ignore me. I was looking at an old pinout
First, the graphics are nice but:
What about reading this thread first and check the correctness of the pinout yourself first!
Your pinout of the V2 contains several (copied) errors.
There already is a much improved version of the TTGO V2 (compared to the ‘original’) available in the Opening Post of this thread (read it).
Why a mirrored version of V1? This will lead to confusion.
If your purpose of ‘mirrored’ is to create a Bottom View of the pinout then you should show the bottom side of the board (and title it Bottom View), not the top side because that is very confusing and error prone.
@nibelungen
I suggest you remove the current version of your ‘V1 mirrored’ pinout and the V2 with errors.
You could replace ‘V1 mirrored’ with a Bottom View version.
There is a better and more correct TTGO V2 pinout in the opening post already.
Note: You can edit a post only a limited number of days so don’t rely on thinking you can edit/replace them at a later moment.
Really?