开云体育

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

Jack, Thanks for the response. 1.? Did removed the jumper between the pads so all is ok now with ability to pgm teensy in-situ with supply connected. 2.? I did expect that based on page 25 of the

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

If you plan on using the JackAl system with both USB power and the 3.3V supply, you should but the trace between the VUSB pads on the underside of the board: This will prevent a conflict between power

Temporary binding clip and fan works fine. Thanks closed Vince n2aie

scratch that...I am in debug...as i have the serial monitor active.. i'm assuming this is the new cal routine where you do top left and bottom right 5 times, and it comes up with the average.. where

Jim, I guess i am having issues trying to cal the 7 inch display.? I'm sure I'm not doing it correctly with v 0.95 I'll keep putzing..i am not seeing the values like you are seeing.(not in debug) i

getting warmer.. ok..so 1.? don't uncomment val = 0 (at least with is uncommented, i got all the default values (saved those for a later date if needed). 2.? uncommented InitDisplayCalibration().. i

sorry...Disregard comments about Pads... found the post... still need to get the cal routine running... vince n2aie

just looking at the code and the serial.print values, I'm assuming i should be monitoring the serial monitor to get the values and not on the display. so that requires the teensy to be connected to

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

I was reading my overnight emails, which I do from top to bottom, so I didn't see this before I wrote my last email to you. Actually, these values don't look too far out of what I would expect. Let Al

The expected calibration values for the display are "guessed" near the top of the DisplayCalibration.cpp file (line 55): float xMapLowRange1 = 671; float xMapLowRange2 = 689; float xMapLowRange3 =

Jack, The following are the initial debug values after boot up... Val = 150 displayWidth = 800 displayHeight = 480 defaultTextSize = 3 activeVFO = 1 currentFrequencyA = 14285000 currentFrequencyB =

Jack, I could only get around the screen 7 times before the point ignored became unrelenting and I can’t get past the point you see in the photo below... [image1.jpeg] Jim KM4TXR

Also record the values. Jack, W8TEE

that must be the 7" display as it is different then my 5" dave

Got it Jack thanks, I’m learning, which is the mission with this project. So to answer your previous questions... I have made up to four or five trips around the screen. Obviously haven’t checked

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