AIOC and AllStarLink with simple_usb Module #61
Comments
|
Oh wow I just found the solution already, I was on the right track. |
|
Nice! So this is a first confirmed use for All-star link for me 🙂 Did you end up using the Virtual COS function of the AIOC? |
|
Well I tried to do what they did in that video and did not get the same results. |
|
Virtual COS essentially listens to the audio from the radio and tries to determine if there is a carrier (squelch disengaged). Currently this is done using very simple thresholding. |
|
Ah yes I saw that option in the ASL module code, cool I will see if I can get it to work! |
|
Oh.. I think I should be using v 1.3 RC1 not 1.2, correct Simon? |
|
Ooops, you are correct! My bad. It looks like the COS feature was introduced in the v1.3 version. |
|
Murf, is it possible to share your modified version of Allstarlink? I would love to test it with my AOIC. |
|
All I modified in chan_usbradio.c was the product and vendor ID to match the 1.2 ones.So reversing this, if you can set these to CM108 in 1.3 you are already good to try it.I plan to try this today and will let you know the outcome.
|
|
Simon rather than rebuild v1.3 rc1 with the CM108 Vendor and product ID , here is the changes to the ASL asterisk module : Only chan_usbradio.c needs changes |
|
Ok I see no difference with V1.3 :( |
|
UPDATE: and facepalm... I was using a Quansheng UV-K6, and have now swapped to a 'feng UV-5R and am progressing. |
|
And now OPERATIONAL :) |
What exactly didn't work? I think those should be very similar 🤔
Nice! With virtual COS? Or are you using another way of detecting incoming voice?
Just curious, how did you do it? Using the python script? Note that the next time you use the script, you need to adjust the VID/PID to the new one, or it doesn't find the AIOC. |
|
For the Quansheng, when I run the radio-tune-menu option "F" which is supposed to turn on PTT, emit a tone, then turn off PTT, which it does for the Baofeng UV-5R, but for the Quansheng UV-K6 the PTT stays on and never goes off, and no tone is emitted. For the Vendor/Product ID detection I didnt use the script as I could not get it to run. Modifying the ASL chan_usbradio module itself to look for AIOC IDs rather than CM108 IDs is what I did. For COS I didnt really do anything to the AllStarLink config other than what the Youtube I linked suggested, which is basically just set carrierfrom=VOX in usbradio.conf May I ask, what exactly did you base the CM108 emulation on? Was it the PDF that ASL use for modifying the CM108 hardware? |
|
Has anyone been able to successfully use the script? I have tried on both a linux and windows machine and each time it fails. |
Which script? |
|
The script for v1.3 RC1 that allows the vid and pid to be changed |
No I could not get it to run either, errors in the file. |
|
What all is involved in recompiling the file? Once the file is compiled is it as easy as placing the file on your existing Allstarlink install or do you need to do a complete reinstall of Allstarlink? |
You will need to install build tools on the computer that you have ASL installed on, what OS is it? and distribution? |
|
@Murf I am using the ASL Beta 2 ISO. I believe it's based on Debian 10. |
Perfect, thats what I am using. |
|
Hi, @Murf Brett, Is the modified 'chan_usbradio.c' (chan_usbradio.so) file available?. I have been struggling and only running Raspberry Pi on Linux and would like to try it. I have no major knowledge but can get the file to the correct directory. I would love to get my AIOC working on AllStar. Thanks in advance, or more information (laymans terms) on how to do it. |
|
@Hadgee The file is available in my github, but you need to be able to build it. If
you are not familiar with this process then it is probably not the best
option for you.
…On Mon, 25 Mar 2024 at 07:38, Hadgee ***@***.***> wrote:
Hi, @Murf <https://github.com/Murf> Brett,
Is the modified 'chan_usbradio.c' (chan_usbradio.so) file available?. I
have been struggling and only running Raspberry Pi on Linux and would like
to try it. I have no major knowledge but can get the file to the correct
directory. I would love to get my AIOC working on AllStar. Thanks in
advance, or more information (laymans terms) on how to do it.
Ellis
—
Reply to this email directly, view it on GitHub
<#61 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAG72OOEAQ4LCIQMOIJCMATYZ42UJAVCNFSM6AAAAABECYDKOWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJWHEZTMMBZGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
@Murf No problem. I will investigate further. |
|
@Murf |
Assuming you are using a Pi, here you go |
|
@Murf Thank you, yes Pi. I will let you know how it goes. |
|
@Murf |
Can you try running the script with |
Nice! I think the thresholding detector on the AIOC needs some tuning still. There are ways to manipulate the timeouts using the script as well, but I have not had time to define the registers for that yet. |
Is invertptt = 0 special (different from default)? From what I can tell from e.g. https://allstarsetup.com/modify-a-cm108-sound-fob/ invertptt should have the same polarity on the AIOC. What about carrierfrom=usbinvert? The AIOC sets the Volume UP or DOWN button (not sure) when the carrier is received. I think that is the other way around by default in ASL? |
everything is run Sudo. |
I think the COS overhang needs to be extended a bit as it does flap a bit between words. this causes a problem on ASL. So good news there's a register for it. I would go to say 600ms or so to start with. |
|
Hi @skuep please can you help with advice about an environment that will support the Python hid library functions? I've been struggling for days to get this to work on Rasbian Bullseye, since this is the OS that end users are likely to use (an an RPi 3 etc since they have it already for ASL). I'm running into one error after another. I'm very happy to help where I can, as being able to run the script is essential for any user looking to take advantage of the v1.3 features. Sorry to be a pain but it's difficult to find experts in this specialist area. |
None of my DTMF codes show up at all. |
|
Hi all, |
|
@Hadgee did you have any trouble running the python script to set the new USB ID's and using the HID drivers? I can't seem to get it to work on my Pi 3b. |
|
@G1LRO I only tried it once and it didn't work, also on a Pi 3b. I didn't want to mess with my ASL image on the Pi 4 as I had lost it once. So essentially using @Murf 's modified chan_usbradio.so file so no USB ID modification needed. The only issue I have had was the vox triggering and staying on tx which turned out to be very noisy monitor/HDMI lead. So quiet now its headless. |
|
I definitely need to test the script on a Raspberry Pi. Sounds odd to me, that it doesn't work. But currently I don't have a lot of spare time for this project, so it might take a while. |
Yeah, b feel free to open those issues 👍 |
|
I've provided a documented/scripted software download for the process of using |
|
Oops i spoke too early, I am getting no CTSS at all, tried all 3 settings: |
|
@Murf I don't think you'll get CTCSS to work through the speaker port of the radio, it's all filtered out by then. CTCSS can be used on the receive settings of the radio to secure the channel, then the AIOC will just use it's virtual-COS when the RX audio arrives. so set the ctcssfrom to no and rely on the squelch/ctcss settings on the radio. I'm also getting reliable DTMF operation on the ASL. |
|
Sorry i meant DTMF
I am not quite sure what this setting even means to be honest:
ctcssfrom
…On Sun, 5 May 2024 at 19:16, G1LRO ***@***.***> wrote:
@Murf <https://github.com/Murf> I don't think you'll get CTCSS to work
through the speaker port of the radio, it's all filtered out by then. CTCSS
can be used on the receive settings of the radio to secure the channel,
then the AIOC will just use it's virtual-COS when the RX audio arrives..
—
Reply to this email directly, view it on GitHub
<#61 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAG72OPCAIHAYOTN3PKWDNDZAX2F5AVCNFSM6AAAAABECYDKOWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJUG4YDANZRGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Nice, I like it! Couple of suggestions:
|
I remembered thare are some issues with DTMF due to the default COS timeout being too low.. Not sure though, should be all in this issue here. |
Hi Simon, I haven't modified your binary firmware, I've just supplied the Python scripts for the user to run with the extra parameter that will extend the COS. When the firmware goes to GA then I'll just change the link to the correct bin file, I think everything else will be OK. If/when the HID mechanism is changed then I can update that process too. It's all fairly easily scripted, but for now I'm prescribing a Raspberry Pi image to do the updates as that's a stable machine environment. For @Murf and the DTMF issues, I have not experienced any of these and use DTMF to join nodes on ASL etc, I can also see the DTMF properly reported in the Asterisk command-line console. I wonder if this is a problem with the sending device, I happy to pop a video across if that will help. |
|
@G1LRO The node radio is a Baofeng UV-5R and the radio I am trying to DTMF to it from is a Quansheng UV-K6(8) |
@Murf It might not be your node. I have two Quansheng UV-K6(8) on different firmware. IJV and Egzumer. Only the Egzumer works with my node for DTMF. Try another firmware it might help. |
|
@Hadgee I have tried multiple firmware, and even an Icom and a Yaesu handheld, same thing on all of them, just the occasional "*" is recognized, nothing else. |
ASL-DTMF.mp4Hi @Murf , here is a video of a Boafeng sending DTMF to a Quansheng K5 connected via my Universal Radio Controller box (that includes the AIOC CPU). |
I see.. I was just thrown off by the following
That's a good choice in my opinion for now. |
|
@G1LRO Just wanted to give you a heads up regarding a new firmware release. From now on, the new HID interface will be used. It just has some minor protocol differences, the registers stayed the same (as far as I can remember). You might want to change your scripts to the new solution in order to avoid an influx of users having issues :-) BTW, what was the COS timeout that you decided on for AllStarLink? I was thinking on making this value the new default. |
More of a question than an Issue,
I am trying to get my AIOC working with a 'feng UV-5R for an AllStarLink node.
I recompiled the chan_simpleusb module with the correct vendor and product ID's, and was surprised when the PTT came on during the simpleusb-tune-menu utility option to flash the PTT.
I know I have a long way to go, especially with COR.
How is COR currently handled by default? is it a code sent on the serial port?
Thanks,
Murf.
The text was updated successfully, but these errors were encountered: