Experimental Baofeng RD-5R version

User avatar
F1RMB
Posts: 681
Joined: Sat Nov 16, 2019 5:42 am
Location: Grenoble, France
Contact:

Re: Experimental Baofeng RD-5R version

Post by F1RMB » Tue May 12, 2020 11:37 am

SO5AJG wrote:
Tue May 12, 2020 10:48 am
I don't know if it will be a complete file.
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:
Let it run a little bit more, and re-upload the logs, Maybe we will get more informations.


Cheers.
---
Daniel
73 de Daniel.

SO5AJG
Posts: 60
Joined: Sat Nov 16, 2019 3:44 pm

Re: Experimental Baofeng RD-5R version

Post by SO5AJG » Tue May 12, 2020 12:21 pm

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 9 times
Janusz - SO5AJG - Warsaw

User avatar
F1RMB
Posts: 681
Joined: Sat Nov 16, 2019 5:42 am
Location: Grenoble, France
Contact:

Re: Experimental Baofeng RD-5R version

Post by F1RMB » Tue May 12, 2020 12:44 pm

SO5AJG wrote:
Tue May 12, 2020 12:21 pm
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.
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
73 de Daniel.

User avatar
F1RMB
Posts: 681
Joined: Sat Nov 16, 2019 5:42 am
Location: Grenoble, France
Contact:

Re: Experimental Baofeng RD-5R version

Post by F1RMB » Tue May 12, 2020 1:16 pm

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:

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
73 de Daniel.

SO5AJG
Posts: 60
Joined: Sat Nov 16, 2019 3:44 pm

Re: Experimental Baofeng RD-5R version

Post by SO5AJG » Tue May 12, 2020 2:38 pm

F1RMB wrote:
Tue May 12, 2020 1:16 pm
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:

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
Whether it is sending the same log file as before or another one.
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.
Janusz - SO5AJG - Warsaw

User avatar
F1RMB
Posts: 681
Joined: Sat Nov 16, 2019 5:42 am
Location: Grenoble, France
Contact:

Re: Experimental Baofeng RD-5R version

Post by F1RMB » Tue May 12, 2020 2:45 pm

SO5AJG wrote:
Tue May 12, 2020 2:38 pm

Whether it is sending the same log file as before or another one.
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.
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
73 de Daniel.

SO5AJG
Posts: 60
Joined: Sat Nov 16, 2019 3:44 pm

Re: Experimental Baofeng RD-5R version

Post by SO5AJG » Tue May 12, 2020 3:33 pm

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.
Janusz - SO5AJG - Warsaw

dl8tu
Posts: 2
Joined: Sun May 17, 2020 1:39 pm

Re: Experimental Baofeng RD-5R version

Post by dl8tu » Sun May 17, 2020 3:38 pm

SO5AJG wrote:
Tue May 12, 2020 12:21 pm
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.
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
I don't use Pi-Star. I used different self compiled MMDVMHost binaries to try out the hotspot mode.
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

F6CYK
Posts: 9
Joined: Sat Nov 16, 2019 9:09 pm

Re: Experimental Baofeng RD-5R version

Post by F6CYK » Sun May 17, 2020 9:55 pm

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

SteveTh3Pirate
Posts: 1
Joined: Sun May 10, 2020 7:02 am

Re: Experimental Baofeng RD-5R version

Post by SteveTh3Pirate » Fri May 22, 2020 4:09 am

Hey Peeps,

Same as everyone with running the RD5R as a MDVMM Hotspot, and even the same with running it as DVBlue on Windows. The radio crashes back to VFO/Channel mode. ill paste my latest logs see if they are of any use for decoding.

dmesg

Code: Select all

 [    2.066443] usb 1-1.3: new full-speed USB device number 4 using dwc_otg
