Date   
Re: Radiofax and RTTY from DWD Hamburg/Pinneberg.

tor schofield
 

Hej Martin,

Thank you for your reply, everything I have received has been most useful and I am now receiving DWD radiofax and RTTY.

Regards,

Tor OZ2TOR
Denmark


On 3 Mar 2019, at 20:50, Martin Van Mierlo <mwmierlo@...> wrote:

Hello Tor
I have some nowleds of DWD The best frequentie for dwd is 4583 khz USB In the fine program MultiPsk set the parameters to 50 baud reverse and 450 HZ shift for the mark and space They send plain tekst with info golfheigt temp. seawater and so one. Also 5 figures code with info from wheaterstations all over the world. For that press in MultiPsk  Synops ships and after some time you see the wheatercode.
I hope that you receive some info. 

73,  Martin

Op di 26 feb. 2019 19:44 schreef tor schofield <torschofield@...>:
Does anyone have any knowledge and experience in de-coding the above?



Re: Radiofax and RTTY from DWD Hamburg/Pinneberg.

Martin Van Mierlo
 

Hello Tor
I have some nowleds of DWD The best frequentie for dwd is 4583 khz USB In the fine program MultiPsk set the parameters to 50 baud reverse and 450 HZ shift for the mark and space They send plain tekst with info golfheigt temp. seawater and so one. Also 5 figures code with info from wheaterstations all over the world. For that press in MultiPsk  Synops ships and after some time you see the wheatercode.
I hope that you receive some info. 

73,  Martin

Op di 26 feb. 2019 19:44 schreef tor schofield <torschofield@...>:

Does anyone have any knowledge and experience in de-coding the above?



Re: Nooelec bare bottom LNAs faulty connection

Sergio Sarabia
 

The supply is delivered through the output connector, through the Bias-T activating it physically or by software from the SDR.

Re: Nooelec bare bottom LNAs faulty connection

Paul Gulliver
 

Roland,
The connector marked "Input" goes to the antenna, the connector marked "Output" goes to your dongle/receiver - the DC power feed is also on the "Output" side. When the DC feed is connected a small green led (next to the output connector) should light indicating power is reaching the LNA.
If you connected them incorrectly you have applied DC power to the input of the LNA, this may have damaged them.
I don't know how the Airspy bias tee works but on a V3 dongle the bias tee has to be switched on (or off) when any software is not using the dongle (ie close the software before switching the bias tee)
Sorry, can't help in repairing them, I suspect if they are damaged them throw them away - but test them first with the correct connections :)

Paul


On 03/03/2019 at 17:18, Roland Fechter <fly-fechter@...> wrote:
Hallo,
I got a couple of new Nooelec LNA for inmarsat-Outernet. (bare bottom version)
My problem is:
Each of them shows the mark "Input" and opposite side  the mark"Output".
Could you please tell me if the outlet marked "Input" serves for connection with my antenna
while the other side marked "output" serves for connection with my RX - dongle.
Probably I chose the wrong side in my haste as most of  my LNAs do not work properly.
Does using the wrong side cause a short circuit in the LNAs ruining their function ?
Even with my Aispy most of them do not work correctly - apparently despite clicking the Airspy  Bias Tee function my SDRsharp does not show
any signals above the noise level !
So please tell me how to Correctly connect these Nooelec LNAs - perhaps my remaining untested one could be still of use to me ?
Assuming that most of theme have been hit by short circuit due to incorrect connection by me could these be brought back to life somehow ?
Thanks in advance for your most valuable advice.
Regards,
Roland



These dong

Nooelec bare bottom LNAs faulty connection

Roland Fechter
 

Hallo,
I got a couple of new Nooelec LNA for inmarsat-Outernet. (bare bottom version)
My problem is:
Each of them shows the mark "Input" and opposite side  the mark"Output".
Could you please tell me if the outlet marked "Input" serves for connection with my antenna
while the other side marked "output" serves for connection with my RX - dongle.
Probably I chose the wrong side in my haste as most of  my LNAs do not work properly.
Does using the wrong side cause a short circuit in the LNAs ruining their function ?
Even with my Aispy most of them do not work correctly - apparently despite clicking the Airspy  Bias Tee function my SDRsharp does not show
any signals above the noise level !
So please tell me how to Correctly connect these Nooelec LNAs - perhaps my remaining untested one could be still of use to me ?
Assuming that most of theme have been hit by short circuit due to incorrect connection by me could these be brought back to life somehow ?
Thanks in advance for your most valuable advice.
Regards,
Roland



