Date   

Re: lost audio out in wsjt-x

N5XMT
 

Best bet would be to open an issue on the wsjt-x github. It's obviously an issue with the sw and not a pi issue

On Jan 19, 2021, at 14:50, Jay Lijoi <lijoi@...> wrote:
Good day,

Here is what happens:

  • Using version wsjt-x 2.2.2 I lost audio out to my ic-7300
  • switched to 2.2.3 and all worked
  • 2.2.3 taken down by developer
  • reinstalled fresh 2.2.2 and no audio out
Equipment:
IC-7300
Raspberry PI 4 computer


I don't understand the difference between the two versions, but something is definitely different. As of now I can't operate wsjt-x.

Jay
WB2QQJ

#wsjt-x
#audio


lost audio out in wsjt-x

Jay Lijoi
 

Good day,

Here is what happens:

  • Using version wsjt-x 2.2.2 I lost audio out to my ic-7300
  • switched to 2.2.3 and all worked
  • 2.2.3 taken down by developer
  • reinstalled fresh 2.2.2 and no audio out
Equipment:
IC-7300
Raspberry PI 4 computer


I don't understand the difference between the two versions, but something is definitely different. As of now I can't operate wsjt-x.

Jay
WB2QQJ

#wsjt-x
#audio


Re: USB lock

David Birnbaum
 

I have done this for both my radio, Winkeyer and NanoVNA.  Works perfectly.  Independent of which USB port the radio is plugged into/

dave
k2lyv

Virus-free. www.avast.com


On Tue, Jan 19, 2021 at 12:02 PM John D Hays - K7VE <john@...> wrote:
You can create a udev rule which will make sure the IC-7300 always has a /dev file name that is consistent.  Udev rules files go in /etc/udev/rules.d

See example file content at: 
https://gist.github.com/peteonrails/fa99d57b58315a57631956c7e68f4d00

This should create a file /dev/ic7300 when you plug in your radio.  You can then use this instead of /dev/ttyUSBx and will be consistent between invocations.  /dev/ic7300 will be a dynamically assigned link to whichever /dev/ttyUSBx is assigned to the radio.



On Tue, Jan 19, 2021 at 8:21 AM Jay Lijoi <lijoi@...> wrote:
Good day,

I usually have to go to settings and pick my serial port, usually USB0 in my case, every time I start WSJT-X. Is there a way to have it connect to my ic-7300 consistently, or I'd this just the nature of Linux dynamic allocation of serial devices?

Jay
WB2QQJ
_,_



--
John D. Hays
Kingston, WA
K7VE

 


Re: USB lock

 

You can create a udev rule which will make sure the IC-7300 always has a /dev file name that is consistent.  Udev rules files go in /etc/udev/rules.d

See example file content at: 
https://gist.github.com/peteonrails/fa99d57b58315a57631956c7e68f4d00

This should create a file /dev/ic7300 when you plug in your radio.  You can then use this instead of /dev/ttyUSBx and will be consistent between invocations.  /dev/ic7300 will be a dynamically assigned link to whichever /dev/ttyUSBx is assigned to the radio.



On Tue, Jan 19, 2021 at 8:21 AM Jay Lijoi <lijoi@...> wrote:
Good day,

I usually have to go to settings and pick my serial port, usually USB0 in my case, every time I start WSJT-X. Is there a way to have it connect to my ic-7300 consistently, or I'd this just the nature of Linux dynamic allocation of serial devices?

Jay
WB2QQJ
_,_



--
John D. Hays
Kingston, WA
K7VE

 


USB lock

Jay Lijoi
 

Good day,

I usually have to go to settings and pick my serial port, usually USB0 in my case, every time I start WSJT-X. Is there a way to have it connect to my ic-7300 consistently, or I'd this just the nature of Linux dynamic allocation of serial devices?

Jay
WB2QQJ


Re: Argon One M.2 sata 3 2280

David [kg5eiu]
 

Here is what I have for the Argon case bottom
 


Re: Argon One M.2 sata 3 2280

 

What version of Buster are you using? I am trying current jan 2021 and can only see usb drive if I unplug dongle.
Don Ahlskog K4EAE
#35810 WiresX
Daytona Beach, FL


On Sun, Jan 17, 2021 at 9:51 PM David [kg5eiu] via groups.io <dcappello=aol.com@groups.io> wrote:
I bought just the bottom case and upgraded an existing Argon case - gallery with some photos at:
https://flic.kr/p/2km8EhK
I first booted off SD card validated EPROM on Pi was latest and updated - rebooted then loaded G-Parted 
and deleted the partition off the fresh M2.SATA Drive and then used the Pi Imager utility to write a fresh image to the M2 SATA Drive, then power
down removed the SD card and booted up from the M2.SATA Drive - works great and 
I have just under a Terabyte of storage - amazingly fast.  


