toggle quoted messageShow quoted text
Thank you, David.
I knew you'd updated the Windows version for Fusion, and have been happily using it -- it's FANTASTIC! I didn't know you'd also updated the Android version, which I note was updated on my phone automatically, and seems to be working just fine via my Pi Ambeserver. Thank you again!
Is Peanut working like Alain suggested? Just curious...I'm not using Peanut.
On Sat, May 30, 2020 at 4:07 PM David PA7LIM <info@...
The Garage project ( BlueDV AMBE for Android ) is transmitting on Fusion.
Greets and 73,
From: email@example.com <firstname.lastname@example.org>
On Behalf Of Gwen Patton via groups.io
Sent: Saturday, 30 May 2020 21:52
Subject: Re: [ambe] Linking Peanut Server to Fusion Room
Yeah, the Windows version works already with ThumbDV on Fusion just great. Just a plain-jane Ambeserver install on a Pi with a dynamic DNS daemon to keep the IP address steady will work great with the Windows version on Fusion anywhere
you have Internet. But that's the Windows version. The Android version(s) have never, to my knowledge, EVER transmitted on Fusion. (Some will RECEIVE it with a secret handshake that I don't recall offhand.)
All I'm saying. I'm done. Y'all have a good day now.
On Sat, May 30, 2020 at 3:44 PM kb8zgl <wolthuis@...> wrote:
Sorry, no the Windows version.
Mike, are you talking about the ANDROID version of BlueDV? It is called "BlueDV AMBE". That's it's name.
The WINDOWS version was the only one working completely with Fusion last I looked. David even said the Android version may never transmit on Fusion, last I heard.
Peanut is a very restricted version that only ever worked with David's servers that I know of. I'll admit I haven't looked at Peanut recently, but I generally
don't need it.
The ThumbDV stuck is an AMBE device, but the NAME of the Windows version that works on Fusion is "BlueDV Windows". "BlueDV AMBE" is the NAME of the Android version
that never has had full Fusion support.
Hence my confusion here. I didn't know Peanut worked with any servers but David's, and want aware he made it work with Fusion when the FULL Android version still
does not. Peanut is an Android product, so I hope you see why I asked what I did.
The latest BlueDV beta is working on Fusion with NW Radio AMBE! Mines over network and vpn even
On May 30, 2020, at 1:07 PM, Gwen Patton <ardrhi@...> wrote:
Is there a reason you're using Peanut, and not the actual BlueDV or BlueDV AMBE clients? I have a simple AMBEServer set up on a Pi 3+, and I can connect to any
reflector. With BlueDV Windows, I can even connect to Fusion rooms. You just can't connect to Fusion to transmit with the Android client. But the Windows client works fine on DMR, D-STar, and Fusion. The Android BlueDV works fine for DMR and D-Star.
So why are you messing with Peanut? That's a really limited program. David hasn't made BlueDV AMBE do Fusion, has he made Peanut do Fusion somehow? Is that why
you're using Peanut?
On Sat, May 30, 2020 at 11:16 AM Alain Reid <va2spb@...> wrote:
Folks, I am trying to achieve what PA7LIM describes below: My goal that is to allow an amateur with Peanuts Client on his Android / Windows to have a QSO with an amateur who uses his Yeasu FT3D
on my Fusion repeater. So I followed PA7LIM procedure described below:
I set up an AMBEserver on a Raspberry PI 4 using a
ThumbDV. That works well. It did not work with DVStick30 unfortunately. In reference to the red dots above, my questions are the following:
Q1: Do I really have to build a YSF repeater or I can just provide PA7LIM with my Room number so he can connects is Peanut server to my Fusion Room number? Q2: Do I need to set up a YSF Server and than link it to my Fusion Room number and forward
that to PA7LIM with the Hostname and port of the YSF server? Thank you folks if you can bright some light! 73!