Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[RFI\]\s+SolarEdge\s+RFI\s+Update\s+Final\s+\-\s+They\s+Won\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[RFI\]\s+SolarEdge\s+RFI\s+Update\s+Final\s+\-\s+They\s+Won\s*$/: 2 ]

Total 2 documents matching your query.

1. [RFI] SolarEdge RFI Update Final - They Won (score: 1): Author: Tony <dxdx@optonline.net>; Date: Tue, 18 Aug 2020 16:20:22 -0400; All: Just got word from SolarEdge that they will not go any further to solve the RFI problem being caused by their installation here in New York. They've made marginal improvements with chokes and an; /archives//html/RFI/2020-08/msg00010.html (7,315 bytes)
2. Re: [RFI] SolarEdge RFI Update Final - They Won (score: 1): Author: "EDWARDS, EDDIE J via RFI" <rfi@contesting.com>; Date: Tue, 18 Aug 2020 20:40:30 +0000; Has the ARRL been involved at this point? If not, they should be. Then ARRL can trigger an FCC letter to the owner-operator of the device if they cannot get the customer and vendor to respond to ARRL; /archives//html/RFI/2020-08/msg00011.html (8,647 bytes)

Current List: 1 - 2
Page: [1]