开云体育

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

It appears that some of Jerry’s nearly daily posts relate to self inflicted issues. I think he is a veteran and talented bit banger so his posts always lead this old (nearly 83) system engineer to

You're right. Tell you what: I work on being less defensive if you are more thoughtful in your word selection when criticizing the T41 Project. The T41 is not my project. It is the distillation of the

Not the project, just the tuning. It works great once you get where you're going. It's quite an achievement, Jack. You deserve kudos for bringing it to us. Don't be so defensive. - Jerry, KF6VB

Working toward minimal audio disruption from display changes will make the tuning useable - but still not nice Why would I not get that impression? To imply something is "unusable" clearly implies

*** Jack, I am not asking you to work on it. I am working on it right now. What on earth gave you the impression that I was asking YOU to work on it? - Jerry, KF6VB

It already has a WIFI block onboard and an minipci bus too. Amazing little board. The documentation says Verilog is the right tool for programming. Dr. William J. Schmidt - K9HZ J68HZ 8P6HK ZF2HZ

Thanks for the update. Yep. I’m very familiar with the Radioberry. I have a couple of them and they work flawlessly. Using the Radioberry and the Hermes projects as examples, I’m convinced that

See below:Jack, W8TEE

That would be awesome.? I have not built yet and that is those were my biggest worries!

Dr. Bill, In yeterday's Mouser delivery, there were a couple MKR VIDOR 4000 Assemblies ( https://docs.arduino.cc/resources/pinouts/ABX00022-full-pinout.pdf ). I will have to look at the Arduino

*** Yet it is very disruptive to the audio. Why is that? I think it's because interrupts are disabled during SPI transfers. Tracking what has changed and what hasn't changed would likely ***