28MHz WSPR

 Steppir 3e 70m! coax working fine . The SOLAR EDGE  QRM is solved by the company placing new type optimisers and new cabling all noise and carriers gone, halleluja! Solar Edge did a good job here ( after 3 years) they solved the problem , they kept there promise . 

  All bogus decodes striped out , i was the only one decoded in Antarctica !  and the only North EU that decoded PY3FF this time 

Timestamp	Call	MHz	SNR	Drift	Grid	Pwr	Reporter	RGrid	km	az	Mode	# Spots
2021-05-14 14:14	3K3SOY	28.126076	-21	0	BD80	20	DL0HT	JO43jb	18152	100	2	1
2021-05-14 06:00	F91QSM	28.126094	-30	0	BE90	0.2	ON3URE	JO20cw	17561	73	2	1
2021-05-14 16:22	SM7PNV	28.125992	-17	-2	AA00	0.2	EI4GGB	IO63ik	16002	172	2	3
2021-05-14 13:40	P56QNI	28.126092	-26	0	CF12	100	CT2IWW	IN51wf	15668	68	2	1
2021-05-14 22:26	VK1PVJ	28.126123	-33	0	PF06	0.02	CT2IWW	IN51wf	15500	296	2	1
2021-05-14 16:22	SM7PNV	28.126027	-22	-1	AA00	0.2	DO1MTU	JN58vc	15409	191	2	1
2021-05-14 13:26	ZY2L	28.126052	-22	1	OD23	501	G7VKQ	IO91xl	15329	296	2	1
2021-05-14 10:42	PA0O	28.126167	-27	0	JO33hg	5	DP0GVN/1	IB59ui	13830	186	2	1
2021-05-14 21:58	PY2TOW	28.126057	-27	2	GG66or	50	KH6KR	BL10ts	12825	283	2	1
2021-05-14 19:08	M0ILZ	28.126146	-29	0	LE50	0.2	SM0FKI	JO89ug	12466	342	2	1
2021-05-14 23:32	VK2IJM	28.126091	-24	0	QF56ni	10	KK6PR	CN94ik	12373	50	2	2
2021-05-14 23:32	VK2IJM	28.126091	-23	-1	QF56ni	10	ND7M	DM16xf	12358	60	2	3
2021-05-14 23:32	VK2IJM	28.126162	-26	0	QF56ni	10	WA6JRW	DM14he	12146	61	2	2
2021-05-14 23:32	VK2IJM	28.126112	-23	0	QF56ni	10	K6RRP	DM12lw	12107	62	2	4
2021-05-14 23:32	VK2IJM	28.126110	-27	0	QF56ni	10	KP4MD	CM98iq	12076	55	2	2
2021-05-15 00:24	VK2IJM	28.126115	-26	0	QF56ni	10	WW6D	CM88pk	11954	55	2	1
2021-05-15 00:24	VK2IJM	28.126085	-27	0	QF56ni	10	K6PZB	CM88nk	11942	55	2	1
2021-05-14 22:40	VK2IJM	28.126094	-18	0	QF56ni	10	KFS	CM87tj	11923	56	2	6
2021-05-14 19:54	PY3FF	28.126138	-30	0	GF49ju	1	PA0O	JO33hg	10820	31	2	1
2021-05-14 17:58	PY3FF	28.126138	-20	0	GF49ju	1	KA7OEI-1	DN31uo	10140	319	2	1
2021-05-14 17:50	PY3FF	28.126112	-22	0	GF49ju	1	ND7M	DM16xf	10009	313	2	13
2021-05-14 19:24	PY3FF	28.126122	-22	0	GF49ju	1	K6RRP	DM12lw	9854	310	2	4
2021-05-14 10:40	OL8EFB	28.126000	-26	0	OK20	0.1	ON3URE	JO20cw	9844	322	2	1
2021-05-14 14:28	OQ5DAQ	28.126070	-27	0	DL42	0.5	ON3URE	JO20cw	9698	35	2	1
2021-05-14 21:58	PY2TOW	28.125993	-24	0	GG66or	50	WB5DYG	DM43ff	9297	310	2	1
2021-05-14 11:40	JM1DRW	28.126151	-23	0	JF93	5	F4CWN	JN03kn	9090	347	2	1
2021-05-14 14:50	PY3FF	28.126100	-29	0	GF49ju	1	CT2IWW	IN51wf	9087	31	2	1
2021-05-14 15:20	OH5XO	28.126119	-20	0	KP41ca	0.2	FY5KE	GJ35	9004	265	2	8