[    2.200531] usb 1-1.3: New USB device found, idVendor=1fc9, idProduct=0094
[    2.201947] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    2.203485] usb 1-1.3: Product: MCU VIRTUAL COM DEMO
[    2.205115] usb 1-1.3: Manufacturer: NXP SEMICONDUCTORS
[    2.237832] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[    2.298031] i2c /dev entries driver
[    2.486966] systemd-udevd[137]: starting version 215
[    2.735850] cdc_acm 1-1.3:1.0: ttyACM0: USB ACM device
[    2.738197] usbcore: registered new interface driver cdc_acm
[    2.738210] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[    2.778230] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
[    3.092975] usbcore: registered new interface driver brcmfmac
[    3.172091] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[    3.216305] brcmfmac: Firmware version = wl0: Aug  7 2017 00:46:29 version 7.45.41.46 (r666254 CY) FWID 01-f8a78378
[    3.927010] systemd-journald[122]: Received request to flush runtime journal from PID 1
[    4.043634] ip_tables: (C) 2000-2006 Netfilter Core Team
[    4.193335] ip6_tables: (C) 2000-2006 Netfilter Core Team
[    4.560413] brcmfmac: power management disabled
[    5.698431] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[   12.910751] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[   13.241237] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[   35.427787] random: crng init done
[   57.009915] cdc_acm 1-1.3:1.0: failed to set dtr/rts
[   59.010561] cdc_acm 1-1.3:1.0: failed to set dtr/rts
[   71.827336] cdc_acm 1-1.3:1.0: failed to set dtr/rts
[  156.593698] cdc_acm 1-1.3:1.0: failed to set dtr/rts
[  169.411792] cdc_acm 1-1.3:1.0: failed to set dtr/rts 
And my modem log;

Code: Select all

