Soon available! DMR on ThumbDV DV3000U on BlueDV for Windows.

https://youtu.be/69mE5m0Fk14

Will this also work the with Mega256 and Gus's AMBE3000 ?

--

Hi Peter,

The Arduino MEGA withDVMEGA  AMBE3000 will also work! You need a special firmware for that and can be downloaded on the website of DVMEGA.
There are also shield available at combitronics that makes the solution smaller. This will replace the Arduino UNO.



Greets,
    David PA7LIM

--

Hi All,

You can find a pre beta version in the files section of this group.
Please email me directly with your findings. ( or post in this group )

You can find a short manual how to use Brandmeister DMR: http://www.pa7lim.nl/bluedv-windows-ambe/

David PA7LIM
info@...

Hi David,

Got it working right away. The only thing that I noticed what the audio input level didn't behave quite like I expected. Seems to be maxed out even with a very small input signal.

Making a recording into audacity with the same source sees voice peaks at -21dB although on DMR I'm getting reports of being very loud.

Great work though, I'm very impressed.

73
Peter
G7RPG

Hi Peter,

Thanks for your report! Will check if I can lower the default input level tomorrow. 
Does DMR differ from DSTAR in level?

Greets,
   David PA7LIM

Hi David

Thank you for a great program.
I have my ThumbDV up and running okay on Dstar with the Beta program, but on The DMR Status I have got logged out and not sure why. Any help will be appreciated.
Regards
Ian
M0CAG

Hi David,

Great work !!
I'm testing since two days and it looks stable. There are some level différences between DMR and DSTAR. Is there an ALC for the input ?

Also can't wait to try Fusion when available :-)

Is it possible to add in the DMR+ list IPSC2 servers ?

Best regards from Jean-Marc F1SCA

Hi David,

Do you think to develop it with DV3000 (GPIO modul on Rpi)

Best 73, Nicolas
F8FKD

--------------------------------------------

Ok John,

Many thanks

--------------------------------------------

I have been trying to get my ThumbDV to work on Ubuntu Mate Linux version 17.04.
It does work on Windows using WinDV.
I have read various documents about installing binaries and compiling but found that the binaries fail because of version mismatches with dependent software.
I have studied the following docs:
- - - - http://www.amateurlogic.com/downloads/DV3000.pdf
- - - - http://nwdigitalradio.com/thumbdv-and-dv3000-resource-page/
I did download and compile wxWidgets and DummyRepeater and AMBEserver.
I can successfully run "python AMBEtest3.py -n -s /dev/ttyUSB0".  where -n switch means it is the newer hardware which runs at 460800 Baud.

I have so far identified three problems.  They may or may not be interrelated.

Problem #1
I try to run AMBEserver after modifying init.d/AMBEserver configs for the port and speed. 
I configured it to run as a service using :sudo update-rc.d AMBEserver defaults" and then do "service AMBEserver start"
I run "ps -ef|grep AMBE" and see that it is running in the background:
root     18390     1  0 09:22 ?        00:00:00 /usr/bin/AMBEserver -d -i /dev/ttyUSB0 -s 460800
and "server AMBEserver status" shows this:
AMBEserver.service - LSB: Provide AMBE Encode/Decode
   Loaded: loaded (/etc/init.d/AMBEserver; generated; vendor preset: enabled)
   Active: active (running) since Tue 2017-07-25 10:00:41 CDT; 3s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 19189 ExecStop=/etc/init.d/AMBEserver stop (code=killed, signal=TERM)
  Process: 19228 ExecStart=/etc/init.d/AMBEserver start (code=exited, status=0/SUCCESS)
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/AMBEserver.service
           └─19230 /usr/bin/AMBEserver -d -i /dev/ttyUSB0 -s 460800
Jul 25 10:00:41 systemd[1]: Starting LSB: Provide AMBE Encode/Decode...
Jul 25 10:00:41 AMBEserver[19228]: AMBEserver: Starting...
Jul 25 10:00:41 AMBEserver[19228]: Starting AMBEserver at 460800 Baud on ttyUSB0
Jul 25 10:00:41 systemd[1]: Started LSB: Provide AMBE Encode/Decode.
Jul 25 10:00:41 AMBEserver[19228]: AMBEserver: Opened serial port /dev/ttyUSB0 at 460800 bps.

But then as soon as I run dummyrepeater I check AMBEservice and it is is no longer running.
Is there a log which would give more info?   I have checked in /var/log, All I find is a reference to auth.log which shows that I ran the service command.
Not having AMBEserver not stay resident is problem #1.

Problem #2.
After compiling dummyrepeater I added LD_LIBRARY_PATH="/usr/local/lib" to both $HOME/.bashrc and $HOME/.profile
Despite that, I can only get dummyrepeater to run by using the following at the command prompt:
export LD_LIBRARY_PATH="/usr/local/lib";dummyrepeater

Problem #3
If I run dummyrepeater (preceding it with above export statement), I then go to Preferences and configure it for ThumbDV on /dev/ttyUSB0, add my CallSign, etc. then exit and rerun dummyrepeater.  I get this error:
"Can't find the AMBE Dongle on the port specified"
The speed field in Preferences was greyed out, so I went into the "$HOME/.Dummy Repeater" configuration file and changed the speed from dongleSpeed=230400 to dongleSpeed=460800.  There was no change when I reran dummyrepeater.
The DummyReapeater-xxxx.log file has these entries:
E: 2017-07-25 14:32:45: Cannot open device - /dev/ttyUSB0
E: 2017-07-25 14:32:45: Can't find the AMBE Dongle on the port specified
M: 2017-07-25 14:32:45: Opened hw:0,1 hw:0,0 Rate 48000
M: 2017-07-25 14:32:45: Starting ALSA reader thread
M: 2017-07-25 14:32:45: Starting ALSA writer thread
/dev/ttyUSB0 is in group dialout, so I added my user to the dialout group.

I have carefully documented all the steps which I took to compile and configure everything.
I even have reinstalled the Linux OS from scratch and redone the steps using that documentation.
I have reached a brick wall and am hoping some else has had success and may be able to suggest something.

73
Rolf  NR0T

Note:  in Tab 'Dongle' in Preferences for dummyrepeater, I did set the Dongle Type to "DV3000 Serial" and then was able to set the speed to 460800 from within the software.  This change made no difference to the reported results.

I also discovered the following on AMBEserver. I run it from the command line, instead of as a service I get this output to stdio:
$ sudo ./AMBEserver  -d -i /dev/ttyUSB0 -s 460800
AMBEserver: Starting...
AMBEserver: Opened serial port /dev/ttyUSB0 at 460800 bps.
AMBEserver: Couldn't find start byte in serial data
AMBEserver: error receiving response to reset
AMBEserver: Could not initialize the DV3K!

The code for AMBEserver.c shows it is looking for x61 as start byte.
Here is the output of sudo python AMBEtest3.py  -n -s /dev/ttyUSB0
Setting ...
/dev/ttyUSB0
d
8
N
1
False
False
False

Reset
6100010033
Wrote: 5 bytes

Product ID
6100010030
Wrote: 5 bytes

Version
6100010031
Wrote: 5 bytes
g
Set DSTAR Mode
61000c000a013007634000000000000048
Wrote: 17 bytes

It appears that following the reset there is a "61"