Experienced  EMC problem with USB audio devices  of above type 7.1 Channel sound

QRM signature: strong RF spark type pulses at 144 and 432 MHz  annoying strong.. 

Those USB audio adapters are offered as low as 1€ !  + shipping at AliExpress or eBay

They work without extra drivers instantly in W7/10  and offer audio channels for digital modes.

I use 2 of them  simultane  the default system is kept free the extra audio channels do not interfere  system audio. 

They support DVD  48kb/s speed, no specs about AD/DA resolution guess 8bits ? 

Once saw a very rough blocked shape sinus output  causing multiple audio traces, but after reset this was fixed. Monitor the  FT8 signal is a good thing.

(b.t.w.  General when using WSPR unattended  one must be reachable by email or mobile.

   My signal also got disturbed 1 day and 3 HAM's  mailed me it, was better to  be reachable by           Whatsapp

   Some HAMS are complete unreachable like a PA1 at 80m having 4 or more multiple decodes many   weeks now, but no email / telephone and not logged in at WSPRNET.ORG  ,complete anonymous.     

)

Oké, To continue,  About these cheap USB audio devices but they generate strong spark type pulses at 144 and 432 MHz and in between!

All my 5 USB audio plugs produce his spark type QRM so the issue is reproducible. 

Using good fer-rite clamps with multiple winding  over a short USB extension cable helped.

But while testing an other rig with USB -Audio the cracks where  very loud again at 144 

Plugged in an USB hub this QRM was gone! , not sure if all USB  hubs can do that.

But this was an easy solution of the QRM problem plus the advantage of having more USB 2 type slots available.

Some HAM's report no RFI problems with this device maybe because using some other type USB slot.

My experience is that data bus systems like USB cause QRM , f.i. the internal device bus in the K3.

Even  Winkeyer USB suffers high QRM S9 at 14MHz,  Grounding the USB connector case to the ground of the K3 brought it down from  S9 to S1 

left 7.1 channel USB audio right USB serial for Kenwood TS811E CAT 70cm all mode set's in use at PI4GN. The Sweex silenced the VHF/UHF pulses from the USB-AUDIO.

Right is an USB/rs232 converter prolific chip  for the TS811E  CAT option.

I prefer FTDI types but this one works stable in Win10 

The CAT data connection does interfere with the modulation of the TS811E  on both rigs.

Signature:  cyclic  data puls train burst heard in modulation.

This is caused by bad or no shielding  and grounding of this data interface.

Grounding the USB connector case to the TS811E housing did the data rumble disappear almost 100%...  I had to ground the USB case in another EMC issue with the WinkeyUSB years ago. For unknown reason the USB devices are bad shielded even the ones that are ment to work with sensitive radio devices

TS811 CAT option well build rs232 interface. But...RTS DTR lines can not be used for T/R CW function   RTS needs to be kept high  or else the connection goes offline. No handshake function enabled  RTS  does not need to be connected with CTS or DSR inputs. I do not understand why other then TxD and RxD lines are used for this simple rig polling type communication?  
There are more things i do not understand.. f.i. why does N1MM rig communication stop polling with a "timeout error" if the rig communication is interrupted shortly for what ever reason.
 N1MM  comes up with an error message saying the rig comport xx os offline The program is halted and the user must click ok  , okay? , no not okay! Why not simply sign the communication status red and continue polling the rig to automatic reconnect?   
If this same procedure was used in internet communication and  every network interruption would bring an annoying popup be clicked away with "okay?"
  for something that is not okay what would you like that?