-
Notifications
You must be signed in to change notification settings - Fork 110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AMBED with Flo DF3ET AMBE3003 and DV-30 Stick #117
Comments
I could not check it yet but I guess the code fails pairing the spare AMBE channel of the DF2ET AMBE 3003 board with the channel of the DV-Stick 30. I have to take a look at the code. |
Ist it an issue or just not supported |
I found the same issue and proposed a change today to get it work.
73 de Hans DL5DI |
Hi Hans,
thanks for the info. I was also trying to debug this. Could I see you patch please?
vy73 de Florian DF2ET
|
Uhps, sure.
I am no specialist on GitHub and thought that it would be visible at the
correct place automatically.
Maybe I did something wrong when recommending it.
The changed source file is located in this forked branch:
https://github.com/dl5di/xlxd/blob/patch-1/ambed/cvocodecs.cpp
73 de Hans DL5DI
Am 26.03.2019 um 07:48 schrieb Florian (DF2ET):
… Hi Hans,
thanks for the info. I was also trying to debug this. Could I see you
patch please?
vy73 de Florian DF2ET
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#117 (comment)>, or
mute the thread
<https://github.com/notifications/unsubscribe-auth/ACpzZHbEqjpVdB2j67YUZVmCpFQyIQUNks5vacKzgaJpZM4aUCgG>.
|
Hi Hans, no problem. I could also have had a look at your repo :-) vy73 de Florian DF2ET |
Last night I saw 2 branches in addition to the master in the xlxd repo.
One was older, the other showed my recommended changes.
Both are gone now, I only see the master branch left.
|
Maybe you looked at the original repo rather than your fork. I can still see the changes in your forked repo: https://github.com/dl5di/xlxd/tree/patch-1?files=1 |
First test:
Need to check my hars/soft reset settings on the USB-3000 board ... |
I also found some open issues to fix with my modified old ThumbDVs,
which were for RPI/GPIO, but now modified for USB/FTDI.
But these things should not have anything to do with the detection and
pairing fix.
This stuff was just invisible before, because the device was not used at
all.
The worst was, that the ambed always run into a deadlock as soon as I
plugged in 2 sticks.
Have fun with fixing the other open issues! :-)
73 de Hans DL5DI
Am 26.03.2019 um 11:16 schrieb Florian (DF2ET):
First test:
|~/xlxd/ambed $ !! sudo ./ambed 10.99.0.156 Starting AMBEd 1.3.3
Initializing vocodecs: Detected 2 USB-FTDI devices Description :
DF2ET-3003 Serial : AI041BTL Description : USB-3000 Serial : AI041BTM
Opening DF2ET-3003:AI041BTL device Trying DF2ET-3003 soft reset
DF2ET-3003 soft reset succeeded ReadDeviceVersion :
0AMBE3003F1V120.E100.XXXX.C106.G514.R008.A0030608.C0020208/ Opening
USB-3000:AI041BTM device FTDI function FT_Write error 0 FTDI function
FT_Write error 0 FTDI function FT_Write error 0 FTDI function FT_Write
error 0 FTDI function FT_Write error 0 FTDI function FT_Write error 0
FTDI function FT_Write error 0 FTDI function FT_Write error 0 |
Need to check my hars/soft reset settings on the USB-3000 board ...
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#117 (comment)>, or
mute the thread
<https://github.com/notifications/unsubscribe-auth/ACpzZNdEe5PcrXI-RJz30yDZGSgPsbe5ks5vafOAgaJpZM4aUCgG>.
--
73
Hans DL5DI
|
any news on this? |
Hi folks, AMBED with Flo DF3ET AMBE3003 and DV-30 Stick should be fixed with the latest AMBEd release v2.3.1 73, Luc |
Jupp, I have tested latest changes by LX1JL successfully. Thank you for your support guys. |
Tnx Flo, you're welcome. 73, Luc |
As soon as I add a DV-Stick 30 Stick to the USB Port of the AMBE Server the AMBE3003 stops workling.
Both Ambes are recognized but no channels available.
As soon as I reject the DV-Stick 30 all is ok again.
The text was updated successfully, but these errors were encountered: