forum.pistar.uk

Here's the output of pistar-findmodem: Detected MMDVM_HS (GPIO): /dev/ttyAMA0 (MMDVM_HS_Dual_Hat-v1.4.14 20181209 14.7456MHz dual ADF7021 FW by CA6JAU GitID #8d77ff3) Another oddity - when I first boot, dash/admin don't show fw/tcxo. Then something (don't know what) happens and it appears. Re-boot a...

modem is an N5BOC duplex, pistar-findmodem does return a typical string. I can't figure out how to copy from expert mode ssh into the web browser window for this forum (and I don't feel like typing the whole darn thing

3.4.17 20190526 dashboard

fw version and tcxo info is missing

http://www.pistar.uk/beta/

I'm running it on a P3B+ and it works fine.

Another modification I happened upon is to remove (de-solder) the pins that come in the screen and replace with right-angle ones. Together with a GPIO shim (sold by HRO) this would lower the profile of the screen. But still a couple problems with this - when using a case you need to find a way to ge...

The examples of a .96 OLED on a ZUMspot I've seen have use wires between the two since it appears that the GPIO header positions aren't contiguous so you can't just position the screen's pins over the GPIO and solder. And no C4Labs case.

Screen position over the board is especially important if you want, for example, to install a ZUMspot on a Pi0W with a .96 OLED screen all in a ZRZ-1S case from C4Labs.

I'd be interested in hearing from someone who did the above configuration.

The .96in OLED screens I've found have 4 pins at .1in spacing Depending on the MMDVM board, the OLED header can be either wired to the STM32 chip or the GPIO header. Since the software (MMDVMHost and/or MMDVM firmware?) does not support OLED, if wired to the STM32 the OLED header is not functional. ...

Typo and/or poor memory.

Yes, should be 0.4 and 0.5

Will edit and correct, thanks.

Sent from my VS995 using Tapatalk

0.5 is current. HRO sold me a 0.4

What's the difference?

Sent from my VS995 using Tapatalk