Date   

Re: ASL BeagleBone Black

Mike/K5JR
 

Nope, the ASL_1.01-20180228-armhf-bbb-strech-image.img. The accompanying readme file says user:repeater, pw:allstarlink, consistent with other ASL rpi versions. 

I do have a couple of the early hamvoip bbb units operating (pre rpi) and wish to migrate them over to ASL. Yes, they are “root”. 

I realize that little, if any, development is taking place on the ASL version. And absolutely *zero* development has taken place on the hv version in years. 


tnx
Mike / W5JR
Alpharetta GA


On Oct 8, 2019, at 5:09 PM, Steve KC1AWV <smiller@...> wrote:

A quick Google search for Beaglebone Black AllStarLink provided a document with this information:

The login username is root and the PW is root

I also assume this is the hamvoip distribution? If so, you may get better help from the hamvoip folks.

On Tue, Oct 8, 2019 at 4:27 PM Mike/W5JR <w5jr.lists@...> wrote:
I’ve finally gotten around to making an SD card for the BBB ASL image. I’m trying to log into the unit for the first time with this SD card. I’m connected to it via ssh port 22 just fine and it appears to accept the “repeater” user name. Entering the password specified in the readme file of “allstarlink” isn’t working. I’ve tried some capitalization perturbations, but no joy. Is there a different pw? Reimage the SD card? Looking for ideas. 

Tnx
Mike/W5JR
Alpharetta GA



--
Steve Miller
KC1AWV


Re: ASL BeagleBone Black

Steve KC1AWV
 

A quick Google search for Beaglebone Black AllStarLink provided a document with this information:

The login username is root and the PW is root

I also assume this is the hamvoip distribution? If so, you may get better help from the hamvoip folks.


On Tue, Oct 8, 2019 at 4:27 PM Mike/W5JR <w5jr.lists@...> wrote:
I’ve finally gotten around to making an SD card for the BBB ASL image. I’m trying to log into the unit for the first time with this SD card. I’m connected to it via ssh port 22 just fine and it appears to accept the “repeater” user name. Entering the password specified in the readme file of “allstarlink” isn’t working. I’ve tried some capitalization perturbations, but no joy. Is there a different pw? Reimage the SD card? Looking for ideas. 

Tnx
Mike/W5JR
Alpharetta GA



--
Steve Miller
KC1AWV


ASL BeagleBone Black

Mike/K5JR
 

I’ve finally gotten around to making an SD card for the BBB ASL image. I’m trying to log into the unit for the first time with this SD card. I’m connected to it via ssh port 22 just fine and it appears to accept the “repeater” user name. Entering the password specified in the readme file of “allstarlink” isn’t working. I’ve tried some capitalization perturbations, but no joy. Is there a different pw? Reimage the SD card? Looking for ideas. 

Tnx
Mike/W5JR
Alpharetta GA


Re: MMDVM_BRIDGE

 

sounds like you got you dmr id blocked by keying up to close together. do not use it for an hour and it should unlock.

also you may want to set min TX to 2500 in analog_bridge to help with that.

On Tue, Oct 8, 2019 at 2:21 PM Chris K7AZ via Groups.Io <kilo7alphazulu=verizon.net@groups.io> wrote:


Has anyone heard of a voice saying "blocked" related to transcoding DMR to ASL?
Typically its heard on the ASL side and 1-2 seconds after ASL source unkeys.   

Thank you in advance for any help debugging this issue.  

Chris K7AZ 

Sent from my Verizon, Samsung Galaxy smartphone


MMDVM_BRIDGE

Chris K7AZ
 



Has anyone heard of a voice saying "blocked" related to transcoding DMR to ASL?
Typically its heard on the ASL side and 1-2 seconds after ASL source unkeys.   

Thank you in advance for any help debugging this issue.  

Chris K7AZ 

Sent from my Verizon, Samsung Galaxy smartphone


Re: Image for Raspberry pi3 with Debian 10 Buster with DVSWICTH SERVER, HBLINK3 AND HBMONITOR.

Tom Corcoran
 

Hello EA5GVK Joaquin,

can you explain what I am looking at on the desktop??


--
Tom VE3NY


test

Pierre Martel
 

Just making a test


Re: USRP connection on the Windows IAXRPT client?

Steve N4IRS
 

There will be a Windows (Python3) USRP client.

Sent by smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Steve KC1AWV <smiller@...>
Sent: Monday, October 7, 2019 11:54:50 AM
To: main@dvswitch.groups.io <main@dvswitch.groups.io>
Subject: Re: [DVSwitch] USRP connection on the Windows IAXRPT client?
 
If you're talking the Xelatec (xipar) IAXRPT dispatch console, I don't think so. It's closed source as well, so a separate Windows client would be needed to build in the USRP functions I believe.

On Mon, Oct 7, 2019 at 11:38 AM Russell, KV4S <russelljthomas@...> wrote:
This may not be available but does anyone know if you can configure the Windows client to talk to USRP?



--
Steve Miller
KC1AWV


Re: USRP connection on the Windows IAXRPT client?

Steve KC1AWV
 

If you're talking the Xelatec (xipar) IAXRPT dispatch console, I don't think so. It's closed source as well, so a separate Windows client would be needed to build in the USRP functions I believe.

On Mon, Oct 7, 2019 at 11:38 AM Russell, KV4S <russelljthomas@...> wrote:
This may not be available but does anyone know if you can configure the Windows client to talk to USRP?



--
Steve Miller
KC1AWV


USRP connection on the Windows IAXRPT client?

 

This may not be available but does anyone know if you can configure the Windows client to talk to USRP?


Re: MMDVM_BRIDGE and connect to XLX selected Module #mmdvm_bridge

SP2ONG Waldek
 
Edited

