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

FACES and FACES II keyboard conflict with LoRa 433 #244

Open
0RIN0C0 opened this issue Mar 2, 2021 · 0 comments
Open

FACES and FACES II keyboard conflict with LoRa 433 #244

0RIN0C0 opened this issue Mar 2, 2021 · 0 comments

Comments

@0RIN0C0
Copy link

0RIN0C0 commented Mar 2, 2021

Hello guys, I'm new to the GitHub community, but my problem is a classic hardware problem, I think:

I you connect a FACES module+keyboard to the M5Stack Grey+LoRa module then the LoRa module does not send of receive anything. After some search online I found out that the keyboard uses as its interrupt line the same line (pin) that the Lora module uses as its chip/slave select line (marked either CS, SS or NSS). This is pin 5 on the M5Stack connector. Is there a way of fixing this without resorting to soldering?

I know that the M5LoRa.h file contains a function called setpins where the main pins for the LoRa module operation are defined: setPins(int ss = LORA_DEFAULT_SS_PIN, int reset = LORA_DEFAULT_RESET_PIN, int dio0 = LORA_DEFAULT_DIO0_PIN);

I am pretty sure that you can change the SS (slave select) pin there and be done with it, as far as software changes are concerned, but that means that you should now hard wire another of the M5Stack connector's pins to the LoRa chip's SS line. I am trying to avoid that. Is there any other way? Perhaps there is a way to change the line that the keyboard is using as its interrupt?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant