|
|
Post by oregonron on Jul 24, 2016 6:56:51 GMT -7
I downloaded the 2.1 version of Commander and configured it using an external monitor and keyboard as opposed to using VNC. I discovered some data would not save and thus unit would not work. Some data did save so its weird to find this out. Never had issue doing it this way with Maryland firmware. I was able to get everything working but only by using VNC viewer. Anyone else notice this?
|
|
AA7US
New Member
Posts: 41 
|
Post by AA7US on Jul 24, 2016 7:40:57 GMT -7
I downloaded the 2.1 version of Commander and configured it using an external monitor and keyboard as opposed to using VNC. I discovered some data would not save and thus unit would not work. Some data did save so its weird to find this out. Never had issue doing it this way with Maryland firmware. I was able to get everything working but only by using VNC viewer. Anyone else notice this? Can you provide more details on exact which configuration you had trouble with saving? By chance was it when you were attempting to alter and save the configuration of the D-Star Repeater and / or the ircDDB Gateway apps? If yes, I've encountered this when phenomenon also when using VNC (which is the only way I have to access my RPi's). It is an intermittent problem and doesn't happen all the time. When it does happen, I've simply modify the configuration files directly using a text editor (nano), which I realize may not advisable, but it has worked well for me. Regards, John AA7US |
|
|
|
Post by W6KD on Jul 24, 2016 9:13:44 GMT -7
Usually if data is not saved when using the ircddbgatewayconfig or dstarrepeaterconfig programs (the two config icons on the desktop) it's because you didn't close the program before making changes. You have to close the ircddbgateway and/or dstarrepeater program(s) first before running the config program, or changes may not save properly.
Regards
|
|
AA7US
New Member
Posts: 41
|
Post by AA7US on Jul 24, 2016 9:17:09 GMT -7
Hi Bob,
I suspected that may be the problem.
Thanks,
John
AA7US
|
|
|
|
Post by oregonron on Jul 24, 2016 14:23:49 GMT -7
I had this problem yesterday configuring my DVAP/DHAP. Today I tried the same thing using DVMEGA/DHAP. I have tried this two ways, using a monitor and bluetooth keyboard as well as using VNC Viewer. In almost all cases the mega will not work and looses data saved. I always only have one function selected such as gatewayconfig. I put data in, then save it. Once dvmega reboots data is back to default values. Much worse of a problem on the dvmega than dap. Basically just does not work where as using the Maryland image causes no problems. Since I like the commander software better I would like to find a solution. I have spent hours repeating these steps and am convinced at this point I am not making an error. Appears to be a bug to me. Any help is appreciated. Thank You
|
|
|
|
Post by W6KD on Jul 24, 2016 20:54:22 GMT -7
I always only have one function selected such as gatewayconfig. I put data in, then save it. Once dvmega reboots data is back to default values. Only have one function selected...uh, what? Sorry, but I have no idea what this means. To reiterate, if the ircddbgateway or dstarrepeater window is visible on the desktop while you are making changes to the respective program's settings (IOW the program is running), the changes usually do not save out properly. You have to first close the ircddbgateway program before opening the ircddbgateway config program, and close the dstar repeater program before running the DStar Config program via the icon on the desktop. Regards |
|
|
|
Post by oregonron on Jul 25, 2016 2:20:31 GMT -7
I believe I understand. I close down all the screens such that only the icons for each program is visible on the screen. Then I go in to one of them such as DStar Config, one by one, entering parameters, saving data, then exiting each one. Only one screen is open and visible on the screen at any given time. If I go back in, I see changes have been made but when I reboot the pi, I continue to loose data, such as my callsign. This happens using vdc viewer and/or just using a keyboard/monitor connected to the DHAP. The two worst modules doing this are: D-star config and gateway config, where the wifi section seems to retain and save data correctly. I hope I have made this clear and its a very frustrating problem keeping the mega from running. With the Maryland images, this problem does not occur and no data is being lost using either VNC viewer or DHAP/keyboard/monitor on the mega. Has anyone else seen this problem and why would this happen especially using DHAP/keyboard/monitor on the mega, makes no sense to me as the problem here is consistent.
|
|
AA7US
New Member
Posts: 41
|
Post by AA7US on Jul 25, 2016 12:18:33 GMT -7
...I see changes have been made but when I reboot the pi, I continue to loose data, such as my callsign... Questions: How are you rebooting the RPi? You specifically mentioned your callsign being lost, but what about all the other parameters you changed? Are they being retained? Have you made any other alternations to the RPi's OS and/or added any other programs? Besides using the D-Star Repeater Config and Gateway Config programs, have you made any other configurations changes anywhere in the RPi? Thanks, John AA7US |
|
|
|
Post by W6KD on Jul 25, 2016 12:31:21 GMT -7
Did you try setting the configuration using the included DStarConfig.exe program on your PC when you flashed the image? That's generally the easiest way to set things up.
Regards
|
|
AA7US
New Member
Posts: 41
|
Post by AA7US on Jul 25, 2016 12:36:06 GMT -7
Ron,
FYI, I just tested making and saving some changes using the Gateway Config program on my RPi 3B / DVMega running D-Star Commander 2.01 and had no problems with retention, even after rebooting.
As W6KD Bob suggested, maybe first try setting things up on the SD card using the MS Windows compatible program and THEN once you're sure everything is working properly, VNC in to your RPi and try some changes using the D-Star Repeater Config and Gateway Config programs.
Good luck,
John
AA7US
|
|
|
|
Post by oregonron on Jul 27, 2016 8:53:37 GMT -7
I did everything as everyone suggested and finally got it working, rebooting by not pouring off raspberry seemed to help the most, all is okay now! Thanks
|
|