OK, on github is version from  M: 2019-10-07 06:55:32.816 Built 10:28:48 Jul  1 2019 (GitID #43be6b4)

You have update 2 July  and this version has working XLX but is not avilabel as binary on GitHub

73 Waldek


Re: MMDVM_BRIDGE and connect to XLX selected Module #mmdvm_bridge

Mike Zingman - N4IRR
 

Please read the thread below.


Re: MMDVM_BRIDGE and connect to XLX selected Module #mmdvm_bridge

SP2ONG Waldek
 

Hi Mike,

I have try used "options=XLX:4004" but is not working me with XLX reflectror, I have used 

I: 2019-10-07 06:55:32.815 MMDVM_Bridge:
I: 2019-10-07 06:55:32.816 Portions Copyright (C) 2018 DVSwitch, INAD.
I: 2019-10-07 06:55:32.816 Hacks by Mike N4IRR and Steve N4IRS
I: 2019-10-07 06:55:32.816 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
I: 2019-10-07 06:55:32.816 This software is for use on amateur radio networks only,
I: 2019-10-07 06:55:32.816 it is to be used for educational purposes only. Its use on
I: 2019-10-07 06:55:32.816 commercial networks is strictly prohibited.
I: 2019-10-07 06:55:32.816 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others
M: 2019-10-07 06:55:32.816 MMDVM_Bridge-20180423 is starting
M: 2019-10-07 06:55:32.816 Built 10:28:48 Jul  1 2019 (GitID #43be6b4)
........
I: 2019-10-07 06:51:39.717 DMR Network Parameters
I: 2019-10-07 06:51:39.717     Address: 172.16.1.10
I: 2019-10-07 06:51:39.717     Port: 62030
I: 2019-10-07 06:51:39.717     Local: 52033
I: 2019-10-07 06:51:39.717     Jitter: 360ms
I: 2019-10-07 06:51:39.717     Slot 1: disabled
I: 2019-10-07 06:51:39.717     Slot 2: enabled
I: 2019-10-07 06:51:39.717     Mode Hang: 3s
I: 2019-10-07 06:51:39.717     Options: XLX:4004
.....
M: 2019-10-07 06:55:33.010 MMDVM_Bridge-20180423 is running
D: 2019-10-07 06:55:43.053 DMR, Sending authorisation
D: 2019-10-07 06:55:43.089 DMR, Sending configuration
D: 2019-10-07 06:55:43.129 DMR, Sending options
M: 2019-10-07 06:55:43.165 DMR, Logged into the master successfully




On Thu, Oct 3, 2019 at 09:11 AM, Mike Zingman - N4IRR wrote:
Correct syntax for MB is

Options
=XLX:4009


USPR and GPIO (4 wire analog interface) to P25 #mmdvm_bridge #analog_bridge

 

Hi,
I was wondering if there is any progress in using analog audio with (PTT and COS via a Pi GPIO) _> USPR --- analog bridge -- P25 MMDVM Gateway.
Any help would be greatly appreciated.
Currently using a MMDVM hotspot - P25 radio to Analog 4 wire E+M circuit I'm sure this can be achieved with DVSwitch and P25 Gateway via USPR.
Thanks
Tim
VK3TIM


Re: MMDVM_BRIDGE and connect to XLX selected Module #mmdvm_bridge

Mike Zingman - N4IRR
 

Yes, we are aware. 


Re: MMDVM_BRIDGE and connect to XLX selected Module #mmdvm_bridge

SP2ONG Waldek
 
Edited

Steve and Mike,

I suppose MMDVM_Bridge is based on MMDVMHost and looking at the sources in the version.h file

https://github.com/g4klx/MMDVMHost/blob/master/Version.h#L22

there is information about the software version. Maybe it will be nice to put, for example, "20190701-MMDVM_Bridge" just like Andy does in MMDVMHost for Pi-Star: "20190923-Pi_Star"


I suspect why I see "MMDVM_Unknow" in the "PACKAGE_ID" field of the Hombrew protocol from MMDVM_Bridge. Looking for MMDVMHost sources in DMRNetwork.cpp

   https://github.com/g4klx/MMDVMHost/blob/0b9c1b13629901803f8a3d63bec2695ad13c5269/DMRNetwork.cpp#L576

is placed in PACKAGE_ID information about the hardware/modem used. Because MMDVM_Bridge does not use a hardware modem, it is "MMDVM_Unknown"  it looks OK, but it might be better to enter the  "NONE" :-), but there is cosmetic information when we displayed information about connected systems / users, such as on maps or BM status, etc.:


http://bm.ham-dmr.pl/status/list.htm

73 Waldek SP2ONG


Re: MMDVM_BRIDGE and connect to XLX selected Module #mmdvm_bridge

SP2ONG Waldek
 

These values are shown in HBmonitor so it's probably worth to correspond to reality, i.e. version and type MMDVM (currently shows MMDVM_Unknow) but it is not urgent


Re: MMDVM_BRIDGE and connect to XLX selected Module #mmdvm_bridge

Steve N4IRS
 

I'll put it on the list.
Are you actually testing for those values somewhere or is it cosmetic?

Steve N4IRS

On 10/4/19 12:41 AM, Waldek SP2ONG wrote:

Hi Steve and Mike

When you compile the new version of MMDVM_Bridge, please update the information in the code with the version information from 20180423 to the current one and maybe MMDVM_Bridge will send PACKAGE_ID information in HBP, e.g. MMDVM_BRIDGE?

Waldek



Re: MMDVM_BRIDGE and connect to XLX selected Module #mmdvm_bridge

SP2ONG Waldek
 

Hi Steve and Mike

When you compile the new version of MMDVM_Bridge, please update the information in the code with the version information from 20180423 to the current one and maybe MMDVM_Bridge will send PACKAGE_ID information in HBP, e.g. MMDVM_BRIDGE?

Waldek


Re: MMDVM_BRIDGE and connect to XLX selected Module #mmdvm_bridge

Steve N4IRS
 

The build date is when I build it. The latest available version will always be on the github site. I usually will update github when Mike and I are doing a lot of bug fixes or enhancements. When Mike and I feel it's ready, I will package it up into the apt repository.

Steve

On 10/3/19 7:37 PM, Adrian Fewster wrote:

The reason I mention it Steve, Is that usually the build date, would reflect the commit date on a binary reference.

I understand it doesn't, and your update it is pending. My intention in this thread was to ensure I had infact downloaded the latest available.


On 4/10/19 9:27 am, Steve N4IRS wrote:
I'm so glad.

On 10/3/19 7:25 PM, Adrian Fewster wrote:

Yes that's correct, I agree.

On 4/10/19 9:16 am, Steve N4IRS wrote:
You are talking about the published binary. Mike is talking about the source.

On 10/3/19 7:15 PM, Adrian Fewster wrote:

Not in the

https://github.com/DVSwitch/MMDVM_Bridge/blob/master/bin/MMDVM_Bridge.amd64  path

the latest commit date regarding that, which is what I am & we are talking about, is Jul 2



On 4/10/19 9:11 am, Mike Zingman - N4IRR wrote:
Actually the latest commit date is beyond that.  Several other issues/features were also addressed.
The XLX commit date is July 2



5001 - 5020 of 9925