Re: Argon One M.2 sata 3 2280

David [kg5eiu]
 

I bought just the bottom case and upgraded an existing Argon case - gallery with some photos at:
https://flic.kr/p/2km8EhK
I first booted off SD card validated EPROM on Pi was latest and updated - rebooted then loaded G-Parted 
and deleted the partition off the fresh M2.SATA Drive and then used the Pi Imager utility to write a fresh image to the M2 SATA Drive, then power
down removed the SD card and booted up from the M2.SATA Drive - works great and 
I have just under a Terabyte of storage - amazingly fast.  


Re: Argon One M.2 sata 3 2280

N5XMT
 

Also, the M.2 drive must be a SATA M.2 drive, not NVMe or PCIe

On Jan 17, 2021, at 10:49, David Ranch <rpi4hamradio-groupsio@...> wrote:

As I understand it, the Argon case includes a USB to SATA M2 adapter connected via the USB "U connector".  I assume you've been connecting that as it's REQUIRED.  If you have been but the SATA M.2 isn't being seen, if you have a working SD card to boot from, try removing the U connector and boot up the Rpi from the SD card.  Now run "dmesg" in a terminal window and see where the text output ends.  Now plug in the USB U-connector and run dmesg again.  Do you see the drive?  Does it show errors?

I also assume you've partitioned and formatted the M.2 drive.  Without that, yes, /dev/sda should be recognized but it won't do anything with it.

--David
KI6ZHD


On 01/16/2021 10:21 AM, Don A wrote:
Linux isn't recognizing the drive. I can plug the case into my mac and no problems. I have tried installation multiple time but drive doesn't come up as /dev/sda1?


Re: Argon One M.2 sata 3 2280

David Ranch
 


As I understand it, the Argon case includes a USB to SATA M2 adapter connected via the USB "U connector".  I assume you've been connecting that as it's REQUIRED.  If you have been but the SATA M.2 isn't being seen, if you have a working SD card to boot from, try removing the U connector and boot up the Rpi from the SD card.  Now run "dmesg" in a terminal window and see where the text output ends.  Now plug in the USB U-connector and run dmesg again.  Do you see the drive?  Does it show errors?

I also assume you've partitioned and formatted the M.2 drive.  Without that, yes, /dev/sda should be recognized but it won't do anything with it.

--David
KI6ZHD


On 01/16/2021 10:21 AM, Don A wrote:
Linux isn't recognizing the drive. I can plug the case into my mac and no problems. I have tried installation multiple time but drive doesn't come up as /dev/sda1?


Re: Argon One M.2 sata 3 2280

Perry Ogletree
 
Edited

Have you been able to boot from a USB device before? I just ran into an issue with a new, just out of the box, RPi 4B that refused to boot via USB. I found that the EEPROM boot order was at fault and using raspi-config wouldn't fix the issue. I had to follow these directions to change the boot order...
https://www.raspberrypi.org/documentation/hardware/raspberrypi/bcm2711_bootloader_config.md
I used the suggested "0xf41" as the new boot order selection.

Perry K4PWO


Re: Long serial cable issue

Ray Wells
 

Welcome to the house of Murphy.

Ray vk2tv

On 17/1/21 5:28 am, dtmenges via groups.io wrote:
Lots of good discussion and I should have checked the obvious. I sketched out the cable and then miscounted the pins on the 9-pin. Not sure how I did that when I only had to count 1-5 but I did. Probably not enough coffee. When I got the Tx and Rx on the right pins, everything worked.
_._,_._,_
------------------------------------------------------------------------


Argon One M.2 sata 3 2280

 

Linux isn't recognizing the drive. I can plug the case into my mac and no problems. I have tried installation multiple time but drive doesn't come up as /dev/sda1?


Re: Long serial cable issue

dtmenges@...
 

Lots of good discussion and I should have checked the obvious. I sketched out the cable and then miscounted the pins on the 9-pin. Not sure how I did that when I only had to count 1-5 but I did. Probably not enough coffee. When I got the Tx and Rx on the right pins, everything worked.


Re: FW: [RaspberryPi-4-HamRadio] Long serial cable issue

Dave
 

Thanks Don,

I am looking for some of the extenders.

Not a big issue.

Dave KC3AM

On 01/16/2021 10:25, Don Woodward wrote:
A short haul modem will extend the serial over 4 wires - I used a Blackbox branded one in the 80's to connect a terminal in the alumni house which was about a mile from the office where our main system was.� I believe they can go several miles.

Don W.
KD4APP


From: RaspberryPi-4-HamRadio@groups.io <RaspberryPi-4-HamRadio@groups.io> on behalf of Dave via groups.io <kc3am@...>
Sent: Wednesday, January 13, 2021 5:43 PM
To: RaspberryPi-4-HamRadio@groups.io <RaspberryPi-4-HamRadio@groups.io>
Subject: Re: FW: [RaspberryPi-4-HamRadio] Long serial cable issue
�
Fred,

