forum.pistar.uk

I have TG #1234 defined as static. Listen to #1234 just fine for extended period. As soon as I make my first transmission, #1234 shows as a dynamic group. After 15 minutes with no more transmissions, #1234 no longer shows as dynamic Any idea why BM does this? There's no need to add it as dynamic whe...

I see you answered this over on another thread. Never mind.

Is it my imagination, or has it been in beta for a really long time? And 4.0 never came out of beta?

Thanks Toshen

I misread the file names there as 4.0 not 4.1, sorry.

Where are the files for RC5 and RC6? Or haven't they been released for general consumption.

Were any versions of 4.0 or 4.1 ever released or are they all still beta?

Where are the 4.1 files located for download?

Starting update, please wait... Stopping Services... Done Updating DV Binaries... No updates for /usr/local/bin available Done Updating Pi-Star Binaries... error: bad signature fatal: index file corrupt Updating /usr/local/sbin... error: bad signature fatal: index file corrupt error: bad signature f...

Is V4 still beta?

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.

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

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.