Re: OCXO oscillator works fine but not recognized by my U3S
|
The MCU talks to the synth via I2C and expects answers in return, if this does not happen it will show an error. As the data lines goes through a level converter on the synth board, these too needs to be working properly for the communication to work. Scope the SDA/SCL lines on both the MCU and synth side and see if it gets through. If there's 5V clock/data on one side and 3.3V on the other, the synth could be bad. Otherwise there could be a problem with the level converters. If unlucky and there's 5V on the synth side it could be toasted.On Wed, Aug 23, 2017 at 9:37 AM, David Parker <dwparker@...> wrote: I have a number of ultimate 3s WSPR beacons up and running. I recently had an overvoltage issue with one of them which has damaged the OCXO, most likely the oven transistors as far as I can see. This unit is still recognized by the software (ver 3.11. However I decided to start afresh. I've finished the build of a new OCXO but not fully enclosed it yet. The oscillator tests out fine and is ok for frequency and level. However the OCXO is not recognized by the software. What is the software looking for as a valid unit? This may help me in further fault finding. I have a 100meh scope and 3gig spectrum analyser for fault finding.? |
Daniel Ekman SA2KNG