Msi2500SDR - Revision history

Bertrik Sikken: /* rtl_433 */

2023-03-14T15:40:07Z

rtl_433

← Older revision		Revision as of 15:40, 14 March 2023
Line 101:		Line 101:
	rtl_433 -d driver=miri -v		rtl_433 -d driver=miri -v
	or		or
	rtl_433 -d driver=~~SoapyMiri~~ -v ~~(TODO: check)~~		rtl_433 -d driver=soapyMiri -v

	=== libmiri + sdrangel ===		=== libmiri + sdrangel ===

Bertrik Sikken: /* Soapy SDR */

2023-03-14T15:39:33Z

Soapy SDR

← Older revision		Revision as of 15:39, 14 March 2023
Line 63:		Line 63:

	Support for the msi2500:		Support for the msi2500:
	* install the soapy driver:		* install the soapy 'miri' driver:
	sudo apt install soapysdr-module-mirisdr		sudo apt install soapysdr-module-mirisdr
	* try to find it with SoapySDRUtil		* try to find it with SoapySDRUtil

Bertrik Sikken: /* Introduction */

2023-03-08T15:49:22Z

Introduction

← Older revision		Revision as of 15:49, 8 March 2023
Line 14:		Line 14:

	On this page, I'm documenting how to get it to work effectively under Linux.		On this page, I'm documenting how to get it to work effectively under Linux.

			Although this thing seems technically superior to the well-known rtl-sdr dongle , in fact my personal experience with it has been 'meh' so far:
			* drivers are not very mature, there are so many to choose from but it appears there's not a single good one that "just works" (TM)
			* many tools that work out-of-the-box for rtl-sdr simply don't work with this dongle, for example
			** rtl_433, should be supported through soapy, have not yet seen a single decode
			** dump1090, doesn't work, in fact there is no input for signals > 1 GHz on my receiver
			** sdrangel works with it, but often crashes randomly (that might just be sdrangel instability)

	= Hardware =		= Hardware =

Bertrik Sikken: /* Soapy SDR */

2023-03-07T16:48:50Z

Soapy SDR

← Older revision		Revision as of 16:48, 7 March 2023
Line 58:		Line 58:
	* install the soapy driver:		* install the soapy driver:
	sudo apt install soapysdr-module-mirisdr		sudo apt install soapysdr-module-mirisdr
	* try to find in SoapySDRUtil		* try to find it with SoapySDRUtil
	SoapySDRUtil --find		SoapySDRUtil --find
	should result in (for example):		should result in (for example):
Line 66:		Line 66:
	label = Mirics MSi2500 default (e.g. VTX3D card)		label = Mirics MSi2500 default (e.g. VTX3D card)
	miri = 0		miri = 0
			</pre>
			or
			<pre>
			Found device 4
			driver = soapyMiri
			index = 0
			label = Mirics MSi2500 default (e.g. VTX3D card) :: 00000001
			manufacturer = Mirics
			product = MSi2500
			serial = 00000001
	</pre>		</pre>
	* try to open with SoapySDRUtil		* try to open with SoapySDRUtil
	SoapySDRUtil --probe="driver=miri"		SoapySDRUtil --probe="driver=miri"
	~~results in~~		or
	~~<pre>~~		SoapySDRUtil --probe="driver=soapyMiri"
	~~Probe device~~ driver=~~miri~~
	~~Using device #0: Mirics MSi2500 default (e.g. VTX3D card)~~
	~~usb_claim_interface error -6~~
	~~Error probing device: Failed to open mirisdr device.~~
	~~</pre>~~

	~~This can be 'fixed' by unloading and blacklisting the msi001 and msi2500 linux kernel drivers.~~

	==== SoapyMiri driver ====		==== SoapyMiri driver ====
Line 83:		Line 86:
	Works together with https://github.com/ericek111/libmirisdr-5 .		Works together with https://github.com/ericek111/libmirisdr-5 .

	This is an alternative SoapySDR driver for 'soapysdr-module-mirisdr' package as described. This one identifies as "soapyMiri" ~~(TODO: check)~~ instead of simply "miri".		This is an alternative SoapySDR driver for 'soapysdr-module-mirisdr' package as described. This one identifies as "soapyMiri" instead of simply "miri".

	=== rtl_433 ===		=== rtl_433 ===

Bertrik Sikken: /* Other packages */

2023-03-07T12:23:54Z

