Newbie Question...
Posted: Sun Oct 03, 2021 12:10 pm
OK, new to all of this, here's the setup:
Raspberry Pi 3B
Generic Chineesium MMDVM_HS_HAT_DUPLEX modem board from eBay
C4LABS case
Nextion NX3224K024 Display
I've had the Pi for years, never did more than run different versions of Raspbian on it and fool around. Recently purchased two ICOM ID-31A HT's at the Shelby Hamfest (MONSTER deal, paid $100 for the pair!) only to find out that there's a total lack of D-Star infrastructure in the area. I initially purchased a couple of simplex hotspots from a different eBay vendor (a whole different fiasco) then purchased the Duplex board. I slapped it on the
Pi 3B and installed Pi-Star. Off to the races! The learning curve was a bit steep at first but now I've got a basic handle on things. I've made several contacts via D-Star and YSF so the modem is happy. A few days pass, and my case and screen show up. Now comes the hair-pulling... The display powers up fine, but all I can get out of it is the "demo" stuff. I've read enough posts here and other places to sink a battleship, all to no avail. Yes, I've got the right modem selected in Pi-Star, I even tried selecting a few wrong ones just to see what happened. I've tried all of the display combinations in Pi-Star several times over, still no dice. I've wiped and reinstalled Pi-Star half a dozen times to make sure none of my futzing around corrupted anything. I even tried switching the TX and RX lines between the modem and display since I got conflicting information as to whether or not to cross them. (I'm old enough to remember needing crossover ethernet cables in some situations and built a bunch of them in the day.) At this point I can't say if the modem, display, or software is to blame. It just may be the loose nut behind the keyboard, I'm man enough to admit that too. I don't have another MMDVM board or display to swap out to eliminate or blame either of those.
I've been a professional auto and light truck mechanic for over thirty years, and I'm pretty good at diagnosing and repairing electronic systems, but a lack of diagnostic equipment and spare parts has me stumped. I have no way of testing for data transfer between the Pi, the modem, and the display. I've got a feeling that's where my issue is, either the data isn't getting thru, or some part of the system isn't doing what it should with that data once it gets there.
Anybody got a suggestion, before I pull out what hair I have left?
Raspberry Pi 3B
Generic Chineesium MMDVM_HS_HAT_DUPLEX modem board from eBay
C4LABS case
Nextion NX3224K024 Display
I've had the Pi for years, never did more than run different versions of Raspbian on it and fool around. Recently purchased two ICOM ID-31A HT's at the Shelby Hamfest (MONSTER deal, paid $100 for the pair!) only to find out that there's a total lack of D-Star infrastructure in the area. I initially purchased a couple of simplex hotspots from a different eBay vendor (a whole different fiasco) then purchased the Duplex board. I slapped it on the
Pi 3B and installed Pi-Star. Off to the races! The learning curve was a bit steep at first but now I've got a basic handle on things. I've made several contacts via D-Star and YSF so the modem is happy. A few days pass, and my case and screen show up. Now comes the hair-pulling... The display powers up fine, but all I can get out of it is the "demo" stuff. I've read enough posts here and other places to sink a battleship, all to no avail. Yes, I've got the right modem selected in Pi-Star, I even tried selecting a few wrong ones just to see what happened. I've tried all of the display combinations in Pi-Star several times over, still no dice. I've wiped and reinstalled Pi-Star half a dozen times to make sure none of my futzing around corrupted anything. I even tried switching the TX and RX lines between the modem and display since I got conflicting information as to whether or not to cross them. (I'm old enough to remember needing crossover ethernet cables in some situations and built a bunch of them in the day.) At this point I can't say if the modem, display, or software is to blame. It just may be the loose nut behind the keyboard, I'm man enough to admit that too. I don't have another MMDVM board or display to swap out to eliminate or blame either of those.
I've been a professional auto and light truck mechanic for over thirty years, and I'm pretty good at diagnosing and repairing electronic systems, but a lack of diagnostic equipment and spare parts has me stumped. I have no way of testing for data transfer between the Pi, the modem, and the display. I've got a feeling that's where my issue is, either the data isn't getting thru, or some part of the system isn't doing what it should with that data once it gets there.
Anybody got a suggestion, before I pull out what hair I have left?