These dong

Re: RTL disconnect

Fred Albertson
 

Hi Mauro,

I checked my files and the "rtl_sdr.txt" file has a creation date of 5/18/2018.

That is also the "Date Modified" for all of the MultiPSK "PAIR#.TXT" and "??.SER"
files in the MultiPSK directory.  There are other files dated the same.  It is probably
the date of a previous MultiPSK installation on my machine.  When I update
MultiPSk, I copy only recently changed files to the MultiPSk directory to prevent
overwriting data that I have collected or modified, unless Patrick says otherwise.

I'm sorry, but that is all know about it's source.

Good luck on the troubleshooting.

Fred


Re: RTL disconnect

Patrick Lindecker
 

Hello Mauro,

For Patrick: The error indicated in the configuration screen is -12, does
this mean anything to you?
Yes of course. Read one of my previous emails for the solution.

73
Patrick

-----Message d'origine-----
De : multipsk@groups.io [mailto:multipsk@groups.io] De la part de pelix21
Envoyé : dimanche 3 mars 2019 10:53
À : multipsk@groups.io
Objet : Re: [multipsk] RTL disconnect

Thanks everybody for the comments, I am glad to see that in most stuations
Win10 is running fine.  At this point I would like to check a possible
device problem, how do you get the "rtl_sdr.txt" file shown by Fred? I did
not find any in my computer.

For Patrick: The error indicated in the configuration screen is -12, does
this mean anything to you?

Mauro





---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus

Re: RTL disconnect

pelix21
 

Thanks everybody for the comments, I am glad to see that in most stuations Win10 is running fine.  At this point I would like to check a possible device problem, how do you get the "rtl_sdr.txt" file shown by Fred? I did not find any in my computer.

For Patrick: The error indicated in the configuration screen is -12, does this mean anything to you?

Mauro

Re: RTL disconnect

Patrick Lindecker
 

Hello Mike,

 

> I have Zadig 2.2 and have never had any problem with running/installing dongles.

>No recent Windows 10 updates have made any differences.

Interesting as it is not systematic (and much better if the standard is “no problem”).

 

73

Patrick

 

De : multipsk@groups.io [mailto:multipsk@groups.io] De la part de MadMike
Envoyé : samedi 2 mars 2019 22:48
À : m
ultipsk@groups.io
Objet : Re: [multipsk] RTL disconnect

 

I have 2 PCs here, both running Windows 10 64 bit version and always with latest updates. I have Zadig 2.2 and have never had any problem with running/installing dongles. No recent Windows 10 updates have made any differences.

 

Regards, Mike Simpson

South Penrith, NSW, Australia

 

 




Avast logo

L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
www.avast.com


Re: RTL disconnect

agene
 

I have 2 PCs here, both running Windows 10 64 bit version and always with latest updates. I have Zadig 2.2 and have never had any problem with running/installing dongles. No recent Windows 10 updates have made any differences.

Regards, Mike Simpson
South Penrith, NSW, Australia


Re: RTL disconnect #EEProm reprogrammation #eeprom

Patrick Lindecker
 

Thanks Dick for the trick about the possibility to reprogram the EEProm of a dongle. I don't know that it was possible.

73
Patrick

-----Message d'origine-----
De : multipsk@groups.io [mailto:multipsk@groups.io] De la part de Dick
Envoyé : samedi 2 mars 2019 13:58
À : multipsk@groups.io
Objet : Re: [multipsk] RTL disconnect

On Fri, Mar 1, 2019 at 09:05 PM, Patrick Lindecker wrote:


Do you know what version of Zadig you use?
For the test I did related to thread https://groups.io/g/multipsk/message/1504
I used zadig-2.4.exe on my 64bit Win 10 (up-to-date) laptop and have not seen any problems.

