Re: Good 2m rig?
Check out a recent script (wlgw-check.sh) I wrote for rig control of the tm-v71.
toggle quoted messageShow quoted text
https://github.com/n7nix/auto-rmsgw-find This script iterates through a list of RMS gateways using a TM-V71a and Hamlib rigctl /Basil
On May 31, 2019 5:43:34 PM PDT, Keith Williamson <hkwilliamson@...> wrote:
|
|
Re: Good 2m rig?
Keith Williamson
I now have a TM-V71a connected to my UDRC and am trying to get rigctl to work with it. I have an equivalent of a PG-5H connected to a serial/USB converter enumerated as /dev/ttyUSB0. My first test of the cable was with chirp and it seems to work fine. When I try ""rigctl -m 234 -r /dev/ttyUSB0 -vvvv", I see multiple read_string timeouts and then rigctl enters command mode. When I try "f" to get the current vfo frequency, I get multiple read_string timeouts and finally "get_freq: error = Communication timed out". Are there specific serial params needed to talk to the V71a? (e.g. RTS/CTS flow control, specific baud rate)? Thanks for any help! Keith KF7DRV
On Sat, May 25, 2019 at 4:13 PM Doug Henry <doug.henry1@...> wrote:
|
|
Yes
toggle quoted messageShow quoted text
On May 28, 2019, at 9:03 AM, John D Hays - K7VE <john@...> wrote:
|
|
toggle quoted messageShow quoted text
On Tue, May 28, 2019 at 8:54 AM k6acj <k6acj@...> wrote:
--
John D. Hays Kingston, WA K7VE
|
|
k6acj
I’ve been booting from the external Toshiba 500gig USB drive for years but the Pi still needs /boot on the SD card to read the configuration then continues booting from the external drive. In your case are you saying the SD card is completely eliminated if the PiDrive is used ?
toggle quoted messageShow quoted text
Building the external boot is not too hard: DD the SD image to the HD then figure out the Linux ID of the external HD, edit I think it is /boot/config.txt with the external ID and reboot. I wrote up the routine on the rasperry pi forums long ago but it should still be there, search boot external hard drive. Bill acj
On May 23, 2019, at 2:48 PM, John D Hays - K7VE <john@...> wrote:
|
|
okiejim
Thank you Christopher,
I kinda knew that but my attempt was to use the 12 volt input to power everything. I am using the draws in my RV/ToyHauler and 12volt amps do fluctuate during times of no hookups. I appreciate your help. I ended up using the PiDrive as my DNS server and NAS and the Draws will be separate for the radio work. The actual current draw will be less this way, as the radio/draws will not be on all of the time.
|
|
Re: 2m rig Update
Steve McGrane <temporarilyoffline@...>
Thanks for getting back to me. DRAWS Side: Pin 3/Orange writing 1 to pin 12 will raise voltage to 4.22v PTT light goes on Pin 3/Orange writing 0 to pin 12 will lower voltage to 3.6mv PTT light goes off Removing the cable I think is PTT on the radio side and touching the ground on the DRAWS side (Pin 5) results in open transmit until removed. New Development: If I have radio and DRAWS connected properly I can turn on PTT with CLI. When I turn off PTT at CLI, DRAWS PTT light goes out, THEN if I touch something to the PTT it adds enough resistance to pull the circuit down and turn off the radio. So I tried some resistors in-line: 1.0k = Too Much PTT wouldn't open ____? 820 = Close, works, but not very reliably 570 = Too Little PTT wouldn't close outside of that, I'm either out of ideas or parts. `gpio -g write 12 1 && sleep 1 && gpio -g write 12 0` Any thoughts are welcome?
On Mon, May 27, 2019 at 2:17 PM Basil Gunn <basil@...> wrote:
|
|
Re: 2m rig Update
Verify the DRAWS hat
toggle quoted messageShow quoted text
-------------------- Disconnect the cable from your radio but plug into DRAWS hat on the open connector put your volt meter on what you think is the PTT pin Manually turn the gpio for PTT on & off Left connector: PTT On: gpio -g write 12 1 PTT Off: gpio -g write 12 0 PTT Check: gio -g read 12 Right connector: PTT On: gpio -g write 23 1 PTT Off: gpio -g write 23 0 PTT Check: gio -g read 23 Verify your radio ----------------- Disconnect the cable from DRAWS hat & connect to radio. Ground the pin you think is the PTT pin ... did your radio transmit? Un-ground the PTT pin ... did the radio stop transmitting? /Basil Steve McGrane <temporarilyoffline@gmail.com> writes:
I got some time today (its raining!) to play with this.
|
|
Re: 2m rig Update
Steve McGrane <temporarilyoffline@...>
I got some time today (its raining!) to play with this. Initially the measure_deviation.sh script would run and not trip the PTT circuit. So I re-wired the cable and after looking more closely, I don't even understand why it worked in the first place. I think originally I had the speaker from the radio connected to the ground pin on the draws din6 connector??? maybe the ground is "noisy enough" that it got picked up elsewhere??? Here is my rewire: Radio MIC to DRAWS AFOUT Radio PTT to DRAWS PTT Radio GND to DRAWS GND Radio AFOUT to DRAWS AFIN (I'm guessing that a common ground would help out. The DRAWS and the radio are plugged into the same power supply, so this could also be creating a loop) And the results are that measure_deviate.sh will trip the PTT, but will not stop PTTing. The DRAWS will both send and receive APRS messages using XASTIR. XASTIR repeats the "text message" several times and has the same "won't stop PTTing" problem. So its progress... but it comes at a price. 1. Any ideas on the won't stop PTTing issue? 2. If you think I'm making a ground loop and shouldn't let me know. Thanks, - Steve
On Sat, May 25, 2019 at 8:19 PM Basil Gunn <basil@...> wrote:
|
|
Re: 2m rig Update
To debug PTT issues:
toggle quoted messageShow quoted text
Use the 'How to use measure_deviate.sh' notes here: https://github.com/nwdigitalradio/n7nix/tree/master/deviation Use left & right connector locations and either tune a second radio to the same frequency as your test radio so you can hear the tone or watch your radio to see if it transmits. If that doesn't work you have a cable problem. /Basil Steve McGrane <temporarilyoffline@gmail.com> writes:
Follow-up to the cable issue.
|
|
Re: 2m rig Update
Steve McGrane <temporarilyoffline@...>
Follow-up to the cable issue. I've double checked the setup. If I put the hand mic back in line and Press PTT, my receiving radio breaks squelch, so it would seem that the PTT circuit is not activating from DRAWS. I checked with Basil's notes and I've got PTT setup for 12 & 23. For grins, I've reversed the GPIO numbers and cables such that I've hit all combos of l/r ports and 12/13 GPIOs. still no joy. Any thoughts?
On Fri, May 24, 2019 at 7:25 PM Temporarily Offline <temporarilyoffline@...> wrote:
|
|
Re: Good 2m rig?
Doug Henry
Bill, 6 pin mini din 1200 and 9600 although I've only used on 1200. Doug VE1ZG
On Sat, 25 May 2019 at 19:59, Bill Vodall <wa7nwp@...> wrote: > The Icom IC-7000 has a data port that works well for packet.
|
|
Re: Good 2m rig?
The Icom IC-7000 has a data port that works well for packet.6 pin mini-din or other? 1200 baud and/or 9600 baud?
|
|
Re: Good 2m rig?
Doug Henry
The Icom IC-7000 has a data port that works well for packet. Doug VE1ZG
On Sat, 25 May 2019 at 16:24, WA7SKG via Groups.Io <wa7skg=yahoo.com@groups.io> wrote: You are comparing apples and oranges. The "Data Port" on ham radios is a
|
|
Re: Good 2m rig?
WA7SKG <wa7skg@...>
You are comparing apples and oranges. The "Data Port" on ham radios is a misnomer. It is a port for audio connections, just like the microphone jack. It typically has PTT, TX and RX audio (often from two locations in the radio for wide/narrow audio bandwidth), COS, and other signals. This is designed to use with some hardware interface (TNC, modem, etc.) or sound card (Signalink, etc.) device. Your USB connectors are for just that, USB connections for power and data transfer. Trying to use a mini-USB (4 pins) connector or micro-USB (5 pins) for an analog signal cable is a recipe for disaster.
toggle quoted messageShow quoted text
When manufacturers first started interfacing with radios, they simply used the microphone connector. This often required the use of an external switch box go go between the TNC and the microphone so the radio could be used for dual purposes. Then, users wanted to hook both devices simultaneously, plus wanted added features (discriminator tap for UHF packet, COS, etc.) The mini-DIN 6 pin connector was an industry standard at the time, used for PS/2 connections to computers and other purposes. Readily available, inexpensive, smaller than Molex or DB connectors, it was a good choice and became somewhat a standard for the purpose. So, hopefully, that may answer your "Why do so many of you want a DIN-6 port?" question. Your other comments regarding the different HT/computer interfaces, compatibilities between adapter/OS, drivers, baud rates, etc. are a totally different issue. That is regarding purely data interfaces via USB and converted serial data. Completely irrelevant to the conversation at hand. 73, Michael WA7SKG Al Szymanski via Groups.Io wrote on 5/24/19 2:01 PM:
Not so much as a reply , but a genuine question.
|
|
Christopher Warren
The problem you are experiencing is being caused by the lack of power to run the hard drive. Buy yourself a Y USB splitter to allow the drive to be powered from a separate supply. Make sure the voltage does not also supply the RPI. I had to cut the positive lead in the y splitter cable. So be careful.
On Sat, 25 May 2019, 21:00 okiejim, <kd6vpe@...> wrote: I just plugged the harddrive into a USB port on the Pi3. I now get the lightning bolt when the drvie is accessed. When idle the lightning bolt is not on. So it is working but un-sure at this point about other devices. I will run it this way over the weekend to see if it holds up. I do see all of the partitions I built with the WDLabs image so that is cool. I am running the beta13 image right now. I have mis-placed my ps2 female pig tail. When I find it I will solder up a connector for the 2m rig and see if I have enough power to drive the radio audio. More to come.
|
|
okiejim
I just plugged the harddrive into a USB port on the Pi3. I now get the lightning bolt when the drvie is accessed. When idle the lightning bolt is not on. So it is working but un-sure at this point about other devices. I will run it this way over the weekend to see if it holds up. I do see all of the partitions I built with the WDLabs image so that is cool. I am running the beta13 image right now. I have mis-placed my ps2 female pig tail. When I find it I will solder up a connector for the 2m rig and see if I have enough power to drive the radio audio. More to come.
|
|
okiejim
Success!!!
I unplugged all my accessories and also unhooked the drive power from the Pi. So I have two power inputs at this time. The Pi is powered by the 12 volts from the Draws Hat and the Drive is powered via the USB cable to and external USB charger. I have beta13 running and had it on all night. No smoke and still running. I have not hooked it up to a radio yet but I do suspect it will run fine. I will try a radio later on once I build up a cable. I plan to run Xastir with a TenTec 1220 2m kit. More to come. At this time I am not going to try to hook the drive up to the pi. I think that may have been the over draw that caused the smoke signal not sure yet but nothing burned out yet.
|
|
Draws hat
#draws
Rob Lapham
It would be nice to have a little more information
on shipping dates, and order status
|
|
Re: 2m rig Update
Steve McGrane <temporarilyoffline@...>
So far I can receive only. I'm getting a little screwed up in the pin labeling and what side of the cable I'm on. What I have so far: Cable from DRAWS w/end cut reveals Pin 6 Green Pin 5 Black Pin 4 Orange Pin 3 Yellow Pin 2 Brown Pin 1 Red Radio uses an RJ-45 MIC cable and a speaker audio Pin 1 N/C Pin 2 DC 8V Pin 3 GND Pin 4 PTT Pin 5 GND (MIC) Pin 6 MIC Pin 7 N/C Pin 8 DTMF Data Plus TRS on rear audio 1/8th jack I have DRAWS = Radio 1 = 6 2 = 5 3 = 4 4 = N/C 5 = Rear Speaker TIP 6 = N/C GND = N/C Any thoughts?
On Fri, May 24, 2019 at 6:47 PM David Lowry <huskyrunnr@...> wrote: https://imgur.com/iMaXWRR
|
|