Keyboard Shortcuts
Likes
- Direwolf
- Messages
Search
|
Re: Using "TRANSMIT INHIBIT INPUT"
For all who's interested, or as reference: After implementing my circuitry for a PTT interlocking and DCD sharing solution combined with Direwolf, I can confirm Direwolf holds the frames in queue when the TX inhibit input (TXINH) is active, and sends them after release of the input. 73! Dave |
||
|
Re: Radio power control
开云体育Yes that is the feature: Power Control.. ? If the station is transmitting weather, the radio does not need to be powered on most of the time. However, with a bit more functionality, it could be powered up at pre-determined times for possible incoming commands. ? Fred N7FMH ? From: [email protected] [mailto:[email protected]] On Behalf Of Rob Giuliano via groups.io
Sent: Thursday, July 15, 2021 9:33 PM To: [email protected] Subject: Re: [direwolf] Radio power control ? You are request the same feature as the Power Control feature. As If I am reading the Argent Data manual, the feature needs to: ?? a) Activate a GPIO Power Control pin (to power up the radio) ?? ? ? Argent Data unit has a switch to active low, so GPIO = -3 ?? b) Wait a specified number of seconds - so this needs to be before the TX section. ?? c) Then run normal TX function ?? d) De-Activate GPIO Power Control pin ? Of course this would be a tracker feature because there woiuld be no decode while the radio is OFF. Robert Giuliano ? ? On Thursday, July 15, 2021, 8:45:14 PM EDT, Rob Giuliano via groups.io <kb8rco@...> wrote: ? ? Fred, What are you running Direwolf on? ? If it's a pi, you could use the GPIO and a relay to handle the radio power.?? Probably could be done with about any system.? ? Rob Giuliano KB8RCO
|
||
|
Re: Radio power control
开云体育Hi Robert, ? If Direwolf is running and occasionally sending a packet, shouldn’t it be the one to turn the radio on and off? ? The Tracker2/3 could turn on a radio, send a packet, turn off the radio. This may have been commonly used to conserve battery power. Saving battery power is what I have in mind. Unfortunately one of the radios I have draws quite a bit in receive, and, there isn’t much use to keep it on. ? I could see a different app that might turn on a radio at a prescribed time for remote access. ? Of course, an app could launch Direwolf and wait some amount of time for a packet to be transmitted and then “kill” Direwolf. ? Fred N7FMH ? ? From: [email protected] [mailto:[email protected]] On Behalf Of Rob Giuliano via groups.io ? Fred, What are you running Direwolf on? ? If it's a pi, you could use the GPIO and a relay to handle the radio power.?? Probably could be done with about any system.? ? Rob Giuliano KB8RCO
|
||
|
Re: Radio power control
You are request the same feature as the Power Control feature. As If I am reading the Argent Data manual, the feature needs to: ?? a) Activate a GPIO Power Control pin (to power up the radio) ?? ? ? Argent Data unit has a switch to active low, so GPIO = -3 ?? b) Wait a specified number of seconds - so this needs to be before the TX section. ?? c) Then run normal TX function ?? d) De-Activate GPIO Power Control pin Of course this would be a tracker feature because there woiuld be no decode while the radio is OFF. Robert Giuliano
On Thursday, July 15, 2021, 8:45:14 PM EDT, Rob Giuliano via groups.io <kb8rco@...> wrote:
Fred, What are you running Direwolf on? If it's a pi, you could use the GPIO and a relay to handle the radio power.?? Probably could be done with about any system.? Rob Giuliano KB8RCO
|
||
|
Re: Radio power control
Fred,
toggle quoted message
Show quoted text
What are you running Direwolf on? If it's a pi, you could use the GPIO and a relay to handle the radio power.?? Probably could be done with about any system.? Rob Giuliano KB8RCO
|
||
|
Radio power control
开云体育Greetings, ? I am looking to power up a radio, send a packet, shutdown radio. I had this function on the ArgentData trackers. ? I am not seeing a reference to this option in the documentation but then I have missed the obvious before. ? Thanks! ? Best regards, Fred N7FMH |
||
|
Re: Using "TRANSMIT INHIBIT INPUT"
No need to use ALC input, better not actually... Having a good solution, preferably in software, with PTT interlock and DCD sharing across some channels will do the job. No need to involve any ALC input there. My current solution will do the job too just as intended, but it's important Direwolf is holding frames in queue until the TX inhibit input is released. 73! Dave |
||
|
Re: Using "TRANSMIT INHIBIT INPUT"
How about using the ALC input ?
toggle quoted message
Show quoted text
On 14/07/2021 9:00 pm, Dave via groups.io wrote:
|
||
|
Re: Using "TRANSMIT INHIBIT INPUT"
Hi all, I'm about to implement and test with the TRANSMIT INHIBIT INPUT too for some special purpose. For success it's imported it queues the frames and TX-es them when the TXINH input is released. Therefore I'm curious about its behaviour too. Currently my thoughts are to use the TXINH input for a PTT interlock and DCD 'sharing' function as they're both not possible (yet) in software I think, or I missed something in the documentation... To prohibit the 2nd radio from TX-ing when the 1st radio is TX-ing OR receiving frames (or vice versa), I already made some circuitry which can toggle each channel's TXINH input. 73! Dave |
||
|
Re: Direwatch tft display driver for direwolf
开云体育That looks very nice Craig and some of your other projects on Github look pretty interesting as well!? Thanks for posting those. --David KI6ZHD On 07/10/2021 06:23 AM, Craig, KM6LYW
wrote:
|
||
|
Re: KISSPORT #### does not override 8001
I have used Direwolf on Pis and never seen this message with GPIO, or VOX.
Since this was a slightly different installation of my client, I looked through my APRS client to see if there were any settings (TXTAIL) that it changes to cause this.? The client does not change any settings. I glanced through the file around line 910 and worked in both directions. ?? Line 756 turns PTT ON ?? Line 860 seems to do TXTAIL timing, but I still don't see what it is "looking at" to determine PTT is still active - in this case there is nothing it CAN check. ?? And line 931 disable PTT The computer is a quad core AMD (4 thread) running 3.5 GHz.? Direwolf (2 audio channels) and APRSIS32 running under WINE was pretty much the only thing running.? That's much more than any Pi - even with the extra overhead of a desktop. |
||
|
Re: Audio Level Reporting (Inaccurate)
Audacity and or AlsaMixer are relative readings, similar to an uncalibrated S-meter. You can read the manuals and know what the radio is outputting - especially when using the radio's data jack.? They are typically about 300mVp-p for 1200 baud pin and 500mVp-p on the 9600 baud pin.? That is out of the Yaesu manual and I find others very similar. What you don't know is how "hot" the input circuit is on the sound card.? If using a mic input, many have pre-amps (typically called boost) that can heavily influence the readings. I have found some with adjustable boost, while others are set.? I think this is a way to use the same port as 'line in' or 'mic'. As David stated, adjust to a reading of 50 is the best way to get the most out of Direwolf, as that is using its internal 'strategy' to determine what it "likes". Robert Giuliano
On Saturday, July 10, 2021, 1:34:14 AM EDT, David Ranch <direwolf-groupsio@...> wrote:
Direwolf is really very forgiving on RX levels but the general guidance is that it's average receive level is around 50.? I can't comment on how the alsamixer setting might look within in a zoomed in Audacity but if Direwolf is happy, that's all that matters for proper decodes.? When in doubt, make your levels LOWER than 50 to avoid clipping, etc. --David KI6ZHD On 06/30/2021 06:53 PM, Michael - NA7Q
wrote:
I always setup my installs using Audacity to fine tune the receiver audio. I usually adjust it with an open squelch then put it around the 0.60-0.75 mark on the Audacity level. 1.0 is maximum and of couse I never get anywhere near that. I do this to check for any audio issues, like potentional noise, or just too much audio on the line. |
||
|
Re: USB audio problems; need recovery help
开云体育This is why I ONLY use HAT sound cards, like Fe-Pi, and now my soon to be released sound card HAT that's similar to the Fe-Pi. HATs have never given me issue. So that's what I suggest anyone do is use HATs where possible. Fe-Pi sound cards are no longer made, so that's unfortunate.? You can buy the Fe-Pi designed HAT from the new design owners below: ?? --David KI6ZHD |
||
|
Re: Audio Level Reporting (Inaccurate)
开云体育Direwolf is really very forgiving on RX levels but the general guidance is that it's average receive level is around 50.? I can't comment on how the alsamixer setting might look within in a zoomed in Audacity but if Direwolf is happy, that's all that matters for proper decodes.? When in doubt, make your levels LOWER than 50 to avoid clipping, etc. --David KI6ZHD On 06/30/2021 06:53 PM, Michael - NA7Q
wrote:
I always setup my installs using Audacity to fine tune the receiver audio. I usually adjust it with an open squelch then put it around the 0.60-0.75 mark on the Audacity level. 1.0 is maximum and of couse I never get anywhere near that. I do this to check for any audio issues, like potentional noise, or just too much audio on the line. |
||
|
Re: KISSPORT #### does not override 8001
开云体育The error came on a older x86_64 KUbuntu desktp homebrew computer, with the motherboard sound card, and no PTT setting (VOX).? Direwolf has "no clue' how the PTT is being handled. Ok.. that takes the iffy Raspberry Pi USB stack out of the running.
When no PTT is configured, it's assume you're using VOX or using a sound device like a Signalink that asserts PTT for you.? Per the previous thread found via Google, if you look at like 910 at: ?? You can see where this message is coming from but it's not totally clear why you're seeing this.? I would argue that ANY 64bit x86 machine should be more than fast enough but maybe it's under a lot of other load or something?? I've personally never seen this error. --David KI6ZHD |
||
|
Re: KISSPORT #### does not override 8001
The error came on a older x86_64 KUbuntu desktp homebrew computer, with the motherboard sound card, and no PTT setting (VOX).? Direwolf has "no clue' how the PTT is being handled.
toggle quoted message
Show quoted text
In fact, the testing was originally started with no radio connected at all.? How can the PTT be on for too long when thd non-connected radio has no connection to Direwolf to be measured (timed)?
|
||
|
Re: option digipeater no work in mi direwolf
开云体育Hello Alejandro, I would recommend to start with confirming that your HT can hear your Direwolf station (XE1GNU-1) beacons.? Per your configuration, those beacons should be sent every 5 minutes.? Is Direwolf keying up your radio?? Do you hear the modem burst on your HT?? If not, check your sound card mixer settings and make sure the levels are correctly set.?? Once you get past that, then we can help with any digipeating issue with Direwolf. --David KI6ZHD On 06/30/2021 11:13 PM, Alejandro G
Sánchez Martínez wrote:
Hello, I compiled on a raspberry pi zero W direwolf 1.6 as indicated in the manual, my intention is to configure an aprs repeter (digipeater). |
||
|
Re: KISSPORT #### does not override 8001
开云体育Hello Rob, If you google the following term: ?? direwolf "Transmit timing error: PTT is on" "mSec too long" You'll see a few hits and one one of these talks about the issue being known on non-Raspberry Pi 4 and newer hardware with it's older USB stack.? What hardware are you using with your setup?? If you are using older Raspberry Pi hardware, there is a workaround you can try: ?? --David KI6ZHD On 07/09/2021 07:19 AM, Rob Giuliano
via groups.io wrote:
|
||
|
Re: KISSPORT #### does not override 8001
I used the config file you proposed and it appears to be behaving now. I am getting an error 1.7-dev-A that is ????? Transmit timing error: PTT is on 104 mSec too long.? I am using VOX (no PTT settings), so not sure where this is coming from. The times vary from about 100 mSec too long to maybe 250 mSec too long This seems to be shorter ('too long time') and less often with the updated config.c file. With the original config.c, they were as long as 500 mSec. They only seem happen on TX from an attached client (either [0L] or [1L], but not both), or for PBEACON on the [1L] stream Robert Giuliano
On Thursday, July 8, 2021, 3:36:49 PM EDT, Brent WG0A <bjpetit@...> wrote:
I bumped into this when trying to run two separate instances of direwolf. One for VHF and one for HF. In that case I would see a collision on port 8001. After digging around a bit I found that the way to turn off the 8001 default is to set KISSPORT 0 before any other KISSPORT settings in the config.? I also proposed a code change to the KISSPORT default behavior here. https://github.com/wb2osz/direwolf/pull/333 |
