OpenGD77

kd2lh wrote: ↑

Sun Feb 02, 2020 1:52 pm

The 0.87.1 experimental firmware has continued to operate without problem for 23 hours.

About 8 hours ago, I switched a very busy talkgroup (3100) static linked onto the hotspot, so there has been considerable activity load from Brandmeister.

So far, no lockups with USB on the PiZero W.

The CWID message on screen is a great enhancement to. Confirms operation.

Marc

Thanks Marc for all the report. I'm also happy to read that you don't have any more lockup/reboot problems.
I will finish what I'm doing right now, and raise a PR with the modifications you're using at the moment.

Cheers.
---
Daniel

Where can I find this great, praised version 0.87.1?
I am asking for a hint.

The link to .0.87.1 is earlier in this thread:

https://www.opengd77.com/viewtopic.php? ... t=30#p4892

Note that it is down on some of the features issued in Roger's last firmware. When Daniel releases the changes I've been testing, there will be a more formal release with Roger's latest changes and Daniel's work merged.

Marc

So far, 0.87.1 continues to run without rebooting.

I think it's periodically dropping voice packets in the middle of conversations, and not recovering until the subsequent transmission by another caller into the talkgroup. This could be triggered by IP errors at the remote end interrupting things, but then the transmitter of the hotspot stays off while TX remains "TX" Red on the dashboard for a period of time. Finally another ham initiates conversation and things start back up again.

Marc

Just testing 31 January 2020 experimental firmware. Is it normal now for the receive screen not to show DMR ID: XXXXXXX ? It appears that the DMR ID of the station currently being received is no longer displayed? The only way I can see this information is by going into last heard menu.

Is this how it should be?
Thanks

G0NHF wrote: ↑

Mon Feb 03, 2020 12:03 am

Just testing 31 January 2020 experimental firmware. Is it normal now for the receive screen not to show DMR ID: XXXXXXX ? It appears that the DMR ID of the station currently being received is no longer displayed? The only way I can see this information is by going into last heard menu.

Is this how it should be?
Thanks

There are some bugs in the DMR ID handling, which are currently being fixed.

Still up and running, but I noticed some strange behavior in trace. The hotspot had been idle for about an hour, and I made calls to the parrot through it. This generated a number of "RF User 0 rejected" errors. It happened both times I called.

M: 2020-02-03 02:37:00.049 DMR Slot 2, RF user 0 rejected
M: 2020-02-03 02:37:00.103 DMR Slot 2, RF user 0 rejected
M: 2020-02-03 02:37:00.406 DMR Slot 2, RF user 0 rejected
M: 2020-02-03 02:37:00.465 DMR Slot 2, RF user 0 rejected
M: 2020-02-03 02:37:00.710 DMR Slot 2, received RF voice header from KD2LH to 9990
M: 2020-02-03 02:37:06.529 DMR Slot 2, RF voice transmission lost from KD2LH to 9990, 5.4 seconds, BER: 1.2%, RSSI: -70/-70/-70 dBm
M: 2020-02-03 02:37:10.500 DMR Slot 2, received network voice header from 9990 to KD2LH
M: 2020-02-03 02:37:15.843 DMR Slot 2, received network end of voice transmission from 9990 to KD2LH, 5.5 seconds, 0% packet loss, BER: 0.0%
M: 2020-02-03 02:37:23.445 DMR Slot 2, RF user 0 rejected
M: 2020-02-03 02:37:23.505 DMR Slot 2, RF user 0 rejected
M: 2020-02-03 02:37:23.807 DMR Slot 2, RF user 0 rejected
M: 2020-02-03 02:37:23.868 DMR Slot 2, RF user 0 rejected
M: 2020-02-03 02:37:23.988 DMR Slot 2, received RF voice header from KD2LH to 9990
M: 2020-02-03 02:37:28.370 DMR Slot 2, RF voice transmission lost from KD2LH to 9990, 4.1 seconds, BER: 1.5%, RSSI: -70/-70/-70 dBm
M: 2020-02-03 02:37:32.461 DMR Slot 2, received network voice header from 9990 to KD2LH
M: 2020-02-03 02:37:36.485 DMR Slot 2, received network end of voice transmission from 9990 to KD2LH, 4.2 seconds, 0% packet loss, BER: 0.0%

The end of the parrot response is also cut off even though the red TX stays on in PiStar the entire length of the response time.

Firmware- 0.87.1 HotSpot mode continues to operate without interruption, including considerable Brandmeister group activity.

It's now been 48 hours without a reboot.

I have had occasional situations where PiStar desktop is left in "TX" mode, but the transmitter in the GD77 is off.

This does not interrupt further operation locally. I am able to call the hotspot, and I appear on the PiStar Desktop. At the close of my call, the red "TX" for the prior call resets.

PiStar's interaction with Brandmeister seems to have failed at this point, even though DMR and DMR Net are in Green. I'm rebooting.

Hi Marc,

I've build a version based on master branch, including the modifications you're using, plus some cleanup, like sharing the same USB buffer as the CPS communication uses.
I'm testing it at the moment, and once I don't see any huge problem with it, I'll upload this version here, if you want to test it.

Thanks for all the long tests and nice reports you've made.

Cheers.
---
Daniel

F1RMB wrote: ↑

Tue Feb 04, 2020 8:47 am

...
I've build a version based on master branch, including the modifications you're using, plus some cleanup, like sharing the same USB buffer as the CPS communication uses.
...

Daniel, does it mean that you have included changes in "latest" FW from today, plus your additions?

Thanks!