tcxo info missing

[KC3MLA]

3.4.17 20190526 dashboard

fw version and tcxo info is missing

[KC3MLA]

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

[w7efs]

... I can't figure out how to copy from expert mode ssh into the web browser window for this forum ...

Highlight the text you want to copy, then Ctrl-C. Change to the reply window, select the </> icon above then Ctrl-V.

[MW0MWZ]

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

What does pistar-findmodem return ?

[KC3MLA]

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 and it goes away again.

[KC3MLA]

So just now it was sitting with no FW/TCXO info showing on the admin dashboard. I went over to config/expert/ssh to run pistar-findmodem.

When I returned to the admin dashboard, poof! there the fw/tcxo was.

[KC3MLA]

Tried to reproduce by booting, verifying absence of fw/tcxo info, then going to config/expert/ssh and logging in/out. Not enough to make fw/tcxo info appear on dashboards.

So far I've had to actually execute pistar-findmodem while ssh'ed in for fw/fcxo into to appear when returning to dashboard

[w7efs]

Have you saved the configuration, re-burned a fresh Pi-Star image to the same card and restored the configuration? It sounds like something isn't quite right there somehow.

[KC3MLA]

Thought about it. But the 3.n version I have is a bit old, and I don't want to run 4.0 until it's out of beta.

Also seems like the nightly update messes it up, too.

[w7efs]

That was our delay in running v4rc4 too, but last weekend I made a trip to the remote site for something else and swapped microSD cards from v3.4.17 to v4rc4 just so we had an upgrade path. So far the only problem observed was that the D-Star Configuration "Time Announcements:" reloaded as "enabled", but that was easily changed remotely.