开云体育

I purchased a number of 680 nF 1206 inductors for L5 and L7 to address the uBitx spurs for version 4 pcb (the fix also requires correct relays not included). I have lots of spares of the Inductors. If you would like a few (3) send me a SASE (self addressed and stamped envelope) and a quarter to: Pete Meier 140 Cave. Ave. Manitou Springs, CO 80829 Please do not expect me to reply and confirm all your emails. Just send the envelopes, I will send them out as I receive them. I likely have enough for the group for some time. For reference today's date is 03/19/2019 When I get close to running out I will notify the group so no one loses a stamp and quarter. :-) Pete WK8S

Was able to compile JackAl 0.95. Installed Arduino 1.8.9 to it's own directory (did not use installer, downloaded ZIP) Installed Teensyduino 1.4.6 beta 10 (available on their forums) Removed RA8875 from Teensy library folder, replaced with RA8875 from Ham Radio Designs Added appropriate libraries per installation instructions (OpenAudio, Rotary, UTouch/Buttons, etc) Compiled successfully for Teensy 3.6 I don't have the JackAl board built yet, moving into new home so no workbench yet) Dave - AI6K

Uggg.. Still no headway. Guess I'm not understanding where to put AL's 7 inch values.. maybe I'll try a bit more tomorrow. bummed Vince n2aie

1. what software goes in the teensy. 2. is there a drawing that shows voltages to check when starting up? thanks dave k7da

The problem is that the code goes out and checks the first byte of EEPROM (EEPROMNew.cpp): void ReadUserSettings() { int val; EEPROM.get(0, val); // Read first byte of EEPROM memory //val = 0; // Uncomment this line forces a rewrite of EEPROM. Comment out line 23 to display // is not changed. Serial.print("Val = "); Serial.println(val); if (val != EEPROMINITVALUE) { // Already set or not? GlobalDefaultEEPROMValues(); // No, so set some common values WriteEEPROMSettings(EEPROMDEFAULTOFFSET); // Write default values to default block WriteEEPROMSettings(EEPROMUSEROFFSET); // Also assume defaults for user first time through If that first byte (e.g., EEPROM address 0) read into val is not equal to EEPROMINITVALUE, the program automatically goes into the initialization routines. Raw EEPROM on a new Teensy is initialized to 0xFF, which is not what EEPROMINITVALUE. This will cause the code to write default values into EEPROM. No doubt, that's what happened to your system. Exactly what is the problem after you init the screen? Is it that the buttons don't respond to presses at all, or that the presses are way off target? I did find some early tests we did with the 7" display (it died!) and the values we were using were: #ifdef AL7 // ------------------------ Al's 7" Calibration ------------ 8-14-18 calty = map(yFinal, 838, 174, 50, 430); // Al range = map(int(calty), 0, 479, 1, 4); switch (range) { case 1: caltx = map(xFinal, 684, 321, 50, 750); // Map from ADC values to Screen // Al break; case 2: caltx = map(xFinal, 684, 321, 50, 750); // Map from ADC values to Screen // Al break; case 3: caltx = map(xFinal, 684, 321, 50, 750); // Map from ADC values to Screen // Al break; case 4: caltx = map(xFinal, 684, 321, 50, 750); // Map from ADC values to Screen // Al break; } #endif which is near line 158 in the DisplayCalibration.cpp file. You'll notice this code was only toggled in when we were testing Al's 7" display (e.g., #define AL7) much like I explained with the DEBUG symbolic constant. I don't know if this will help, as we don't have a working 7" display right now. It might be a starting point... Jack, W8TEE Jack, maybe I didn't ask the correct question. I missed the initial cal routine at first powerup...probably because i didn't have the display installed?? anyway. to get to run the cal routine, i should set VAL = 0 ?? then what is the next step?? Vince n2aie

No. Look at line #4 in the JackAl.h header file: #define DEBUG // Comment out when not debugging If you want to debug stuff, leave as it is above. When you're done debugging, change it to: // #define DEBUG // Comment out when not debugging Placing the two comment lines at the front removes the DEBUG symbolic constant from the program once you recompile the code. So what? Look at line 927 at the top of setup(): #ifdef DEBUG Serial.begin(115200); #endif and line 955: #ifdef DEBUG ShowEEPROMValues(); #endif Now think about what these say: If the symbolic constant named DEBUG is defined in the program (in the JackAl.h header file), the code at line 927 in setup() says to instantiate the Serial monitor, which is your primary tool for debugging a program in the Arduino IDE. About thirty lines later, if you're in the DEBUG mode, you will see the ShowEEPROMValues() call displays all of the data that is stored in EEPROM. There are a number of other "hidden" debug calls throughout the program. Likewise, if DEBUG is NOT defined, no Serial object is instantiated and all of the debug function calls are NOT compiled into the program. This technique is called "scaffolding". It allows you to keep debugging stuff in the program, but without bloating the code when you're not debugging. Jack, W8TEE On Friday, March 15, 2019, 4:47:56 PM EDT, James Zdunic <james_zdunic@...> wrote: Jack, Sorry Arduino newby here... When you say debug mode do you mean running the IDE while the CPU is connected to the PC? And if so is it the serial monitor where you would see these values reported, or is there a separate debug function...? Jim KM4TXR On Mar 15, 2019, at 4:37 PM, jjpurdum via Groups.Io <jjpurdum@...> wrote: How many data points (trips around the display) do you make? If you're in the DEBUG mode, you should see the EEPROM values that are read back when the program starts. The call is around line 955 in setup(). Are you seeing reasonable values for all of the values shown there, including the display offsets. Jack, W8TEE On Friday, March 15, 2019, 4:00:28 PM EDT, Rick Price <rickprice48@...> wrote: Jack, I have the same problems on a 5" screen. Very sluggish at times to over responsive at others. I have calibrated using the setup option numerous times always the same results. Frequency digit selection arrow buttons are only responsive at the left hand edge and sometimes will cause the cursor to jump 2 or 3 places. Moving right is always harder then trying to move the cursor left. When I do the selection the audio changes to a quieter tone for the time I am pushing on the button. I did calibrate one time using an imaginary point to the right of the calibration points on the left hand side of the screen(1st two points) and that did seem to help center the action better. Band selection is especially troublesome when I select 20. 9 out of 10 times it will change to 15 and then I have to reselect 20. I am using a fiber stylus spudger tool to do the selections and have tried the end retracted end of a ball point pen and a nylon tuning wand with the same results. Just more info FWIW. Rick KN4AIE From: [email protected] [mailto:[email protected]] On Behalf Of James Zdunic Sent: Friday, March 15, 2019 2:12 PM To: [email protected] Subject: Re: [JackAl] 7" Display Drawing I’m running version 95 and did go through the setup/calibration routine contained in that version. Jim KM4TXR On Mar 15, 2019, at 2:10 PM, jjpurdum via Groups.Io <jjpurdum@...> wrote: Have you run the new software calibration routine? Jack, W8TEE On ?Friday?, ?March? ?15?, ?2019? ?02?:?05?:?52? ?PM? ?EDT, James Zdunic <james_zdunic@...> wrote: Hello Vince, I’d be curious to how the touch response performance is on your 7” display after doing the calibration? Reason being my 7” screen touch response is inaccurate with adjacent buttons as well as distant buttons being activated at random times. Also having issues with the touch response stopping completely requiring a reboot of the system to make it respond again. I’m trying to determine if my screen has issues or if it could be something else

the test document says to check voltage in the agc section. where are the voltages listed? dave k7da

All: Al and I have spent considerable time testing a couple of V5 ?BITX boards for use with our JackAl board. (See hamradiodesigns.com) No hardware modifications are required. We did have to make some minor changes in the software because of the new IF frequency. We expect to release a new software release for the V5 board in a few days. I will send out a notice when it is ready for download. We are also expanding the assembly manual with additional photos and narrative. That should be ready next week. The JackAl boards are being sold by QRPGuys.com. Jack, W8TEE

I am getting ready to build the dummy load. I have a 250W Dummy load I am going to use. What changes would need to be made to the software to increase power measured to 250W? I assume the voltage divider circuit would need to have values adjusted as well to keep max voltage at 5V for the Arduino input. Mike AI4NS

Of the recommended mods to the stock uBitx, which are still recommended when using the JackAl board? I'll be changing L5 & L7 and probably the relays too. John W1JDS

Hi, Did everybody connect through the single pin marked VUSB from the Jackal board to the Teensy? Keith M6OLP