What I have seen in the past is that if the dongle has lost part of the configuration (serialnumber, manufacturer) then some programs fail to recognize the dongle but programs work well.
That is why I wanted to know if the problem was dongle, machine or software related.

73, Dick




---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus

Re: RTL disconnect #EEProm reprogrammation #eeprom

Patrick Lindecker
 

-----Message d'origine-----
De : multipsk@groups.io [mailto:multipsk@groups.io] De la part de Dick
Envoyé : samedi 2 mars 2019 13:58
À : multipsk@groups.io
Objet : Re: [multipsk] RTL disconnect

[Edited Message Follows]
[Reason: More details on a problem I had in the past.]

On Fri, Mar 1, 2019 at 09:05 PM, Patrick Lindecker wrote:


Do you know what version of Zadig you use?
For the test I did related to thread https://groups.io/g/multipsk/message/1504
I used zadig-2.4.exe on my 64bit Win 10 (up-to-date) laptop and have not seen any problems.

What I have seen in the past is that if the dongle has lost part of the configuration (serialnumber, manufacturer) then some programs fail to recognize the dongle but other programs work well.
I just found my notes on that issue.
"quote"
When the dongle (sn: 00000005) is connected to my Win10 Laptop and using Zadig the Zadig log shows this:
libwdi:debug [wdi_create_list] WinUSB USB device (2): USB\VID_0BDA&PID_2832\77771111153705700
libwdi:debug [wdi_create_list] Device description: 'RTL2832U'
This Device description 'RTL2832U' is wrong, it should be 'RTL2838UHIDIR'
Also the Serialnumber '77771111153705700' is wrong, it should be '00000005'

After I used rtl-eeprom to restore the dongle's EEprom with the default factory settings all worked fine.
rtl_eeprom can be found in "RelWithDebInfo.zip" from "http://osmocom.org/projects/sdr/wiki/rtl-sdr"
This is the command I used (on my RPi): rtl_eeprom -g realtek

The EEprom of the dongle became corrupted due to power problems on my RPi.
Actually it happened to two dongles and I sucesfully restored both.
"unquote"

That is why I wanted to know if the problem was dongle, machine or software related.

73, Dick




---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus

Re: RTL disconnect

Patrick Lindecker
 

Hello Fred,

 

RR for all.

 

>I have had no changes in the performance of MultiPSK or the SDR's from the newest Win 10 updates.
There will be no reason of performance alteration as long as Windows 10 remains compatible with Win32. But W 10 complicates programmers work. For example Zadig 2.0.1 cannot install a driver on W10 due to a problem of identification. Zadig 2.4 solves the problem, but now Windows leaves the installation of the driver but without considering it... Thanks to Internet where you can find solutions given by other users.  

 

73

Patrick

 

 

 

De : multipsk@groups.io [mailto:multipsk@groups.io] De la part de Fred Albertson
Envoyé : samedi 2 mars 2019 14:50
À : multipsk@groups.io
Objet : Re: [multipsk] RTL disconnect

 

OK Patrick,

Just a bit more info:  The PC is 64-bit hardware and is fully updated.

The operating system software is:

Windows 10 Home, Version 1803, OS build 17134.590.  That
is current to this morning.

I am not running any of the programs in "Compatability Mode."

I have had no changes in the performance of MultiPSK or the
SDR's from the newest Win 10 updates.

Maybe I'm just lucky...

Fred




Avast logo

L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
www.avast.com


Re: RTL disconnect

Fred Albertson
 

OK Patrick,

Just a bit more info:  The PC is 64-bit hardware and is fully updated.

The operating system software is:

Windows 10 Home, Version 1803, OS build 17134.590.  That
is current to this morning.

I am not running any of the programs in "Compatability Mode."

I have had no changes in the performance of MultiPSK or the
SDR's from the newest Win 10 updates.

Maybe I'm just lucky...

Fred

Re: RTL disconnect

Dick
 
Edited

On Fri, Mar 1, 2019 at 09:05 PM, Patrick Lindecker wrote:


Do you know what version of Zadig you use?
For the test I did related to thread https://groups.io/g/multipsk/message/1504
I used zadig-2.4.exe on my 64bit Win 10 (up-to-date) laptop and have not seen any problems.

What I have seen in the past is that if the dongle has lost part of the configuration (serialnumber, manufacturer) then some programs fail to recognize the dongle but other programs work well.
I just found my notes on that issue.
"quote"
When the dongle (sn: 00000005) is connected to my Win10 Laptop and using Zadig the Zadig log shows this:
libwdi:debug [wdi_create_list] WinUSB USB device (2): USB\VID_0BDA&PID_2832\77771111153705700
libwdi:debug [wdi_create_list] Device description: 'RTL2832U'
This Device description 'RTL2832U' is wrong, it should be 'RTL2838UHIDIR'
Also the Serialnumber '77771111153705700' is wrong, it should be '00000005'

After I used rtl-eeprom to restore the dongle's EEprom with the default factory settings all worked fine.
rtl_eeprom can be found in "RelWithDebInfo.zip" from "http://osmocom.org/projects/sdr/wiki/rtl-sdr"
This is the command I used (on my RPi): rtl_eeprom -g realtek

The EEprom of the dongle became corrupted due to power problems on my RPi.
Actually it happened to two dongles and I sucesfully restored both.
"unquote"

That is why I wanted to know if the problem was dongle, machine or software related.

73, Dick

Re: RTL disconnect

Patrick Lindecker
 

Hello Fred,

 

Thanks for the information.

 

It seems that the last W10 updates complicate implementation of non-Windows drivers for, I presume, computer security reason.

 

What is sure is that 32 bits DLL work for 64 bits (ouf!).

 

73

Patrick

 

De : multipsk@groups.io [mailto:multipsk@groups.io] De la part de Fred Albertson
Envoyé : samedi 2 mars 2019 00:10
À : multipsk@groups.io
Objet : Re: [multipsk] RTL disconnect

 

Hi Patrick and Mauro,

I use 2 sdr's with Multipsk on a 64 bit Win 10 PC.  I have
had no issues.  They also operate on SDR# and HDSDR and
RTL1090.exe just fine.

Zadig version is:  2.4

rtlsdr.dll is file version 1.0.0.1 from http://sdr.osmocom.org/trac/wiki/rtl-sdr

RTL_SDR.txt file reads:

Generic_RTL2832U_R820T_Generic_RTL2832U_77771111153705700 0 -65 137211407 9 A
Generic_RTL2832U___ 0 -67 1537700000 9 A
ezcap_USB_2.0_DVB-T/DAB/FM_dongle_Unknown___ -64 0 1090000000 : A
ezcap_USB_2.0_DVB-T/DAB/FM_dongle_R820T_Realtek_RTL2838UHIDIR_00000001 0 66 137262587 9 A
ezcap_USB_2.0_DVB-T/DAB/FM_dongle_Realtek_RTL2838UHIDIR_00000001 0 66 137425081 9 A
ezcap_USB_2.0_DVB-T/DAB/FM_dongle___ 0 -66 1090000000 : A

Hope this helps you in your quest.

Great evening,

Fred







Avast logo

L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
www.avast.com


Re: RTL disconnect

Fred Albertson
 

Hi Patrick and Mauro,

I use 2 sdr's with Multipsk on a 64 bit Win 10 PC.  I have
had no issues.  They also operate on SDR# and HDSDR and
RTL1090.exe just fine.

Zadig version is:  2.4

rtlsdr.dll is file version 1.0.0.1 from http://sdr.osmocom.org/trac/wiki/rtl-sdr

RTL_SDR.txt file reads:

Generic_RTL2832U_R820T_Generic_RTL2832U_77771111153705700 0 -65 137211407 9 A
Generic_RTL2832U___ 0 -67 1537700000 9 A
ezcap_USB_2.0_DVB-T/DAB/FM_dongle_Unknown___ -64 0 1090000000 : A
ezcap_USB_2.0_DVB-T/DAB/FM_dongle_R820T_Realtek_RTL2838UHIDIR_00000001 0 66 137262587 9 A
ezcap_USB_2.0_DVB-T/DAB/FM_dongle_Realtek_RTL2838UHIDIR_00000001 0 66 137425081 9 A
ezcap_USB_2.0_DVB-T/DAB/FM_dongle___ 0 -66 1090000000 : A

Hope this helps you in your quest.

Great evening,

Fred





