OpenGD77

thank you

I'm not sure if it's the level of activity, but the PiStar Raspberry Pi is running warmer than normal at: 51.9°C / 125.4°F

Operation continues without interruption.



2/5/2020 22:05 EST Now at about 8 hours without problem. Thermal back to normal.

2/6/2020 11:00 EST continues operating without problems. Calls to the parrot continue to operate correctly without cutting off the end of the conversation.

2/6/2020 19:05EST another 8 hours without problems. I think that this cache level is probably adequate.

Hi Marc,

kd2lh wrote: ↑

Wed Feb 05, 2020 8:41 pm

I'm not sure if it's the level of activity, but the PiStar Raspberry Pi is running warmer than normal at: 51.9°C / 125.4°F

Operation continues without interruption.



2/5/2020 22:05 EST Now at about 8 hours without problem. Thermal back to normal.

2/6/2020 11:00 EST continues operating without problems. Calls to the parrot continue to operate correctly without cutting off the end of the conversation.

Okay. So I guess I can raise a PR with this latest version of the hotspot code. I'll do that tomorrow.

Once again, many thanks for all the tests you've made , really appreciated.

Cheers.

Well, I just raised the PR

Cheers.
---
Daniel

Good. Stabilizing this and completing the CWID support should make it completely functionally viable as a HotSpot.

I still have not heard back from Radioddity's lab with confirmation of their duty cycle testing - if they are doing it - so we probably should recommend limited power usage on these. It's cool to the touch with a fairly high percentage of transmit operation at 1 watt. I don't think I want to do destructive testing myself so will keep at this power level for now.

I've just switched over to the faster Raspberry Pi4B, and connected through one of the USB2 ports. We'll continue to hit it with the 3100 talkgroup activity.

I noticed loss of conversation after the first few packets a couple of times with one person I was talking with. They continued to be transmitted on the GD-77, but my XPR7550e stopped receiving. I believe that this is a known issue relating to bit settings in the voice packets.

Marc

Daniel, What's the best way to determine which general release from Roger incorporates changes after you release them?

When will these changes commit and be included in the general build?

Thanks again for your work.

BTW, this remains running stable on the Pi4B USB2 ports. It's now about 12 hours.

Hi Marc,

kd2lh wrote: ↑

Fri Feb 07, 2020 12:25 pm

Daniel, What's the best way to determine which general release from Roger incorporates changes after you release them?

When will these changes commit and be included in the general build?

Thanks again for your work.

BTW, this remains running stable on the Pi4B USB2 ports. It's now about 12 hours.

Well, Roger enumerates the changes when he post a new firmware build.
This morning, he published a released with the latest hotspot code (I bumped the version number to 0.1.0).
I try to increment the HS version number each time I make a significant modification into the code, just to be sure about the version users are running when they report a problem.

So, you can go ahead and update your radio with the today release


Cheers.
---
Daniel