Experimental Baofeng RD-5R version
Re: Experimental Baofeng RD-5R version
I don't know if it will be a complete file.
- Attachments
-
- Pi-Star_MMDVM-2020-05-12.zip
- (1.52 KiB) Downloaded 149 times
Re: Experimental Baofeng RD-5R version
I just see the beginning of a network receive, but it stops too early.
Code: Select all
M: 2020-05-12 10:38:35.989 DMR, Logged into the master successfully
M: 2020-05-12 10:40:17.682 DMR Slot 2, received network voice header from SQ6JAR to TG 260
M: 2020-05-12 10:40:17.756 DMR Talker Alias (Data Format 3, Received 3/8 char): 'JAR'
M: 2020-05-12 10:40:17.756 DMR Slot 2, Embedded Talker Alias Header
M:
Cheers.
---
Daniel
Re: Experimental Baofeng RD-5R version
Unfortunately, I tried many times and each time after the last entry the hotspot switches to radio operation. Each first incoming call immediately turns off the hotspot and continues to work as a radio.
- Attachments
-
- Pi-Star_MMDVM-2020-05-12.zip
- (1.49 KiB) Downloaded 163 times
Re: Experimental Baofeng RD-5R version
Okay, so something make MMDVMHost unhappy.
Have you updated your Pi-Star in the last two days, I see Andy updated the MMDVMHost binary, and a patch from myself has been introduced on Saturday, which can help here, maybe. If you have already updated to the latest, which means Andy is not up to date for MMDVMHost, I will give you another procedure to follow to try to catch what is happening.
Cheers.
---
Daniel
Re: Experimental Baofeng RD-5R version
Hi,
In case the Pi-Star doesn't have the up-to-date version of MMDVMHost, here is a small procedure to catch more errors:
ssh to you Pi-Star, then type:
then:
If there is no ERROR message:
Once the hotspot has exited (or by pressing <Control>-<C>):
Now, zip and post the file here.
Once it's okay, just reboot your Pi-Star.
Cheers.
---
Daniel
In case the Pi-Star doesn't have the up-to-date version of MMDVMHost, here is a small procedure to catch more errors:
ssh to you Pi-Star, then type:
Code: Select all
sudo su
then:
Code: Select all
rpi-rw; cp /etc/mmdvmhost /root/mmdvmhost.backup && (systemctl stop mmdvmhost.timer; systemctl stop mmdvmhost.service; sed -i 's/^Daemon=1/Daemon=0/g' /etc/mmdvmhost; sed -i 's/^DisplayLevel=0/DisplayLevel=2/g' /etc/mmdvmhost) || echo ERROR
If there is no ERROR message:
Code: Select all
/usr/local/bin/MMDVMHost /etc/mmdvmhost > /tmp/mmdvm.log 2<&1
Once the hotspot has exited (or by pressing <Control>-<C>):
Code: Select all
rpi-rw; cp /root/mmdvmhost.backup /etc/mmdvmhost; rpi-ro
Now, zip and post the file here.
Once it's okay, just reboot your Pi-Star.
Code: Select all
reboot
Cheers.
---
Daniel
Re: Experimental Baofeng RD-5R version
Whether it is sending the same log file as before or another one.F1RMB wrote: ↑Tue May 12, 2020 1:16 pmHi,
In case the Pi-Star doesn't have the up-to-date version of MMDVMHost, here is a small procedure to catch more errors:
ssh to you Pi-Star, then type:Code: Select all
sudo su
then:Code: Select all
rpi-rw; cp /etc/mmdvmhost /root/mmdvmhost.backup && (systemctl stop mmdvmhost.timer; systemctl stop mmdvmhost.service; sed -i 's/^Daemon=1/Daemon=0/g' /etc/mmdvmhost; sed -i 's/^DisplayLevel=0/DisplayLevel=2/g' /etc/mmdvmhost) || echo ERROR
If there is no ERROR message:Code: Select all
/usr/local/bin/MMDVMHost /etc/mmdvmhost > /tmp/mmdvm.log 2<&1
Once the hotspot has exited (or by pressing <Control>-<C>):Code: Select all
rpi-rw; cp /root/mmdvmhost.backup /etc/mmdvmhost; rpi-ro
Now, zip and post the file here.
Once it's okay, just reboot your Pi-Star.Code: Select all
reboot
Cheers.
---
Daniel
I have a question, is there a difference if I use the same pi-star for GD-77, because I worked with that without a problem.
Re: Experimental Baofeng RD-5R version
It could be different, as some errors aren't logged by older MMDVMHost.
Yes, it's identical, it's the same Hotspot code. But it would be nice to know why you have a problem with this one, e.g is it a problem with some parameter, or corrupted SD Card, etc..
Cheers.
---
Daniel
Re: Experimental Baofeng RD-5R version
I can't understand it either. Practically, the radio works as a hotspot until the first user appears and in the first second the hotspot function is interrupted and the correspondent can no longer be heard, although it can still talk, because I can hear on another radio and another hotspot.
In addition, from what I noticed, despite the fact that the dashboard shows broadcasting (Tx shines red), in fact the RD-5R is not transmitting anything (sporadically it transmits, but very briefly) and immediately goes to radio.
In addition, from what I noticed, despite the fact that the dashboard shows broadcasting (Tx shines red), in fact the RD-5R is not transmitting anything (sporadically it transmits, but very briefly) and immediately goes to radio.
Re: Experimental Baofeng RD-5R version
I use my RD-5R only for testing purpose and also tried to use the hotspot mode. Same situation here. With the first transmission, the hotspot mode stops. I don't think that the MMDVMHost service is the problem. It is the USB connection, as the syslog states:
Code: Select all
Mai 17 16:16:31 raspitest kernel: cdc_acm 1-1.2:1.0: ttyACM0: USB ACM device
Mai 17 16:16:31 raspitest mtp-probe[1186]: checking bus 1, device 5: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2"
Mai 17 16:16:31 raspitest mtp-probe[1186]: bus: 1, device: 5 was not an MTP device
Mai 17 16:16:31 raspitest mtp-probe[1187]: checking bus 1, device 5: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2"
Mai 17 16:16:31 raspitest mtp-probe[1187]: bus: 1, device: 5 was not an MTP device
Mai 17 16:17:06 raspitest systemd[1]: Starting MMDVMHost Service...
Mai 17 16:17:08 raspitest systemd[1]: Started MMDVMHost Service.
Mai 17 16:18:43 raspitest kernel: usb 1-1.2: USB disconnect, device number 5
Mai 17 16:18:43 raspitest kernel: cdc_acm 1-1.2:1.0: failed to set dtr/rts
Mai 17 16:18:43 raspitest kernel: usb 1-1.2: new full-speed USB device number 6 using xhci_hcd
Mai 17 16:18:43 raspitest kernel: usb 1-1.2: New USB device found, idVendor=1fc9, idProduct=0094, bcdDevice= 1.01
Mai 17 16:18:43 raspitest kernel: usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Mai 17 16:18:43 raspitest kernel: usb 1-1.2: Product: MCU VIRTUAL COM DEMO
Mai 17 16:18:43 raspitest kernel: usb 1-1.2: Manufacturer: NXP SEMICONDUCTORS
Mai 17 16:18:43 raspitest kernel: cdc_acm 1-1.2:1.0: ttyACM1: USB ACM device
This happens with 50 mW output power on an external antenna and using stock cable equiped with ferrite beads. I've also tried a self-made cable using a short and shielded cable. USB connection crashes everytime with the same error in the second after a transmission has been started.
It seems that the source of the interference happens already in the device. No measure to shield the way from the device to the Raspberry Pi USB ports helps or makes any difference to the time when the USB connection is dropped.
Same setup has been tried with the GD-77 and verything is working fine, I can use the hotspot mode with full tx power together with the GD-77.
By the way, the RD-5R has BER < 0.3 on all of my MMDVM_Dual_Hat duplex hotspots. Thank you for still working on the improvements also for the OpenRD5R version.
tl;nr: I think the problem is caused by the subobtimal quality of the RD-5R and the interference that it triggers and not by a faulty MMDVMHost binary.
73!
Tino
Re: Experimental Baofeng RD-5R version
Hello everybody !
Exactly the same observation as DL8TU on my own RD-5R with the same precautions (shielded cable, ferrite sleeves, outdoor or dummy antenna etc.).
No problem at all with my GD-77 which works perfectly.
Thank you to Roger and the whole team for the great work done.
73 from F6CYK/Pierre-Antoine
Exactly the same observation as DL8TU on my own RD-5R with the same precautions (shielded cable, ferrite sleeves, outdoor or dummy antenna etc.).
No problem at all with my GD-77 which works perfectly.
Thank you to Roger and the whole team for the great work done.
73 from F6CYK/Pierre-Antoine