Linux and MicroHAM USB3 - Versionsgeschichte

Dl8rds am 12. Mai 2021 um 10:04 Uhr

2021-05-12T10:04:50Z

Dl8rds am 22. Januar 2017 um 18:56 Uhr

2017-01-22T18:56:13Z

Dl8rds: Die Seite wurde neu angelegt: „Project Scope Recently I purchased a microHAM USB 3 interface which is supposed to work with our Kenwood TS-870S. It is supposed to be used from our Raspb…“

2017-01-20T19:14:31Z

Die Seite wurde neu angelegt: „Project Scope Recently I purchased a microHAM USB 3 interface which is supposed to work with our Kenwood TS-870S. It is supposed to be used from our Raspb…“

Neue Seite

[[Project Scope]]

Recently I purchased a microHAM USB 3 interface which is supposed to work with our Kenwood TS-870S. It is supposed to be used from our RaspberryPi3 club station computer.

Since we do not use Windows but Linux all the way, and since there is no really good documentation how to get it up and running, here is my collected experience.

[[Implementation]]

The advantage of the microHAM USB 3 ist that it does not require an additional sound card and it is thus perfectly suited for operation with the Raspberry Pi.

In order to access all the devices on it, you first need to make sure to load the according USB sound support. This is what should come up in /var/log/syslog:

<pre>
Jan 20 19:13:56 db0rc kernel: [ 769.401659] usb 1-1.2: new full-speed USB device number 8 using dwc_otg
Jan 20 19:13:56 db0rc kernel: [ 769.505056] usb 1-1.2: New USB device found, idVendor=0451, idProduct=2036
Jan 20 19:13:56 db0rc kernel: [ 769.505080] usb 1-1.2: New USB device strings: Mfr=0, Product=1, SerialNumber=0
Jan 20 19:13:56 db0rc kernel: [ 769.505093] usb 1-1.2: Product: General Purpose USB Hub
Jan 20 19:13:56 db0rc kernel: [ 769.508555] hub 1-1.2:1.0: USB hub found
Jan 20 19:13:56 db0rc kernel: [ 769.509162] hub 1-1.2:1.0: 2 ports detected
Jan 20 19:13:57 db0rc kernel: [ 769.781652] usb 1-1.2.1: new full-speed USB device number 9 using dwc_otg
Jan 20 19:13:57 db0rc kernel: [ 769.903735] usb 1-1.2.1: New USB device found, idVendor=08bb, idProduct=29c2
Jan 20 19:13:57 db0rc kernel: [ 769.903759] usb 1-1.2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jan 20 19:13:57 db0rc kernel: [ 769.903773] usb 1-1.2.1: Product: USB AUDIO CODEC
Jan 20 19:13:57 db0rc kernel: [ 769.903785] usb 1-1.2.1: Manufacturer: BurrBrown from Texas Instruments
Jan 20 19:13:57 db0rc kernel: [ 769.908294] input: BurrBrown from Texas Instruments USB AUDIO CODEC as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2.1/1-1.2.1:1.3/0003:08BB:29C2.0002/input/input1
Jan 20 19:13:57 db0rc kernel: [ 769.962201] hid-generic 0003:08BB:29C2.0002: input,hidraw0: USB HID v1.00 Device [BurrBrown from Texas Instruments USB AUDIO CODEC] on usb-3f980000.usb-1.2.1/input3
Jan 20 19:13:57 db0rc mtp-probe: checking bus 1, device 9: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2.1"
Jan 20 19:13:57 db0rc mtp-probe: bus: 1, device: 9 was not an MTP device
Jan 20 19:13:57 db0rc kernel: [ 770.041660] usb 1-1.2.2: new full-speed USB device number 10 using dwc_otg
Jan 20 19:13:57 db0rc kernel: [ 770.170491] usb 1-1.2.2: New USB device found, idVendor=0403, idProduct=eeef
Jan 20 19:13:57 db0rc kernel: [ 770.170505] usb 1-1.2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jan 20 19:13:57 db0rc kernel: [ 770.170512] usb 1-1.2.2: Product: USB Interface III
Jan 20 19:13:57 db0rc kernel: [ 770.170518] usb 1-1.2.2: Manufacturer: microHAM
Jan 20 19:13:57 db0rc kernel: [ 770.170524] usb 1-1.2.2: SerialNumber: U30LEVBP
Jan 20 19:13:57 db0rc kernel: [ 770.178590] ftdi_sio 1-1.2.2:1.0: FTDI USB Serial Device converter detected
Jan 20 19:13:57 db0rc kernel: [ 770.178699] usb 1-1.2.2: Detected FT232RL
Jan 20 19:13:57 db0rc kernel: [ 770.179482] usb 1-1.2.2: FTDI USB Serial Device converter now attached to ttyUSB0
Jan 20 19:13:57 db0rc mtp-probe: checking bus 1, device 10: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2.2"
Jan 20 19:13:57 db0rc mtp-probe: bus: 1, device: 10 was not an MTP device
</pre>

← Nächstältere Version		Version vom 12. Mai 2021, 10:04 Uhr
Zeile 72:		Zeile 72:

	Relating to FLDIGI 3.23.20 there is a little restriction with CW: Keying is only provided through Audio Out, and NOT via the DTR line. There are programs that can key the DTR line, but FLDIGI cannot as of now. FLDIGI can switch the DTR line, but it simply does not attach it to the CW keying. I hope there will be a patch soon, but I cannot tell.		Relating to FLDIGI 3.23.20 there is a little restriction with CW: Keying is only provided through Audio Out, and NOT via the DTR line. There are programs that can key the DTR line, but FLDIGI cannot as of now. FLDIGI can switch the DTR line, but it simply does not attach it to the CW keying. I hope there will be a patch soon, but I cannot tell.
		+
		+	== Notes about WSJT ==
		+
		+	Thanks to Thorsten Sinning DG3KBQ, who provided the following information:
		+
		+	He's operating the MicroHAM USB3 interface with a ICOM 7100 TRX over the CV- I interface:
		+
		+
		+	Serial interface /dev/ttyUSB0
		+	Speed: 19200
		+	Stoppbit: 1
		+	Datenbits: 8
		+	Parity: N
		+	PTT switching over /dev/ttyUSB0 using RTS
		+
		+	The only drawback is volume control. He says he can only reach about a quarter of full power no matter how much volume is up. The interface therefore is:
		+
		+	hw:Card=Codec, dev=0
		+
		+	Torsten points out that it is most important to set the jumper accordingly, but this is explained in the manual right at the beginning anyway. In any case such weird things as virtual serial interfaces are unnecessary in Linux.

@@ Zeile 1: / Zeile 1: @@
-[[Project Scope]]
+== Project Scope ==
 Recently I purchased a microHAM USB 3 interface which is supposed to work with our Kenwood TS-870S. It is supposed to be used from our RaspberryPi3 club station computer.
@@ Zeile 5: / Zeile 5: @@
 Since we do not use Windows but Linux all the way, and since there is no really good documentation how to get it up and running, here is my collected experience.
-[[Implementation]]
+== Implementation ==
 The advantage of the microHAM USB 3 ist that it does not require an additional sound card and it is thus perfectly suited for operation with the Raspberry Pi.
-In order to access all the devices on it, you first need to make sure to load the according USB sound support. This is what should come up in /var/log/syslog:
+In order to access all the devices on it, you first need to make sure to load the according USB sound support.
 <pre>
-Jan 20 19:13:56 db0rc kernel: [  769.401659] usb 1-1.2: new full-speed USB device number 8 using dwc_otg
+....
 </pre>