Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- DINAH
- Messages
Search
File /DINAH V4 Construction Manual_v4.0.pdf uploaded
#file-notice
[email protected] Notification
The following files have been uploaded to the Files area of the [email protected] group. By: N8AR Description: |
Re: [direwolf] Problems with DINAH on Raspberry PI 3+
You open an interesting question.? And I believe the answer is nuanced based on: - application?of the soundcard interface - the details of the transceiver I am going to give my best understanding?based on my work with Echolink and a variety of digital modes including Direwolf. My belief is that the DINAH and other Allstar type interfaces are designed for the Allstar modes which are basically voice modes of which?Echolink is a subset. My experience with Echolink has been that the signal needs to have squelch applied at the radio end because it is difficult?to discriminate in software between a voice signal?and noise.? As such if squelch is off the software believes that the radio is always receiving?a signal and will not allow transmission. When I use digital?modes as you note in general?one wants to have squelch off to allow detection of low level digital signals and the software?can discriminate the digital signals out of the noise. As AllStar is a voice mode predominantly the carrier on signal implemented in hardware is an excellent design choice. However when a sound interface with hardware implemented?COS is used for digital modes, the COS line is now potentially problematic.? If the squelch?signal is high indicating receive then COS will disable the transmission and I have had systems effectively?lock up in receive only mode. I have two different configurations for my signallink?interfaces depending on whether it is used for voice or digital modes to work?around this problem. In my present implementation: - I am providing a radio only link to a digipeater about?0.6 miles away which does not have internet access:? I don't need to decode weak signals, the digipeater will do that - my present transceiver?will have Squelch high all the time if squelch is disabled Disabling hardware COS is the simplest solution, but having squelch on for this?use of Direwolf is not a problem for this application and reduces software load for random signals. This is a more general question?of how to have a multipurpose voice and digital mode? sound interface which I am still muttering on.? And? this is compounded by different delay latencies for the PTT line depending on the details of the mode. But thanks for the observation: in general you are correct, for Direwold?one would not want squelch on. Thanks! On Wed, Dec 16, 2020 at 3:20 PM David Ranch <direwolf-groupsio@...> wrote:
AB1PH Don Rolph |
Re: Problems with DINAH on Raspberry PI 3+: issue resolved: I appear ot have damaged my DINAH
OK at Stephen Smith's N8AR suggestion I went and rechecked the behavior of the DINAH on my Raspberry PI 2 and 3+. The previous?testing had been: - worked as expected on Raspberry PI 2:? speaker sound level was high?during transmit even after receiving a squelch signal - did not work as expected on Raspberry PI 3+: spoundlevel on speaker?channel?was set to zero during a squelch singal?and did not return to normal levels and transmit was suppressed I moved to the Raspberry PI 3+ because the Raspberry PI 2 USB was unstable with the DINAH, a wifi dongle, and a bluetooth dongle for keyboard/mouse. I cobbled together a stable test environment on the Raspberry?PI 2 and: - did not work as expected on either? Raspberry PI 3+: or Raspberry PI 2: spoundlevel on speaker?channel?was set to zero during a squelch signal?and did not return to normal levels and transmit was suppressed I must conclude that I damaged the DINAH during the testing and that leads to the present behavior. My apologies for raising the issue and My thanks to Stephen for? his assistance, We can consider this issue closed. On Wed, Dec 16, 2020 at 9:08 AM Don Rolph <don.rolph@...> wrote:
--
AB1PH Don Rolph |
Re: Problems with DINAH on Raspberry PI 3+
Where in the circuit did you confirm the squelch is performing as expected?? Have you looked at it on the anode of D1 on the DINAH PCB?
Pin 48 of the CM108B on DINAH (COS input) is pulled high (about 3.3 volts) by the CM108B.? An open drain FET on the RS-UV3 pulls pin 48 low (about .2 volts) through D1 when the FET is turned on. The RS-UV3 manual says "COR output - Low when squelch is open, open circuit when squelch is closed".? ?Are you sure you have the polarity for COR (COS) set up correctly in Dire Wolf? |
Re: Problems with DINAH on Raspberry PI 3+
ok this is much too small for my eyes to detect properly BUT it appears when I test the diode it is either blown OR unsoldered. It is much too fine a soldering job for me to handle. Thoughts? On Wed, Dec 16, 2020 at 10:51 AM N8AR <n8ar73@...> wrote: Please check the solder joints on D1.? We have had a report of a unit with one end not soldered. --
AB1PH Don Rolph |
Re: Problems with DINAH on Raspberry PI 3+
An RS-UV3 digitally controlled radio from HobbyPCB. I have confirmed that the squelch signal is performing?as expected. On Wed, Dec 16, 2020 at 10:28 AM Basil Gunn <basil@...> wrote:
--
AB1PH Don Rolph |
Re: Problems with DINAH on Raspberry PI 3+
I will check. On Wed, Dec 16, 2020 at 10:51 AM N8AR <n8ar73@...> wrote: Please check the solder joints on D1.? We have had a report of a unit with one end not soldered. --
AB1PH Don Rolph |
Re: Beware of DIN cables
I have a Yaesu CT-175 it is also 6pin to 10 pin din. It is the HRI-200 specified cable I believe the cable designations are identical. I used it to try linking a DINAH to a DR2X Yaesu repeater and found it only works 1/2 duplex. (as transcievers like a FTM-300DR is 1/2 duplex.)
It's for sale. I paid $29.95 plus shipping. I ship it to you for that same $29.95. Contact me w8lm at arrl dot net |
Re: Problems with DINAH on Raspberry PI 3+
If I use alsamixer to up the volume on the speaker just before the transmission, then the signal is heard. The next received signal silences the DINAH card and no further transmissions are heard until I manually increase the volume on the DINAH card. It appears that the COS is not behaving properly on the DINAH card on a Raspberry PI 3+ using Direwolf 1.6 I really don't?want to disconnect the COS signal, but that appears to be what is required?for proper performance. It seems there is a general COS signal handling problem on the D"iNAH card which shows up on Raspberry?PI 3+ and on Windows. Thoughts? On Wed, Dec 16, 2020 at 9:08 AM Don Rolph <don.rolph@...> wrote:
--
AB1PH Don Rolph |
Problems with DINAH on Raspberry PI 3+
I am using a DINAH and either a Raspberry PI 2 or 3+ using the Direwolf 1.6 software When I connect?the DINAH? to a Raspberry PI 3+, an incoming?signal enables Squelch, the volume of the DINAH output goes down but does not return to normal?when Squelch is dropped. This means I can receive?fine but can not send. This actually mirrors a problem I saw on Windows. I can obviously cut the COS line, but this disables?the hardware check for channel busy. Thoughts? Thanks! AB1PH Don Rolph |
Re: selecting 9600 baud
I could easily modify the layout so that JP1 selected 1200 or 9600YES. Confirmed. I modified a cable so that pin 4 9600 baud receive input from a radio (TM-V71a) connected to pin 5 1200 baud receive input on DINAH which is what one of your suggested changes does. I tested @ 9600 baud with direwolf and it worked very well. The other change you have suggested that allows a pin 6 SQL/COS disconnect would be helpful for the Yaesu multi band radios (FT817/FT857FT897). /Basil n7nix |
Problems with DINAH
I am having problems with a DIANH interface I am using: - windows?7 laptop - ARPSISCE32?APRS software? using the AGW interface port - the UZ7HO sound? modem software with AGW enabled - DINAH sound interface - either a Yaesu FT817ND using the data port or a PCB Hobby RS-UV3 with a? homie?made cable - The?first problem seems to surround carrier on sense:?If this is connected to the squelch line of an FT817 or a PCB Hobby RS-UV3 the sound?card is disabled. - If I disconnect this line on the RS-UV3 the green light on the DINAH and the DCD light on the sound?modem card goes on and off regularly - it does not appear?that te?PTT?line?is being activated: soundmodem sees the signal, but the RS-UV3 transmit light does not come on and no RF is transmitted - if the 1200 baud line from?the transmitter?is connected to the sound out from?the DINAH card, the volume control goes to zero. Both configurations work fine if I use a TNC-X TNC system, so it is the DINAH/UX+Z7HO sound? modem combination which is not working. I seem to be terminally confused. Thoughts? Thanks! AB1PH Don Rolph |
Re: selecting 9600 baud
Hi Steve,
I configured direwolf to use DINAH as a sound device @ 1200 baud when I initially received the kit. It was straight forward and easy to do. I have been wanting a path to programatically switch between 1200 & 9600 baud packet for a while. I demonstrated how to do that manually, using scripts running on a Raspberry Pi at the 'APRS Summer Gathering' (North Bend, WA) a couple of years ago. Recently I wrote some scripts to remotely change the baud rate of a gateway using Touch Tones. I just finished that project and will be updating the README some time today. I am now focused on using PulseAudio and virtual sound devices to run both the 1200 & 9600 direwolf modems on the same audio channel. The hard part is virtualizing the PTT method. I am fairly certain I can get this to work. Both the Touch Tone method & the virtual sound device method could work on DINAH after I make a cable that routes the radio discriminator output (mDin 6 pin 4) to the DINAH input (mDin 6 pin 5) There is a requirement that a 'good' digital capable radio must be used. I am currently using a Kenwood TM-V71A. 1200 baud packet works quite well using the radio's discriminator output which is usually labeled 9600 baud. This means that when switching baud rates everything is done in software and radio configuration does not need changing. This is a long way around to saying YES to: Would these changes be useful in order to use DINAH for DireWolf?However, I think you might wait a bit until I make a cable that routes mDin 6 pin 5 (1200) from DINAH to mDin 6 pin 4 (9600) on the radio to get confirming data that this will work for the DIANH audio device. I could also add another jumper that could be cut (normally connected)It is my experience that the Yaesu multi band radios (FT817/FT857/FT897) do something different with the mDin6 pin 6 line (squelch) then iCom or Kenwood radios. Removing mDin6 pin 6 fixed the problem with the NW Digital Radio DRAWS audio codec device () /Basil n7nix Alexander Moore <kitsforhams@...> writes: JP1 was intended to either have a way to bring CTCSS into DINAH using |
Re: selecting 9600 baud
JP1 was intended to either have a way to bring CTCSS into DINAH using a custom cable or supply 5 VDC to something that DINAH was plugged into.? I could easily modify the layout so that JP1 selected 1200 or 9600 baud (normally connected for 1200 baud).? I would then also delete D2 and C10.? I could also add another jumper that could be cut? (normally connected) so that COS could be disconnected.? Here is what I propose:
?
?
Would these changes be useful in order to use DINAH for DireWolf?
?
Steve - N8AR
?
?
|
Re: no transmit - when giving commands
Since all DTMF commands begin with the asterisk, check again to be sure that it is being decoded.
Also, you can set and check your DTMF tone levels more accurately using the method described in this document (?Setting the RX Level in HamVOIP Allstar.pdf? ) located in the FIles section of this group. Steve - N8AR |
Re: no transmit - when giving commands
¿ªÔÆÌåÓýWhat tones are you entering? ? -Michael ? From: [email protected] <[email protected]>
On Behalf Of ham@...
Sent: Saturday, November 21, 2020 10:29 PM To: [email protected] Subject: [DINAH] no transmit - when giving commands ? I have a dinah connected to a Yeasu FT8800 |
to navigate to use esc to dismiss