|
|
Post by Mark - G0TOV on Mar 22, 2016 13:52:13 GMT -7
Hello Bob, and of course anyone else who may have the answer....
Suddenly today the RF commands have stopped operating on both of my DVMega's using the Commander Image. Upto now I have tried two DVMega units (both have the same V1.21 images) using three radios, IC7100 (Home), ID51E and the IC2820 in my car - I have just run a brand new image onto a card and this too doesn't work, on either Mega.
Nothing has changed upto today, in fact upto now everything has worked perfectly. I simply sent a HOSTUPDT in the car this afternoon, only because I hadn't done it for a while and I didn't get the response back after a few minutes of "Not Linked". I then issued a REBOOT and the unit didn't reboot. Sat here in the shack now and when I issue the commands from the 7100 all I see on the screen in the log section is "G0TOV is trying to G2 route to callsign HOSTUPDT"
Any ideas please ? Thank you.
Regards,
Mark.
G0TOV
|
|
|
|
Post by W6KD on Mar 22, 2016 18:14:18 GMT -7
What do they share in common? Router perhaps? If I have multiple networked devices start misbehaving at the same time, a router restart is generally a good starting point. If there's no internet connectivity at boot, then the RasPi can't get to the internet time server to set the time (the Pi has no RTC). This can cause the DStar Commander command interpreter to stop working.
Regards
|
|
|
|
Post by Mark - G0TOV on Mar 23, 2016 15:22:09 GMT -7
Hello Bob, latest update for you now that I have made some progress.
Situation is, connects to DCS and REF's okay - both car and home units.
Issue is the REBOOT, SHUTDOWN, HOSTUPDT commands do not function. The FTP site for the Host Update doesn't appear to be online, if I try to get to it via a PC it doesn't respond so i guess this could be the issue with the host update.
Additionally and if it helps, a friend of mine who also uses the commander image too that I setup for him reports his RF commands have also failed to function tonight, he lives around 40 miles away from me with his own equipment so there is no connection to my equipment here, in case you were going to ask :-)
Very strange, for both of us up until yesterday everything was working perfectly.
Any ideas at all ?
Regards,
Mark.
|
|
|
|
Post by va3twt on Mar 24, 2016 11:37:40 GMT -7
RF commands are not working for me either. I'll keep monitoring the forum to see if a fix becomes available.
73
Gord - VA3TWT
|
|
|
|
Post by Mark - G0TOV on Mar 24, 2016 12:26:32 GMT -7
Thanks Gord, as I said to you on email earlier I wonder if something on the network has changed as this is now affecting four of us, maybe more we don't know about.
@bob - I have run up a Western image today and same issue, RF commands don't work on their version either which is why I am thinking this is more a global problem and certainly not an issue isolated to Commander. I noted on a previous post you had advised to check the RF commander was running, I have run the sudo pgrep Python command and the system returned a value of 2325.
Appreciate any advice Bob, we all just want our Commander image back :-)
Regards,
Mark.
|
|
|
|
Post by W6KD on Mar 24, 2016 18:47:02 GMT -7
K5YOL--the primary hostfile server was down, but the backup (which is sited in the Amazon cloud) was still working, so DSC should have fallen back to that for the hostfile update. That shouldn't explain RF commands other than the HOSTUPDT failing, in any event. Have you done any kind of updates on the Pi (i.e. apt-get update or upgrade)? If so, it's possible a driver update could have broken something, which is why I discourage running software updates on the image. You could try running the CLEANUP command and rebooting to clear out the old log files...I suppose it's possible (but not likely) that the 3.8GB of image space is filling up with accumulated log files. You can also run sudo raspi-config and select the option to expand the file system to use all of the space available on the SD card if you haven't done that already. I've tested things on both the dvMega and DVAP variants of V1.21, and cannot duplicate the issue. Regards
|
|
|
|
Post by Mark - G0TOV on Mar 25, 2016 2:46:25 GMT -7
Hello Bob - firstly, thank you. Everything now seems to be back to normal for some strange reason - my friend over in Canada also reports to me his RF commands are now back and working too. My system at home and in the car (separate Pi's) are both working again.
To answer your questions though, I have done no updates no - Respect the fact you have disabled the Klxupdater and why, so no. I have run the cleanup command this morning on both systems and all okay - I tend to do this randomly to avoid this very issue as with the Host update, which is where all this started - those commands didn't do anything.
I was puzzled as to why the RF commands wouldn't be simply local commands between the radio and Pi but my knowledge is limited in comparison so I was just curious as to how these worked, it seemed to call out to the gateway, the primary hostfile server is back online and so the RF commands now work again, coincidence maybe !
As it stands now everything is back to normal, thanks again for your assistance and great work you do on the Commander image for the benefit of us all, it is appreciated.
Regards,
Mark.
|
|
|
|
Post by W6KD on Mar 25, 2016 10:22:22 GMT -7
OK Mark, thanks. I don't believe in coincidences, though, so I will continue to look into this as I test V2.0 (built on a new Linux variant with Pi3 compatibility).
Regards
|
|
|
|
Post by Mark - G0TOV on Mar 25, 2016 14:18:11 GMT -7
Hello Bob, well it is appreciated thanks. I guess only you know whether the RF commands reach out to the network or not, this is where my thoughts of a coincidence came from, as soon as the server came back online the RF commands started working, my simple logic suggested they must. As for the Pi3 image that would be great, one of my friends has the Commander image I set up for him but has just bought a Pi3 and of course I had to use the Western image for him until you had made a compatible version available so I'll keep an eye out for the release.
Regards,
Mark.
|
|
|
|
Post by Mark - G0TOV on Mar 30, 2016 6:07:58 GMT -7
Hello Bob, taking into account the email my friend Chris (M0LZA) has sent you then you were absolutely correct not to believe in coincidences! It seems the other RF commands were always working but just that the default timeout of 900s hadn't passed so it gave the impression that Reboot / Shutdown etc were also non operational - this answers why sometimes Reboot worked and sometimes it didn't. Issue the Hostupdt command, which didn't work due to the server being offline, then wait 900s and the others would work - of course until Chris looked at the files we would never have known this - you live and learn as they say. Thanks again, great work.
I recently overheard a chap on air saying he was having terrible trouble trying to get his image to work, (whatever it is I don't know) seems he has been "pulling his hair out" for some time and lost patience, anyway suffice to say his kit has landed with me today and he will be getting the "commander" image tonight set up for him! We are promoting you where we can :-)
Regards. Mark.
|
|
|
|
Post by W6KD on Apr 2, 2016 13:59:31 GMT -7
The hostfile server timeout has been addressed in V2.00, which has just been released.
Regards
|
|
