Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conflict Between LoRa CS Pin and GSM Modem Reset Pin on LilyGo-TA7670 v1.2 #160

Open
kadrimanaj opened this issue Oct 13, 2024 · 5 comments
Labels

Comments

@kadrimanaj
Copy link

I am using a LilyGo-TA7670 v1.2 (2022-07-18), LILYGO 868/915MHz Model: LORA32 (20-3-6) v1.1. I've noticed that the LoRa CS pin is IO5, which also functions as the modem reset pin. This overlap raises some questions about usage:

Can I use each module (LoRa and GSM modem) independently without interference from one another? For example:

Using LoRa while keeping the GSM modem off.

Using both LoRa and the GSM modem simultaneously, such as receiving LoRa data and logging it to a server using the GSM modem.

If simultaneous use is not possible due to this pin conflict, is there any recommended workaround? Would another LoRa shield that uses a different CS pin be a better solution?

Any guidance or suggestions would be greatly appreciated. Thanks in advance!

@lewisxhe
Copy link
Contributor

Do you use this? I remember it seems to conflict with the A7670 pin
image

@lewisxhe
Copy link
Contributor

If you are using the expansion board above, then removing the MODEM rst is the best option. The modem rst has no effect on this board because of the Power Ctrl.
If you want, you can remove the resistor pointed by the arrow to release ESP32 GPIO5

image

@kadrimanaj
Copy link
Author

Thanks, bro i will test and tell you the results
My logic is to get data with Lora and save it to an SD card
put sleep GSM and where I need to send data examples every 10 min
wakeup send data and put GSM to sleep again.

Copy link

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Nov 16, 2024
@kadrimanaj
Copy link
Author

thanks

@github-actions github-actions bot removed the stale label Nov 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants