Jump to content

All Activity

This stream auto-updates     

  1. Yesterday
  2. Last week
  3. Hi luckyflyer, Just letting you know that i haven't received it yet even after waiting for almost a month....
  4. Earlier
  5. Thank you for the kind words. Your technical assistance was extremely helpful in identifying the LCD Keyboard problem, so it was a joint effort.
  6. Very quick and professional way to address that this issue can happen again. Can't get better than this! Very proud of your awesome work Mr. Thomas!
  7. I suppose that is the best we can do for now. Given the random nature of the Chinese boards I expect the LCD-Keyboard shield compatibility issue will pop up again. To be proactive about this I have released a new version of the firmware (V2.3). It is posted here: https://www.rc-cam.com/forum/index.php?/topic/4139-diy-rf-power-vswr-meter-low-cost/&do=findComment&comment=29002 There's now a keyboard debug function. It will display the key-press code value when each menu button is pressed. The feature is enabled via the config.h file using DEBUG_KYBD found under the Troubleshooting section. What does it do? For those that need help solving keyboard compatibility problems: Enable DEBUG_KYBD in config.h, re-flash the firmware and then report the five keypress code values shown on the LCD. When posting for help be sure to include the two A0 voltage values mentioned earlier. Also, the config.h file now supports an alternate LCD/Keyboard shield. Currently there's two choices, my DFRobot branded board (LCD_SHIELD_DFR) and the clone used by HF_ATL (LCD_SHIELD_ALT1). The shield choice is made by enabling LCD_SHIELD_DFR or LCD_SHIELD_ALT1 found under the LCD/Keyboard Shield Type section.
  8. I have purchased this item in ebay about 1 year ago. All I can see it says is: "LCD Keypad Shield, Drive the Future". The best would be for users to check what you said to me: "Ideally the A0 voltage with no button pressed will be 2.45V - 2.50V. With the Select button pressed you should see about 2.0V". I guess this is a good starting point to check for possible keypad issues. I still need a directional coupler (not yet purchased) as I'm always looking for a good used one for a good price. Calibration probably will be left as it is unfortunately as I don't have access to any equipment for verify the results.
  9. You are welcome. Thanks for letting me know the keypad is working now. I should add a note to the docs about the changes for your LCD/Keypad shield. Is there a Chinese manufacturer's name or unique ID printed on your DFRobot clone shield so it can be identified by other project builders? That's a sane/reasonable value with nothing connected to the SMA. It should be fine for VSWR only measurements. But a calibration will be required for accurate RF power measurements .
  10. It works as expected! Many thanks for all your support, really appreciated! I have already configured successfully the attn profile for my 30.3db attenuator. I get around -67dbm/-68dbm with nothing connected to the SMA input. Unfortunately I don't have here at the moment a 1.3GHz transmitter to test but I'll come back here and post my results for sure. Wonderful work Mr. Thomas and Mr. Joost!
  11. The 2K ohm (1.99K) resistor is a good A0 choice for your LCD shield. Now the various key press codes will need to be re-mapped. In the RF_Power_Meter.ino file, go to the ReadLCD_Buttons function (starts at line 435). Replace the adc_key_in code section (from lines 486 to 506) with this revised snippet: if (adc_key_in > 1000) { kybd = btnNONE; } else if (adc_key_in < 50) { kybd = btnRIGHT; } else if (adc_key_in < 265) { kybd = btnUP; } else if (adc_key_in < 525) { kybd = btnDOWN; } else if (adc_key_in < 690) { kybd = btnLEFT; } else if (adc_key_in < 865) { kybd = btnSELECT; } else { kybd = btnNONE; } Upload code then check all the button functions. Hopefully you are rewarded with button press happiness. EDIT: Beginning with firmware V2.3 this alternate key press code can be selected in the config.h file. Choose LCD_SHIELD_ALT1 to enable it.
  12. I guess now the values are acceptable enough? Thanks you!
  13. I measured: A0 voltage when no buttons are pressed: 2.47V A0 voltage when select button is pressed: 2.05V Measurements done with the 1.99KOhm resistor.
  14. With a 1.99 KOhm connected between A0 and gnd pin I measured: Select button pressed: 846 Left button pressed: 677 Right button pressed: 10 Up button pressed: 251 Down button pressed: 509 None button pressed: 1020 With the 1.99 KOhm resistor installed I now get 1.10 Kohm between A0 and gnd pin.
  15. The voltages and key press values are now a bit too low. Increase the resistor value a small amount (try ~1.8K). Ideally the A0 voltage with no button pressed will be 2.45V - 2.50V with a "None" key press value between 1015 and 1023. With the Select button pressed you should see about 2.0V. Get as close to these voltages as practical then report all the key press debug values. Important: Never power the meter without the A0 resistor installed.
  16. I measured: A0 voltage when no buttons are pressed: 2.11V A0 voltage when select button is pressed: 1.80V Measurements done with the 1.48KOhm resistor.
  17. With a 1.48 KOhm connected between A0 and gnd pin I measured: Select button pressed: 744 Left button pressed: 611 Right button pressed: 10 Up button pressed: 241 Down button pressed: 470 None button pressed: 871 With the 1.48 KOhm resistor installed I now get 0.93 Kohm between A0 and gnd pin.
  18. Almost there. Try a 1.5K and report the debug values. With the 1.5K installed, please measure the A0 voltage when no buttons are pressed and also when the select button is pressed.
  19. With a 2.2 kOhm connected between A0 and gnd pin I measured: Select button pressed: 884 Left button pressed: 697 Right button pressed: 10 Up button pressed: 252 Down button pressed: 520 None button pressed: 1023 With the 2.2 KOhm resistor installed I now get 1.16Kohm between A0 and gnd pin.
  20. Those values show we are on the right path. But the key press values are still a bit high. Replace the 2.7K ohm with a 2.2K and report all the key press debug values again.
  21. Thanks for your support Mr. RC-CAM! With a 2.7kOhm connected between A0 and gnd pin I measured: Select button pressed: 940 Left button pressed: 736 Right button pressed: 10 Up button pressed: 258 Down button pressed: 542 None button pressed: 1023 With the 2.7 KOhm resistor installed I now get 1.29Kohm between A0 and gnd pin.
  22. Thanks for checking the 3.3K resistor. Mine measures 1.82K ohms between A0 and GND (with 3.3K installed). So that means your LCD Keyboard Shield has different keypad summing resistors on it. The workaround will require changing your 3.3K A0 resistor value. Begin with a 2.7K ohms instead of the 3.3K. Then report back the button values using your "Serial.println(adc_key_in);" debugging code. This will allow me to confirm we're on the right path.
  23. I confirm that the resistor placed between A0 and gnd pin is correct. I have just measured 3.29kOhm with my multimeter (one terminal of the resistor disconnected to properly measure the resistor value). With the resistor connected I measured 1.41kOhm between A0 and gnd.
  24. Before we do any tinkering please verify A0's 3.3K ohm resistor value again. Your photo's colors might be deceiving me, but it appears that the A0 resistor's color code is ORG/ORG/BLK/VIO/VIO. That would be an incorrect value (3.3G ohms).
  25. I confirm that I have a 3.3KOhm resistor between A0 pin and ground. It is the same as the picture above. I attach a photo taken now from mine.
  26. All of your button values are too high. Confirm that you have installed the correct resistor value (3.3K) on pin A0 (see image below). BTW, does the artwork of your LCD Keypad board match the image below? If it is different in any way then the A0 resistor value may need to be altered.
  27. Dear Mr. Joost and Mr. RC-Cam, Many thanks for the quick reply and support! Voltage on A1 pin is 2.1V when no signal is connected. That problem is solved... Both of you nailed it exactly! Apparently it was due to a power supply issue. I just used another 12V source with bigger amp capacity (1A) and now that error message has gone. The LCD backlight must be consuming a lot. The voltage drop is around 0.8V from the supply voltage unconnected to VIN pin. However another issue occurred: The select button on the keypad doesn't work. I used the serial port to get the analogread of the A0 to view the values as I pressed all the keys. I noticed that the values used on the code don't suit my situation. I used this line of code: "Serial.println(adc_key_in);" to get those values on Serial monitor. Even changing the values for the new ones the select button doesn't work. The values I get are: Select button pressed: 1012 Left button pressed: 774 Right button pressed: 10 Up button pressed: 263 Down button pressed: 561 None button pressed: 1023 Best regards, JF
  28. If JoostB's advice does not get you going then we'll need to know a few things. For example: 1. What exactly are you using to power the meter? 2. What is the measured voltage on the Arduino's VIN pin? This is the pin that supplies power to the AD8313 board. 3. Do the five keypad buttons work correctly? Keep in mind that the meter will give you that warning if you try to use it while powered by the USB port. That is to say, an external power source must be connected to the DC Input (barrel plug jack) on the Arduino board. I recommend using 12VDC (3S LiPO battery).
  1. Load more activity
×