RTL disconnect

Patrick Lindecker
 

Mauro,

 

As I said, you must have an error number on the bottom of the Configuration screen. Which is it?

 

If it is 12, it means that either the installation of the driver made by Zadig has not been done or (as in your case) the driver installed by Zadig is not considered by Windows 10 (“it turns out that Windows 10 defaults to treating the RTL-SDR as a "composite" device and auto installs its own driver for it.”).

 

The solution is there:  https://www.rtl-sdr.com/forum/viewtopic.php?t=2031

In fact, it is just enough to uncheck the “Ignore Hubs or Composite Parents”  in the Options menu.

 

73

Patrick

 

De : Patrick Lindecker [mailto:f6cte@...]
Envoyé : vendredi 1 mars 2019 18:27
À : 'multipsk@groups.io'
Objet : RE: [multipsk] RTL disconnect

 

Hello Mauro,

 

Is your PC a 64 bits or a 32 bits (I have never tried in a 64 bits PC and it can be the reason of the problem, so a Multipsk problem)? Perhaps there are users having a feedback about Multipsk using RTL/SDR on a 64 bits PC?

 

You must have an error number on the bottom of the Configuration screen. Which is it?

 

About DLL. You could possibly use the last official dll, but I’m almost sure that it will not change anything (first make a backup of the Multipsk dll):

·  Download the official RTL-SDR Windows release from http://sdr.osmocom.org/trac/attachment/wiki/rtl-sdr/RelWithDebInfo.zip.

·  Copy the libusb-1.0.dll, rtlsdr.dll and pthreadVC2-w32.dll files from the official RTL-SDR Windows release zip file to your Multipsk folder.

 

73

Patrick

 

 

De : multipsk@groups.io [mailto:multipsk@groups.io] De la part de pelix21
Envoyé : vendredi 1 mars 2019 12:36
À : multipsk@groups.io
Objet : Re: [multipsk] RTL disconnect

 

Hi all
I am also experiencing similar problem with RTL-SDR on a new computer with WIN10 . I have installed Multipsk 4.38 outside "Program" directory and it in general  works fine, it also accepts "Direct input" from a Funcube dongle.

I also spent some time to get the RTL dongle working with SDRSHARP (Zadig etc,) but now it works fine. So actual situation is:

MULTIPSK + FUNCUBE : OK
SDRSHARP + RTL : OK
MULTIPSK+ RTL: PROBLEM

When I try to set "DIrect input" from RTL I get an error window saying "problem on a rtl dll" and then lists rtlsdr, libusb-1.0 and msvcr100.  I just tried to replace above dll's with the ones currently working in SDRSHARP but no success.

Any suggestion on thingsd to check?  Thanks. Mauro




Avast logo

L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
www.avast.com


Re: RTL disconnect

Patrick Lindecker
 

Hello Dick,

It corresponds to what I read, i.e the 32 bits dlls for RTL/SDR work for 64 bits PC. So the problem is not about these dll.

Do you know what version of Zadig you use? This because, I read that the 2.0.1.154 version of Zadig works well but not the following versions?

73
Patrick

-----Message d'origine-----
De : multipsk@groups.io [mailto:multipsk@groups.io] De la part de Dick
Envoyé : vendredi 1 mars 2019 19:06
À : multipsk@groups.io
Objet : Re: [multipsk] RTL disconnect

On Fri, Mar 1, 2019 at 06:27 PM, Patrick Lindecker wrote:


Perhaps there are users having a feedback about Multipsk using RTL/SDR on a 64 bits PC?
Related to this thread
https://groups.io/g/multipsk/message/1504
I tried MultiPSK on my 64bit laptop and had no problem using the RTL-SDR dongle with Multipsk 4.38.1.

Cheers,
Dick




---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus

Re: RTL disconnect

Dick
 

On Tue, Feb 20, 2018 at 06:55 PM, Patrick Lindecker wrote:


Any dongle on any port on that machine gets disconnected.
Two questions:
1. Can you clarify "gets disconnected"?
Does this mean that it works fine for some time and then gets disconnected?

2. "on that machine"
So everything works fine on one machine but not on the other machine?
If true than it is machine specific! Correct?

Cheers,
Dick