OpenGD77

Hi Marc,

kd2lh wrote: ↑

Sun Jan 26, 2020 12:04 am

The connectors were solidly connected, and the room was isolated with nobody in there until I came in later this afternoon and noticed the GD77 display was back on 146.52 analog (what the radio defaults to).

I did not witness the GD77 reboot, only the aftermath.

Okay. So, it's a bit hard to guess what did happened, because it could be reboot or USB disconnection/reconnection (as ttyACM number changed). Hmmm.

Cheers.
---
Daniel

Thank you Roger, (and thank you Daniel for all version updates

73 de Paolo IV3BVK

Hi, The reset and lockup has happened again at least three times today. Host is a Pi Zero W.

I was listening to Roger during the most recent lockup, but not at the radio / hotspot to see what happened at the time.

In the middle of an incoming conversation, audio stopped, and the PiStar dashboard froze in TX with Trx showing "TX DMR Slot 2" with red "TX" still in the Duration field.

I found the radio back at the default GD77 VHF frequency - not in HotSpot mode.

The radio with transmit when keyed with the button on the side, so the firmware is live and running.

The livelog shows nothing, just the last Talker ID packets from Roger's conversation.

I'll reset Pistar without repowering the radio to see if it starts up again.

First I'm trying "Update" to stop and restart MMDVMHost.

This does not set the GD77 back to hotspot mode, and this is in livelog:

M: 2020-01-26 23:12:35.636 Opening the MMDVM
E: 2020-01-26 23:12:35.636 Cannot open device - /dev/ttyACM0

Now using power reboot button on Pistar:

This reloaded PiStar and MMDVMHost was able to put the GD77 into hotspot mode. It picked right up with the next incoming transmission (again from Roger on TG98977).

Note that I did not have to recycle power on the GD77.

So, are we doing something that is overrunning the USB interface on the Raspberry Pi?

I don't have hardware USB trace equipment to monitor this with.

Marc

Marc

I've emailed you the link to the version of MMVMHost exe I complied

I've actually uploaded another copy where I've removed my ID so that I can post the link here and people won't accidentally connect as me

https://drive.google.com/open?id=18XGg7 ... OHu_Tacsrl

Another lockup this morning. Likely a firmware reboot in the middle of handling incoming voice data from a Brandmeister talk group.

Hi Marc,

kd2lh wrote: ↑

Mon Jan 27, 2020 2:08 pm

Another lockup this morning. Likely a firmware reboot in the middle of handling incoming voice data from a Brandmeister talk group.

Okay. That's explain the reason of the MMDVMHost lockup.
Now, why ...

Cheers.
---
Daniel

Noticed that after a call has ended, the next incoming call first gets identified with the last call sign, and then quickly gets updated to the current incoming call sign.

This should be blank until the current call lookup has completed.

It is blank between incoming calls.

I just ran a video on the failure. I'll open a new bug.

It appears that the GD77 is rebooting itself in the middle of incoming VOIP packets from 98977 Brandmeister group id.