Sorry, I should have typed 150 feet. I am trying to control a tower top TX that has RS-232 as the input for the laptop interface.

I have tried to talk to the TX at 19200 with no luck.

Dave KC3AM

On 01/13/2021 14:27, Fred Hillhouse wrote:

Just to be specific, you did type 150 inches. It should handle that without issue as long. Of course, that depends on baud rate. Up to 19200 should be fine but YMMV.

If you meant 150 feet it will probably still depend on baud rate. I have never run 150�. Today I would probably figure out how to accomplish it over a network.

�

Fred N7FMH

�

From: RaspberryPi-4-HamRadio@groups.io [mailto:RaspberryPi-4-HamRadio@groups.io] On Behalf Of Dave via groups.io
Sent: Wednesday, January 13, 2021 2:12 PM
To: RaspberryPi-4-HamRadio@groups.io
Subject: Re: FW: [RaspberryPi-4-HamRadio] Long serial cable issue

�

Talking about RS232 cable length,� will RS-232 run 150" on cat 5 and if so what baud rate would be necessary.

Dave KC3AM

On 01/13/2021 10:44, Fred Hillhouse wrote:

If your USB cable is 20� to the adapter, that would likely be a problem.

If your RS232 cable is 20�, that should not be an issue unless you are running at a very high baud rate.

�

A method for troubleshooting is the add a loop back on the dub connector (short pins 2 and 3). Run terminal software to send data. You should see the same character returned.

�

Fred N7FMH

�

From: RaspberryPi-4-HamRadio@groups.io [mailto:RaspberryPi-4-HamRadio@groups.io] On Behalf Of dtmenges via groups.io
Sent: Wednesday, January 13, 2021 10:31 AM
To: RaspberryPi-4-HamRadio@groups.io
Subject: [RaspberryPi-4-HamRadio] Long serial cable issue

�

I'm running (or trying to run) an MFJ-1270B from an Pi 3 B+ and an IO Gear serial adaptor. However, when I go to a long cable, approximately 20 feet, I don't get any communications. A six foot cable works fine. This is the only USB device on the Pi as I am running it headless.� I'm thinking that the Pi can't swing the voltage over a longer cable. Barring a 1d10t error in the cable construction, would a powered hub improve this situation?

Thanks,
Dave
WB9TEN

�


Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com



�

--
Hams should be seen as well as heard, 73, Dave KC3AM


--
Hams should be seen as well as heard, 73, Dave KC3AM

--
Hams should be seen as well as heard, 73, Dave KC3AM


Re: FW: [RaspberryPi-4-HamRadio] Long serial cable issue

Don Woodward
 

A short haul modem will extend the serial over 4 wires - I used a Blackbox branded one in the 80's to connect a terminal in the alumni house which was about a mile from the office where our main system was.  I believe they can go several miles.

Don W.
KD4APP


From: RaspberryPi-4-HamRadio@groups.io <RaspberryPi-4-HamRadio@groups.io> on behalf of Dave via groups.io <kc3am@...>
Sent: Wednesday, January 13, 2021 5:43 PM
To: RaspberryPi-4-HamRadio@groups.io <RaspberryPi-4-HamRadio@groups.io>
Subject: Re: FW: [RaspberryPi-4-HamRadio] Long serial cable issue
 
Fred,

Sorry, I should have typed 150 feet. I am trying to control a tower top TX that has RS-232 as the input for the laptop interface.

I have tried to talk to the TX at 19200 with no luck.

Dave KC3AM

On 01/13/2021 14:27, Fred Hillhouse wrote:

Just to be specific, you did type 150 inches. It should handle that without issue as long. Of course, that depends on baud rate. Up to 19200 should be fine but YMMV.

If you meant 150 feet it will probably still depend on baud rate. I have never run 150’. Today I would probably figure out how to accomplish it over a network.

 

Fred N7FMH

 

From: RaspberryPi-4-HamRadio@groups.io [mailto:RaspberryPi-4-HamRadio@groups.io] On Behalf Of Dave via groups.io
Sent: Wednesday, January 13, 2021 2:12 PM
To: RaspberryPi-4-HamRadio@groups.io
Subject: Re: FW: [RaspberryPi-4-HamRadio] Long serial cable issue

 

Talking about RS232 cable length,  will RS-232 run 150" on cat 5 and if so what baud rate would be necessary.

Dave KC3AM

On 01/13/2021 10:44, Fred Hillhouse wrote:

If your USB cable is 20’ to the adapter, that would likely be a problem.

If your RS232 cable is 20’, that should not be an issue unless you are running at a very high baud rate.

 