I: 2020-05-22 03:59:20.396 This software is for use on amateur radio networks only,
I: 2020-05-22 03:59:20.396 it is to be used for educational purposes only. Its use on
I: 2020-05-22 03:59:20.396 commercial networks is strictly prohibited.
I: 2020-05-22 03:59:20.396 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others
M: 2020-05-22 03:59:20.396 MMDVMHost-20181107_Pi-Star is starting
M: 2020-05-22 03:59:20.396 Built 09:24:10 Nov 12 2018 (GitID #9444eca)
I: 2020-05-22 03:59:20.397 General Parameters
I: 2020-05-22 03:59:20.397     Duplex: no
I: 2020-05-22 03:59:20.397     Timeout: 240s
I: 2020-05-22 03:59:20.397     D-Star: disabled
I: 2020-05-22 03:59:20.397     DMR: enabled
I: 2020-05-22 03:59:20.397     YSF: disabled
I: 2020-05-22 03:59:20.397     P25: disabled
I: 2020-05-22 03:59:20.397     NXDN: disabled
I: 2020-05-22 03:59:20.397     POCSAG: disabled
I: 2020-05-22 03:59:20.397 Modem Parameters
I: 2020-05-22 03:59:20.397     Port: /dev/ttyACM0
I: 2020-05-22 03:59:20.397     Protocol: uart
I: 2020-05-22 03:59:20.397     RX Invert: no
I: 2020-05-22 03:59:20.397     TX Invert: no
I: 2020-05-22 03:59:20.397     PTT Invert: no
I: 2020-05-22 03:59:20.397     TX Delay: 100ms
I: 2020-05-22 03:59:20.397     RX Offset: 0Hz
I: 2020-05-22 03:59:20.397     TX Offset: 0Hz
I: 2020-05-22 03:59:20.397     RX DC Offset: 0
I: 2020-05-22 03:59:20.397     TX DC Offset: 0
I: 2020-05-22 03:59:20.397     RF Level: 100.0%
I: 2020-05-22 03:59:20.397     DMR Delay: 0 (0.0ms)
I: 2020-05-22 03:59:20.397     RX Level: 50.0%
I: 2020-05-22 03:59:20.397     CW Id TX Level: 50.0%
I: 2020-05-22 03:59:20.397     D-Star TX Level: 50.0%
I: 2020-05-22 03:59:20.397     DMR TX Level: 50.0%
I: 2020-05-22 03:59:20.397     YSF TX Level: 50.0%
I: 2020-05-22 03:59:20.397     P25 TX Level: 50.0%
I: 2020-05-22 03:59:20.397     NXDN TX Level: 50.0%
I: 2020-05-22 03:59:20.397     POCSAG TX Level: 50.0%
I: 2020-05-22 03:59:20.397     RX Frequency: 433575000Hz (433575000Hz)
I: 2020-05-22 03:59:20.397     TX Frequency: 433575000Hz (433575000Hz)
M: 2020-05-22 03:59:20.398 Opening the MMDVM
I: 2020-05-22 03:59:22.409 MMDVM protocol version: 1, description: OpenGD77_HS v0.1.4 GitID #d9ab196f (Radio:RD-5R, Mode:MMDVM)
I: 2020-05-22 03:59:22.429 Display Parameters
I: 2020-05-22 03:59:22.430     Type: None
W: 2020-05-22 03:59:22.430 No valid display found, disabling
I: 2020-05-22 03:59:22.434 DMR Network Parameters
I: 2020-05-22 03:59:22.434     Address: tgif.network
I: 2020-05-22 03:59:22.434     Port: 62031
I: 2020-05-22 03:59:22.434     Local: random
I: 2020-05-22 03:59:22.434     Jitter: 360ms
I: 2020-05-22 03:59:22.434     Slot 1: disabled
I: 2020-05-22 03:59:22.434     Slot 2: enabled
I: 2020-05-22 03:59:22.434     Mode Hang: 20s
I: 2020-05-22 03:59:22.452 Info Parameters
I: 2020-05-22 03:59:22.452     RX Frequency: 433575000Hz
I: 2020-05-22 03:59:22.452     TX Frequency: 433575000Hz
I: 2020-05-22 03:59:22.452     Power: 1W
I: 2020-05-22 03:59:22.452     Latitude: 51.167900deg N
I: 2020-05-22 03:59:22.452     Longitude: 1.763000deg E
I: 2020-05-22 03:59:22.452     Height: 0m
I: 2020-05-22 03:59:22.452     Description: "United Kingdom"
M: 2020-05-22 03:59:22.452 DMR, Opening DMR Network
I: 2020-05-22 03:59:22.452 RSSI
I: 2020-05-22 03:59:22.452     Mapping File: /usr/local/etc/RSSI.dat
I: 2020-05-22 03:59:22.453 Loaded 14 RSSI data mapping points from /usr/local/etc/RSSI.dat
I: 2020-05-22 03:59:22.453 DMR Id Lookups
I: 2020-05-22 03:59:22.453     File: /usr/local/etc/DMRIds.dat
I: 2020-05-22 03:59:22.453     Reload: 24 hours
I: 2020-05-22 03:59:23.285 Loaded 162716 Ids to the DMR callsign lookup table
I: 2020-05-22 03:59:23.286 DMR RF Parameters
I: 2020-05-22 03:59:23.286 Started the DMR Id lookup reload thread
I: 2020-05-22 03:59:23.291     Color Code: 1
I: 2020-05-22 03:59:23.291     Self Only: yes
I: 2020-05-22 03:59:23.291     Embedded LC Only: no
I: 2020-05-22 03:59:23.291     Dump Talker Alias Data: yes
I: 2020-05-22 03:59:23.291     Prefixes: 0
I: 2020-05-22 03:59:23.291     Call Hang: 0s
I: 2020-05-22 03:59:23.291     TX Hang: 0s
I: 2020-05-22 03:59:23.291     Mode Hang: 20s
I: 2020-05-22 03:59:23.291     DMR Roaming Beacon Interval: 30s
I: 2020-05-22 03:59:23.291     DMR Roaming Beacon Duration: 3s
M: 2020-05-22 03:59:23.291 MMDVMHost-20181107_Pi-Star is running
M: 2020-05-22 03:59:33.691 DMR, Logged into the master successfully
M: 2020-05-22 03:59:33.776 DMR Slot 2, received network late entry from W8MKH to TG 3154
E: 2020-05-22 03:59:45.434 No reply from the modem for some time, resetting it
M: 2020-05-22 03:59:45.434 Closing the MMDVM
M: 2020-05-22 03:59:47.434 Opening the MMDVM
E: 2020-05-22 04:00:00.251 Unable to read the firmware version after six attempts
M: 2020-05-22 04:00:05.252 Opening the MMDVM
E: 2020-05-22 04:01:37.836 Unable to read the firmware version after six attempts
Thanks guys for the hard work on this firmware.

Post Reply