Hello Forum,
I successfully built a LoRa project based on Bill’s tutorial, with a transmitter on my balcony and a receiver displaying the temperature readings in the Serial Monitor. However, I'm facing a challenge in connecting a dot matrix LED display to show the readings with time and date. The original project used pins 3, 11, and 13, but these are occupied by my LoRa project. I tried redefining the pins, but it didn't work. Before troubleshooting further, I want to clarify if it’s possible to use different pins for the LED display, or if I need to use the original pins specified in the tutorial. Any insight on this would be appreciated!
@fhaddad You didn't say what board. Generally speaking there is a lot of flexibility on pin choice unless the board has only one of a certain kind of pin.
What pins are used for the LORA part, and what logical pins does the display need (by logical I mean are they SPI, I2C and so on)
EDIT: Sorry, didn't notice that the topic specified the board. From what I can see, those pins are just digital pins, so you are free to change them to any other digital pin. Stay away from 1 and 2 though.
First computer 1959. Retired from my own computer company 2004.
Hardware - Expert in 1401, and 360, fairly knowledge in PC plus numerous MPU's and MCU's
Major Languages - Machine language, 360 Macro Assembler, Intel Assembler, PL/I and PL1, Pascal, Basic, C plus numerous job control and scripting languages.
My personal scorecard is now 1 PC hardware fix (circa 1982), 1 open source fix (at age 82), and 2 zero day bugs in a major OS.
@zander Ron can you please spot any mistake in my code below?
I figured it out; thanks a lot, guys.
@fhaddad OK, but there are two points. First, use the help menu on the right above recent posts to learn how to post code, and please use the Tools/Auto Format before posting.
The second point is this forum is for learning, so just letting us know you fixed it does not help. Post the fix, then mark the topic as solved.
First computer 1959. Retired from my own computer company 2004.
Hardware - Expert in 1401, and 360, fairly knowledge in PC plus numerous MPU's and MCU's
Major Languages - Machine language, 360 Macro Assembler, Intel Assembler, PL/I and PL1, Pascal, Basic, C plus numerous job control and scripting languages.
My personal scorecard is now 1 PC hardware fix (circa 1982), 1 open source fix (at age 82), and 2 zero day bugs in a major OS.
MD_Parola P = MD_Parola(HARDWARE_TYPE, DATA_PIN, CLK_PIN, CS_PIN, MAX_DEVICES);
@fhaddad OK, no problem, we all need time to learn. If I may add a new lesson for today, use the Reply link so that the person you are talking to is notified. It is at the bottom right of the post you are reading. If it's a short post, feel free to use the Quote link that is right beside the Reply link.
As far as your mistake, that is probably what I would have done, too. At least fixing a booboo and resubmitting the compile is a few seconds or minutes; when I was a newbie, it was from a few hours to overnight, and that is after writing the code on a specially formatted pad and then submitting it to the keypunch pool. It's a miracle we could ever complete those big systems back then (early 70's)
First computer 1959. Retired from my own computer company 2004.
Hardware - Expert in 1401, and 360, fairly knowledge in PC plus numerous MPU's and MCU's
Major Languages - Machine language, 360 Macro Assembler, Intel Assembler, PL/I and PL1, Pascal, Basic, C plus numerous job control and scripting languages.
My personal scorecard is now 1 PC hardware fix (circa 1982), 1 open source fix (at age 82), and 2 zero day bugs in a major OS.