A method for troubleshooting is the add a loop back on the dub connector (short pins 2 and 3). Run terminal software to send data. You should see the same character returned.

 

Fred N7FMH

 

From: RaspberryPi-4-HamRadio@groups.io [mailto:RaspberryPi-4-HamRadio@groups.io] On Behalf Of dtmenges via groups.io
Sent: Wednesday, January 13, 2021 10:31 AM
To: RaspberryPi-4-HamRadio@groups.io
Subject: [RaspberryPi-4-HamRadio] Long serial cable issue

 

I'm running (or trying to run) an MFJ-1270B from an Pi 3 B+ and an IO Gear serial adaptor. However, when I go to a long cable, approximately 20 feet, I don't get any communications. A six foot cable works fine. This is the only USB device on the Pi as I am running it headless.  I'm thinking that the Pi can't swing the voltage over a longer cable. Barring a 1d10t error in the cable construction, would a powered hub improve this situation?

Thanks,
Dave
WB9TEN

 


Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com



 

--
Hams should be seen as well as heard, 73, Dave KC3AM


--
Hams should be seen as well as heard, 73, Dave KC3AM


Re: HSMM-Pi

 


After having worked with HSMM Mesh, I have seen an apparently-older Pi image for something called the HSMM-Pi, which implements a mesh network node on a Raspberry Pi with WIFI added for the connectivity.

Has anyone implemented a new version of HSMM-Pi or maintained the code base/image so it can be used these days?
It's on the list... Everything is on the list. Best idea for
several reasons is to just use the newer better hardware radios from
the list of supported platforms on ardenmesh.org.

https://www.arednmesh.org/content/supported-platform-matrix


Re: FW: [RaspberryPi-4-HamRadio] Long serial cable issue

Dave
 

Thanks for this link Dallas.

Dave KC3AM

On 01/14/2021 07:43, Dallas N4DDM via groups.io wrote:
RS-232 is only good to 50 feet...  To go farther you need to translate from RS-232 to 422 or 485 and then reverse that at the far end...
And the device you select cannot be just an adapter...  There must be electronics to drive the signals...
https://www.optcore.net/difference-between-rs-232-rs-422-and-rs-485/

73 Dallas N4DDM

--
Hams should be seen as well as heard, 73, Dave KC3AM


Re: Long serial cable issue

Dave
 

Thanks for this link Pierre.

Dave KC3AM

On 01/13/2021 21:23, Pierre Martel wrote:
long distance serial high speed?


I come from the security business and we used rs-485 for links between access system control. It can even do point to point or point to multipoint.

And those module are dirt cheap.

Pierre
VE2PF

Le mer. 13 janv. 2021 à 20:55, Chuck K4RGN <K4rgn@...> a écrit :
RS-232 promised 9600 b/s at 50 feet. Even in the late 1970s, 9600 was still darned fast. Leased line modems that did 14.4 or 19.2 kb/s hit the market after 1980 and the Bell System was just beginning to offer 56 kb/s DDS as an alternative to analog "wideband". I've always thought it was serendipity that RS-232 turned out to be useful at more than 10X the speeds that its designers called for. Most RS-232 interfaces back then were driven with 9 V or more, for example using the ubiquitous 1488 and 1489. Over time, TTL levels and then 3 V became popular. Noise immunity? Not. The RS-422/423 standards were meant for higher speeds but they never attained the traction that RS-232 did.
 
KI6ZHD is correct. A serial cable can be a nice antenna for UHF, VHF, or even 10 meters (which will become more popular as the sunspot count increases). Beware. Think in terms of quarter-wavelengths. I've seen the i2c lines from a Pi have trouble with RFI.

73 Chuck K4RGN 

--
Hams should be seen as well as heard, 73, Dave KC3AM


Re: Long serial cable issue

bbillp
 

Long cables accumulate capacitance and resistance which at the extreme round off the square wave and decrease the peak voltage resulting in errors, this is especially true with poor quality wire cables instead of Quality cable made for RS-232 with shielded and twisted pairs. Scoping the line will reveal this condition. The other issue is the RS-232 serial voltage level, if 0 to +5 like so many USB converters then problems are exaggerated. RS-232 spec is greater than +/- 9V and typically it is +/- 12 volts and thats what you will find on a commercial TNC/modems/serial printers/medical equipment.

Check the cable manufactures specs because there are special cables for long distances or switch over to RS-422 converters and 4 wire cable, rather extreme for the ham station but I thought I would mention it. Before WiFi we used RS-422 in large factories and hospitals where the runs were up to 1000 feet.

As far as the serial speed APRS transmissions are only 1200 baud serial, Packet is 1200 Baud and VERY FEW 2meter/70CM radios are capable of reliable 9600 baud serial so the TNC does not have to be at 9600, anyway the TNC input and output has data buffers so data is not lost. Bill K6ACJ

361 - 380 of 13214