Other packages

← Older revision		Revision as of 12:23, 7 March 2023
Line 138:		Line 138:
	=== Other packages ===		=== Other packages ===
	To be investigated:		To be investigated:
	* https://github.com/ericek111/SoapyMiri
	* https://github.com/AlexandreRouma/SDRPlusPlus		* https://github.com/AlexandreRouma/SDRPlusPlus

Bertrik Sikken: /* SoapyMiri driver */

2023-03-07T12:23:35Z

SoapyMiri driver

← Older revision		Revision as of 12:23, 7 March 2023
Line 82:		Line 82:
	See https://github.com/ericek111/SoapyMiri .		See https://github.com/ericek111/SoapyMiri .
	Works together with https://github.com/ericek111/libmirisdr-5 .		Works together with https://github.com/ericek111/libmirisdr-5 .

	This is an alternative SoapySDR driver for 'soapysdr-module-mirisdr' package as described. This one identifies as "soapyMiri" (TODO: check) instead of simply "miri".		This is an alternative SoapySDR driver for 'soapysdr-module-mirisdr' package as described. This one identifies as "soapyMiri" (TODO: check) instead of simply "miri".

Bertrik Sikken: /* SoapyMiri driver */

2023-03-07T12:23:23Z

SoapyMiri driver

← Older revision		Revision as of 12:23, 7 March 2023
Line 82:		Line 82:
	See https://github.com/ericek111/SoapyMiri .		See https://github.com/ericek111/SoapyMiri .
	Works together with https://github.com/ericek111/libmirisdr-5 .		Works together with https://github.com/ericek111/libmirisdr-5 .
	This is an alternative ~~to the~~ 'soapysdr-module-mirisdr' package described ~~above that identifies itself as "miri" towards SoapySDR~~.		This is an alternative SoapySDR driver for 'soapysdr-module-mirisdr' package as described. This one identifies as "soapyMiri" (TODO: check) instead of simply "miri".

	This ~~is a driver for the soapy framework,~~ identifies as "~~soapMiri~~" (TODO: check) instead of simply "miri" ~~(in the driver described above)~~.

	=== rtl_433 ===		=== rtl_433 ===

Bertrik Sikken: /* rtl_433 */

2023-03-07T12:21:19Z

rtl_433

← Older revision		Revision as of 12:21, 7 March 2023
Line 91:		Line 91:
	Now it can also use soapy as an input, for example		Now it can also use soapy as an input, for example
	rtl_433 -d driver=miri -v		rtl_433 -d driver=miri -v
			or
			rtl_433 -d driver=SoapyMiri -v (TODO: check)

	=== libmiri + sdrangel ===		=== libmiri + sdrangel ===

Bertrik Sikken: /* Soapy SDR */

2023-03-07T12:20:45Z

Soapy SDR

← Older revision		Revision as of 12:20, 7 March 2023
Line 53:		Line 53:

	=== Soapy SDR ===		=== Soapy SDR ===
	~~Still not completely sure what it does~~, read for example https://github.com/pothosware/SoapySDR/wiki		Soapy SDR is a driver framework for several SDR devices, read for example https://github.com/pothosware/SoapySDR/wiki

	Support for the msi2500:		Support for the msi2500:
Line 80:		Line 80:

	==== SoapyMiri driver ====		==== SoapyMiri driver ====
	See https://github.com/ericek111/SoapyMiri		See https://github.com/ericek111/SoapyMiri .
			Works together with https://github.com/ericek111/libmirisdr-5 .
	Works together with https://github.com/ericek111/libmirisdr-5		This is an alternative to the 'soapysdr-module-mirisdr' package described above that identifies itself as "miri" towards SoapySDR.

	This is a driver for the soapy framework, identifies as "soapMiri" (TODO: check) instead of simply "miri" (in the driver described above).		This is a driver for the soapy framework, identifies as "soapMiri" (TODO: check) instead of simply "miri" (in the driver described above).

Bertrik Sikken: /* Linux */

2023-03-07T12:18:56Z

Linux

@@ Line 35: / Line 35: @@
 The thing that worked best for me, is the libmiri package by f4exb, together with SDR software sdrangel (also by f4exb)
 === Soapy SDR ===
@@ Line 75: / Line 91: @@
 Now it can also use soapy as an input, for example
    rtl_433 -d driver=miri -v
 === libmiri + sdrangel ===