开云体育

Thanks Greg! I've been looking for something to measure SMD parts. dave, n3ds [email protected]> wrote:

Thanks! Just bought one. Looks like a reasonable tool. Dr. William J. Schmidt - K9HZ J68HZ 8P6HK ZF2HZ PJ4/K9HZ VP5/K9HZ PJ2/K9HZ VP2EHZ Owner - Operator Big Signal Ranch – K9ZC Staunton, Illinois

I have the FNIRSI tweezers: https://www.amazon.com/dp/B0DBQ4SQGK Pretty good!? Nice to have on the bench during assembly to double-check things. -- 73 Greg KF5N

Sorry, missed your comment... from the usermanual in the Amazon link. They are what they are, but for a ball park figure, perfect. I'm tempted to makeup a lead so I can use the tweezers with my rather

The two boards have a different clock speed (84 vs 72MHz).? It appears the spi frequency for the board can't be set to the 36MHz as is being done at the bottom of Setup32_ILI9341_STM32F103.h. Try

I have been using STM32F103 BluePill boards for several years without any major issues and have them driving ILI9341 TFT displays OK. I decided to try/experiment ?the STM32F401 and have a bought a

Ok thanks. I see what went wrong… that section was copied straight out of the BPF manual and unfortunately not updated. I can fix that. Dr. William J. Schmidt - K9HZ J68HZ 8P6HK ZF2HZ PJ4/K9HZ

The assembly manual T41_RF_Board_Assembly_Manual_V12_042324.docx was confusing in the following paragraph which I understood to say, use address "100": Thanks for all you do on this project. I am

You are quite welcome Dave… For feedback, which documentation is lacking to help avoid a problem here? Dr. William J. Schmidt - K9HZ J68HZ 8P6HK ZF2HZ PJ4/K9HZ VP5/K9HZ PJ2/K9HZ VP2EHZ Owner -

That was it!!!! Wrong address. Now all three boards work with varying receiver attenuation. Now I'm on to calibration. Thank you all for your help. dave, n3ds [email protected]> wrote:

Just so everyone knows. Repeating. A few months back, I separated the T41 boards and kits… from the K9HZ-KI3P boards and kits… by placing them is separate GITHUB directories. I did that because a

The primary RF board (that is the Primary RX and TX) should be set to 0x27 which means that the three address lines A0, A1, and A2 should be set to “111” or no shorted jumpers (J15, J16, J17). Dr.

ah yes. That mythical prototyping standard ... MIL TFD 4.1 "Make It Like The F***ing Drawing, For Once" !

I'm not in a position to try this, being more of a theoretical than a practical person (still not started on my T41) but musing, I wonder if one was to wind the wire loosely around a pencil or

Bill's right: you do not have the correct address for the MCP23017 chip. The I2C address is set by JP15, JP16 and JP17. The command "#define RF_MCP23017_ADDR" sets the address that the code looks for

The control MC23017 is not recognized on the board so its not gonna work no matter what. ALSO MAKE SURE THAT THE .CPP and .H FILES FOR RF CONTROL ARE PRESENT IN THE FILE YOU ARE COMPILING. If they are

No… looks like the control is not talking on the RF board. Here is a list of the reserved addresses (NOTE DON’T get hung up on 1st receiver or Second receiver… they could be either by changing

You can scope the control wires going to the attenuators. They're just DC levels. For the receive attenuator, the signals are U21 pin 21 ( .5dB ) through U21 pin 26. High = near 3.3V, Low = near 0V. -

I wonder if my problem with the attenuator is related to software. All 3 of my boards behave the same. They receive well, but the levels never change when I adjust the receive attenuator. Maybe I have

*** Yeah, the military is a different world. LOADs of paperwork before you write a single line of code. Time card audits... WRT airplanes - according to the guy at the local FSDO ( FAA shop ), I was