That you have?control_tlv320aic3206 in both OpenAudio_ArduinoLibrary and Audio libs.
Jack made a custom OpenAudio_ArduinoLibrary stripping out control_tlv320aic3206 (.cpp and .h) to avoid this and has posted it on //
Replace OpenAudio_ArduinoLibrary with the one from hamradiodesigns. this should fix your problem.
I was pulling hair out last Sunday night on the same thing, until I came to a conclusion that Jack was probably working with an older version of the Teesyduino than he 'told' us to use.
"told" meaning that the link given in the documents:??had most likely been updated since he last checked, and we weren't all singing from the same page in the songbook.
I stripped out the collision (the same way) and had a successful compile Monday morning.
-Gary
|
hello all.
what is the compiler trying to say?
Arduino: 1.8.8 (Windows 10), TD: 1.45, Board: "Teensy 3.6, Serial, 180 MHz, Faster, US English"
C:\JackaLSourceCode\JackAl_Ver0.91a\JackAl_Ver0.91a.ino: In function 'int SetFilterCenterFrequency(int, int, int)':
C:\JackaLSourceCode\JackAl_Ver0.91a\JackAl_Ver0.91a.ino:622:19: warning: variable 'delta' set but not used [-Wunused-but-set-variable]
?? int coordinate, delta, increment, target;
?????????????????? ^
Equalizer.cpp: In function 'void SetEqualizerBands()':
Equalizer.cpp:220: warning: 'position' may be used uninitialized in this function
???? rxEqualizer[j] = position;
????????????????????????????? ^
C:\arduino1.8.8\hardware\teensy\avr\libraries\UTFT\UTFT.cpp:78:48: note: #pragma message: Compiling for Teensy 3.X...
?? #pragma message("Compiling for Teensy 3.X...")
??????????????????????????????????????????????? ^
In file included from C:\arduino1.8.8\hardware\teensy\avr\libraries\UTFT\UTFT.cpp:79:0:
C:\arduino1.8.8\hardware\teensy\avr\libraries\UTFT\hardware/arm/HW_Teensy3.h:104:66: note: #pragma message: Using Ports B&D - pins should be connected to:
? #pragma message("Using Ports B&D - pins should be connected to:")
^
C:\arduino1.8.8\hardware\teensy\avr\libraries\UTFT\hardware/arm/HW_Teensy3.h:106:89: note: #pragma message: DB_0=16, DB_1=17, DB_2=19, DB_3=18, DB_4=0, DB_5=1, DB_6=29, DB_7=30
? #pragma message ("DB_0=16, DB_1=17, DB_2=19, DB_3=18, DB_4=0, DB_5=1, DB_6=29, DB_7=30")
^
C:\arduino1.8.8\hardware\teensy\avr\libraries\UTFT\hardware/arm/HW_Teensy3.h:110:92: note: #pragma message: DB_8=2, DB_9=14, DB_10=7, DB_11=8, DB_12=6, DB_13=20, DB_14=21, DB_15=5
? #pragma message ("DB_8=2, DB_9=14, DB_10=7, DB_11=8, DB_12=6, DB_13=20, DB_14=21, DB_15=5")
^
C:\arduino1.8.8\hardware\teensy\avr\libraries\UTFT\hardware/arm/HW_Teensy3.h:111:91: note: #pragma message: If using a display with an 8-bit bus, use connections to DB_8 to DB_15
? #pragma message ("If using a display with an 8-bit bus, use connections to DB_8 to DB_15")
^
C:\arduino1.8.8\hardware\teensy\avr\libraries\UTFT_Buttons\UTFT_Buttons.cpp: In member function 'void UTFT_Buttons::deleteAllButtons()':
C:\arduino1.8.8\hardware\teensy\avr\libraries\UTFT_Buttons\UTFT_Buttons.cpp:199:19: warning: ISO C++ forbids converting a string constant to 'char*' [-Wwrite-strings]
?? buttons[i].label="";
?????????????????? ^
C:\Users\dave\AppData\Local\Temp\arduino_build_998213\libraries\Audio\control_tlv320aic3206.cpp.o: In function `AudioControlTLV320AIC3206::disable()':
C:\arduino1.8.8\hardware\teensy\avr\libraries\Audio/control_tlv320aic3206.cpp:170: multiple definition of `AudioControlTLV320AIC3206::disable()'
C:\Users\dave\AppData\Local\Temp\arduino_build_998213\libraries\OpenAudio_ArduinoLibrary\control_tlv320aic3206.cpp.o:C:\arduino1.8.8\hardware\teensy\avr\libraries\OpenAudio_ArduinoLibrary/control_tlv320aic3206.cpp:168: first defined here
c:/arduino1.8.8/hardware/tools/arm/bin/../lib/gcc/arm-none-eabi/5.4.1/../../../../arm-none-eabi/bin/ld.exe: Disabling relaxation: it will not work with multiple definitions
C:\Users\dave\AppData\Local\Temp\arduino_build_998213\libraries\Audio\control_tlv320aic3206.cpp.o: In function `AudioControlTLV320AIC3206::disable()':
C:\arduino1.8.8\hardware\teensy\avr\libraries\Audio/control_tlv320aic3206.cpp:170: multiple definition of `AudioControlTLV320AIC3206::inputLevel(float)'
C:\Users\dave\AppData\Local\Temp\arduino_build_998213\libraries\OpenAudio_ArduinoLibrary\control_tlv320aic3206.cpp.o:C:\arduino1.8.8\hardware\teensy\avr\libraries\OpenAudio_ArduinoLibrary/control_tlv320aic3206.cpp:168: first defined here
C:\Users\dave\AppData\Local\Temp\arduino_build_998213\libraries\Audio\control_tlv320aic3206.cpp.o: In function `AudioControlTLV320AIC3206::disable()':
C:\arduino1.8.8\hardware\teensy\avr\libraries\Audio/control_tlv320aic3206.cpp:170: multiple definition of `AudioControlTLV320AIC3206::aic_goToPage(unsigned char)'
C:\Users\dave\AppData\Local\Temp\arduino_build_998213\libraries\OpenAudio_ArduinoLibrary\control_tlv320aic3206.cpp.o:C:\arduino1.8.8\hardware\teensy\avr\libraries\OpenAudio_ArduinoLibrary/control_tlv320aic3206.cpp:168: first defined here
C:\Users\dave\AppData\Local\Temp\arduino_build_998213\libraries\Audio\control_tlv320aic3206.cpp.o: In function `AudioControlTLV320AIC3206::disable()':
C:\arduino1.8.8\hardware\teensy\avr\libraries\Audio/control_tlv320aic3206.cpp:170: multiple definition of `AudioControlTLV320AIC3206::aic_writePage(unsigned char, unsigned char, unsigned char)'
C:\Users\dave\AppData\Local\Temp\arduino_build_998213\libraries\OpenAudio_ArduinoLibrary\control_tlv320aic3206.cpp.o:C:\arduino1.8.8\hardware\teensy\avr\libraries\OpenAudio_ArduinoLibrary/control_tlv320aic3206.cpp:168: first defined here
C:\Users\dave\AppData\Local\Temp\arduino_build_998213\libraries\Audio\control_tlv320aic3206.cpp.o: In function `AudioControlTLV320AIC3206::disable()':
C:\arduino1.8.8\hardware\teensy\avr\libraries\Audio/control_tlv320aic3206.cpp:170: multiple definition of `AudioControlTLV320AIC3206::aic_reset()'
C:\Users\dave\AppData\Local\Temp\arduino_build_998213\libraries\OpenAudio_ArduinoLibrary\control_tlv320aic3206.cpp.o:C:\arduino1.8.8\hardware\teensy\avr\libraries\OpenAudio_ArduinoLibrary/control_tlv320aic3206.cpp:168: first defined here
C:\Users\dave\AppData\Local\Temp\arduino_build_998213\libraries\Audio\control_tlv320aic3206.cpp.o: In function `AudioControlTLV320AIC3206::disable()':
C:\arduino1.8.8\hardware\teensy\avr\libraries\Audio/control_tlv320aic3206.cpp:170: multiple definition of `AudioControlTLV320AIC3206::aic_init()'
C:\Users\dave\AppData\Local\Temp\arduino_build_998213\libraries\OpenAudio_ArduinoLibrary\control_tlv320aic3206.cpp.o:C:\arduino1.8.8\hardware\teensy\avr\libraries\OpenAudio_ArduinoLibrary/control_tlv320aic3206.cpp:168: first defined here
C:\Users\dave\AppData\Local\Temp\arduino_build_998213\libraries\Audio\control_tlv320aic3206.cpp.o: In function `AudioControlTLV320AIC3206::disable()':
C:\arduino1.8.8\hardware\teensy\avr\libraries\Audio/control_tlv320aic3206.cpp:170: multiple definition of `AudioControlTLV320AIC3206::aic_writeAddress(unsigned short, unsigned char)'
C:\Users\dave\AppData\Local\Temp\arduino_build_998213\libraries\OpenAudio_ArduinoLibrary\control_tlv320aic3206.cpp.o:C:\arduino1.8.8\hardware\teensy\avr\libraries\OpenAudio_ArduinoLibrary/control_tlv320aic3206.cpp:168: first defined here
C:\Users\dave\AppData\Local\Temp\arduino_build_998213\libraries\Audio\control_tlv320aic3206.cpp.o: In function `AudioControlTLV320AIC3206::disable()':
C:\arduino1.8.8\hardware\teensy\avr\libraries\Audio/control_tlv320aic3206.cpp:170: multiple definition of `AudioControlTLV320AIC3206::setMicBias(int)'
C:\Users\dave\AppData\Local\Temp\arduino_build_998213\libraries\OpenAudio_ArduinoLibrary\control_tlv320aic3206.cpp.o:C:\arduino1.8.8\hardware\teensy\avr\libraries\OpenAudio_ArduinoLibrary/control_tlv320aic3206.cpp:168: first defined here
C:\Users\dave\AppData\Local\Temp\arduino_build_998213\libraries\Audio\control_tlv320aic3206.cpp.o: In function `AudioControlTLV320AIC3206::disable()':
C:\arduino1.8.8\hardware\teensy\avr\libraries\Audio/control_tlv320aic3206.cpp:170: multiple definition of `AudioControlTLV320AIC3206::inputSelect(int)'
C:\Users\dave\AppData\Local\Temp\arduino_build_998213\libraries\OpenAudio_ArduinoLibrary\control_tlv320aic3206.cpp.o:C:\arduino1.8.8\hardware\teensy\avr\libraries\OpenAudio_ArduinoLibrary/control_tlv320aic3206.cpp:168: first defined here
C:\Users\dave\AppData\Local\Temp\arduino_build_998213\libraries\Audio\control_tlv320aic3206.cpp.o: In function `AudioControlTLV320AIC3206::disable()':
C:\arduino1.8.8\hardware\teensy\avr\libraries\Audio/control_tlv320aic3206.cpp:170: multiple definition of `AudioControlTLV320AIC3206::aic_initADC()'
C:\Users\dave\AppData\Local\Temp\arduino_build_998213\libraries\OpenAudio_ArduinoLibrary\control_tlv320aic3206.cpp.o:C:\arduino1.8.8\hardware\teensy\avr\libraries\OpenAudio_ArduinoLibrary/control_tlv320aic3206.cpp:168: first defined here
C:\Users\dave\AppData\Local\Temp\arduino_build_998213\libraries\Audio\control_tlv320aic3206.cpp.o: In function `AudioControlTLV320AIC3206::disable()':
C:\arduino1.8.8\hardware\teensy\avr\libraries\Audio/control_tlv320aic3206.cpp:170: multiple definition of `AudioControlTLV320AIC3206::setInputGain_dB(float)'
C:\Users\dave\AppData\Local\Temp\arduino_build_998213\libraries\OpenAudio_ArduinoLibrary\control_tlv320aic3206.cpp.o:C:\arduino1.8.8\hardware\teensy\avr\libraries\OpenAudio_ArduinoLibrary/control_tlv320aic3206.cpp:168: first defined here
C:\Users\dave\AppData\Local\Temp\arduino_build_998213\libraries\Audio\control_tlv320aic3206.cpp.o: In function `AudioControlTLV320AIC3206::disable()':
C:\arduino1.8.8\hardware\teensy\avr\libraries\Audio/control_tlv320aic3206.cpp:170: multiple definition of `AudioControlTLV320AIC3206::volume_dB(float)'
C:\Users\dave\AppData\Local\Temp\arduino_build_998213\libraries\OpenAudio_ArduinoLibrary\control_tlv320aic3206.cpp.o:C:\arduino1.8.8\hardware\teensy\avr\libraries\OpenAudio_ArduinoLibrary/control_tlv320aic3206.cpp:168: first defined here
C:\Users\dave\AppData\Local\Temp\arduino_build_998213\libraries\Audio\control_tlv320aic3206.cpp.o: In function `AudioControlTLV320AIC3206::disable()':
C:\arduino1.8.8\hardware\teensy\avr\libraries\Audio/control_tlv320aic3206.cpp:170: multiple definition of `AudioControlTLV320AIC3206::volume(float)'
C:\Users\dave\AppData\Local\Temp\arduino_build_998213\libraries\OpenAudio_ArduinoLibrary\control_tlv320aic3206.cpp.o:C:\arduino1.8.8\hardware\teensy\avr\libraries\OpenAudio_ArduinoLibrary/control_tlv320aic3206.cpp:168: first defined here
C:\Users\dave\AppData\Local\Temp\arduino_build_998213\libraries\Audio\control_tlv320aic3206.cpp.o: In function `AudioControlTLV320AIC3206::disable()':
C:\arduino1.8.8\hardware\teensy\avr\libraries\Audio/control_tlv320aic3206.cpp:170: multiple definition of `AudioControlTLV320AIC3206::aic_initDAC()'
C:\Users\dave\AppData\Local\Temp\arduino_build_998213\libraries\OpenAudio_ArduinoLibrary\control_tlv320aic3206.cpp.o:C:\arduino1.8.8\hardware\teensy\avr\libraries\OpenAudio_ArduinoLibrary/control_tlv320aic3206.cpp:168: first defined here
C:\Users\dave\AppData\Local\Temp\arduino_build_998213\libraries\Audio\control_tlv320aic3206.cpp.o: In function `AudioControlTLV320AIC3206::disable()':
C:\arduino1.8.8\hardware\teensy\avr\libraries\Audio/control_tlv320aic3206.cpp:170: multiple definition of `AudioControlTLV320AIC3206::aic_readPage(unsigned char, unsigned char)'
C:\Users\dave\AppData\Local\Temp\arduino_build_998213\libraries\OpenAudio_ArduinoLibrary\control_tlv320aic3206.cpp.o:C:\arduino1.8.8\hardware\teensy\avr\libraries\OpenAudio_ArduinoLibrary/control_tlv320aic3206.cpp:168: first defined here
C:\Users\dave\AppData\Local\Temp\arduino_build_998213\libraries\Audio\control_tlv320aic3206.cpp.o: In function `AudioControlTLV320AIC3206::disable()':
C:\arduino1.8.8\hardware\teensy\avr\libraries\Audio/control_tlv320aic3206.cpp:170: multiple definition of `AudioControlTLV320AIC3206::enable()'
C:\Users\dave\AppData\Local\Temp\arduino_build_998213\libraries\OpenAudio_ArduinoLibrary\control_tlv320aic3206.cpp.o:C:\arduino1.8.8\hardware\teensy\avr\libraries\OpenAudio_ArduinoLibrary/control_tlv320aic3206.cpp:168: first defined here
C:\Users\dave\AppData\Local\Temp\arduino_build_998213\libraries\Audio\control_tlv320aic3206.cpp.o: In function `AudioControlTLV320AIC3206::disable()':
C:\arduino1.8.8\hardware\teensy\avr\libraries\Audio/control_tlv320aic3206.cpp:170: multiple definition of `vtable for AudioControlTLV320AIC3206'
C:\Users\dave\AppData\Local\Temp\arduino_build_998213\libraries\OpenAudio_ArduinoLibrary\control_tlv320aic3206.cpp.o:C:\arduino1.8.8\hardware\teensy\avr\libraries\OpenAudio_ArduinoLibrary/control_tlv320aic3206.cpp:168: first defined here
collect2.exe: error: ld returned 1 exit status
Multiple libraries were found for "SD.h"
?Used: C:\arduino1.8.8\hardware\teensy\avr\libraries\SD
?Not used: C:\arduino1.8.8\libraries\SD
Error compiling for board Teensy 3.6.
This report would have more information with
"Show verbose output during compilation"
option enabled in File -> Preferences.
|
Re: New Document File: Installing the IDE
Jim, Most likely you still had?sketchbook.path (sketchbook location in the preferences) pointing to "c:/users/admininstrator/my documents/arduino" (where windows wants it) and not to?C:\JackAlCode (where Jack has requested it) If you have a "libraries" folder in your sketchbook folder and a library in there that matches the #include<file> it will be the one chosen. Top priority over the core folder or IDE installation folder. Comment: The IDE is setup this way so users can add libraries / copy and modify a local copy of the library that is specific to that sketchbook. You can have a sketchbook "JackAl" with additional and/or customized libs, and you can have another Sketchbook with different libraries and still use the same IDE installation without potential conflict do to a modified lib.? The IDE has been updated over time to handle the situation we have here. Custom libs for a sketchbook.? For numerous reasons, promoting a customized library to the core or IDE installation folder is not what I would choose to do.? However this way is NOT how Jack instructed you to do it. For this project, I still recommend following Jack's instructions; especially if you are in need of assistance.? Hence the suggestions from Jan 25. Fact check the library guide:? Note about:
Using Sketch -> Include Library -> Add Zip Library ¡ in the Arduino IDE.
This tool is not smart.? Library directory names have to follow rules.? Evidently those rules were not considered when this tool was added.? If it were a reasonable tool, it would know the rules, flag a lib directory name that was not compliant, make a suggestion and let the user choose the proper name upon import. You can use the tool to effectively unzip the folder and place it in the sketchbook library, but you still have to go to the library and fix the name manually if the name is not compliant.?? Might as well just put it there manually to begin with, IMO.? The user still needs to be aware of the naming rules, the tool does not help. Seems this functionality would have been added a long time ago, with so many users using libs from GitHub.?Not a hair puller, just a disappointment that the tool is lacking.
Rgds,
Gary
|
Using library UTFT_Buttons in folder: D:\Ardunio 1.8.8\Arduino\hardware\teensy\avr\libraries\UTFT_Buttons (legacy)
Error compiling for board Teensy 3.6.
This library is directly from the Teensy site, so don't understand what is going on. Also, The TimerLib.h file is missing
from the library, where do I find that one?
Bob -wb6kwt
|
Re: Touch Display...was Built but not yet working
Get directly from PJRC:
Dave - AI6K
|
Re: Touch Display...was Built but not yet working
We actually bring the USB cable out to the back panel using a panel-mount USB extender cable:
 This allows us to modify the code without having to open the case.
Jack, W8TEE
On Sunday, January 27, 2019, 9:50:45 AM EST, Rick Price <rickprice48@...> wrote:
Had the same problem but these 90 deg adapters from
Amazon?took care of it. If you have room you can also raise the 5V
regulator a little and bend it down towards the board.
?
Rick KN4AIE
?
?
?
Thanks Jack, you did answer it. At the moment I must program my
Teensy on a breadboard then put it into the JackAl board because there isn¡¯t
room on the JackAl bd. to plug a USB. The heatsink interferes.?
The delay will be a viable workaround.?
Thanks,
On Jan 26, 2019, at 10:24 PM, jjpurdum via Groups.Io < jjpurdum@...>
wrote:
Pete:
Perhaps I don't understand the question. However, setup() calls
this code, which is at line 14 in 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.
??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
?
? 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
???
InitDisplayCalibration();??????????????????????????????
// Now have them calibrate display
? }
?
ReadEEPROMSettings(EEPROMUSEROFFSET);
}
The second lines causes a read of the first EEPROM byte and save
that value in val. If val is not equal to EEPROMINITVALUE, which
is 150, then the code sets a bunch of default values for variables. (If you
uncomment the line immediately below the EEPROM.get() call, it will
force the if statement block to execute.) The second statement in
the if block writes those default values to one segment of EEPROM
reserved for default values. I did this so you can always return to a default
set of values. (This is what the Restore button you see in the lower right of
the main program screen does when you press it.) Those same set of values are
then also written into the EEPROM segment set aside for your own custom
settings for those variables. As a result, EEPROM maintains a default set of
values and a separate set that is whatever you have made them.
The last function call in the if statement block (i.e.,
InitDisplayCalibration()) is the routine that allows you to calibrate
your display. If you place this statement:
MyDelay(10000UL);
immediately before
InitDisplayCalibration(), you will have 10
seconds to turn off your rig. (Note: there is a standard Delay()
function provided by the standard library, but it is a "blocking"
function. That is, it blocks any interrupts that might occur while processing
its delay. I wrote MyDelay() as a replacement because it does not block
interrupts. So, if you plan to do any code that needs a program delay, you
most likely will want to use MyDelay() instead of the stock
Delay().)
Anyway, I'm not sure I answered your question, but perhaps this
info will help you do what you need to do.
Jack, W8TEE
On Saturday, January 26, 2019, 6:42:18 PM EST, PeteWK8S via Groups.Io
< pmeier@...>
wrote:
Ok I've built my JackAl in such a way I cannot program the Teensy with it
in place. Not enough room to plug a cable in. So I have to program it out of
the JackAL board. I'm working out a workaround. However, in the meantime, how
do delay the Touch calibration routine so that is doesn't execute upon
completion of the load ? ?Insert a long enough DELAY so I have time to
turn off the Teensy before it the routine executes?
Pete WK8S
|
Re: Touch Display...was Built but not yet working
Had the same problem but these 90 deg adapters from
Amazon?took care of it. If you have room you can also raise the 5V
regulator a little and bend it down towards the board.
?
Rick KN4AIE
?
?
?
toggle quoted message
Show quoted text
Thanks Jack, you did answer it. At the moment I must program my
Teensy on a breadboard then put it into the JackAl board because there isn¡¯t
room on the JackAl bd. to plug a USB. The heatsink interferes.?
The delay will be a viable workaround.?
Thanks,
On Jan 26, 2019, at 10:24 PM, jjpurdum via Groups.Io < jjpurdum@...>
wrote:
Pete:
Perhaps I don't understand the question. However, setup() calls
this code, which is at line 14 in 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.
??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????
?
? 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
???
InitDisplayCalibration();??????????????????????????????
// Now have them calibrate display
? }
?
ReadEEPROMSettings(EEPROMUSEROFFSET);
}
The second lines causes a read of the first EEPROM byte and save
that value in val. If val is not equal to EEPROMINITVALUE, which
is 150, then the code sets a bunch of default values for variables. (If you
uncomment the line immediately below the EEPROM.get() call, it will
force the if statement block to execute.) The second statement in
the if block writes those default values to one segment of EEPROM
reserved for default values. I did this so you can always return to a default
set of values. (This is what the Restore button you see in the lower right of
the main program screen does when you press it.) Those same set of values are
then also written into the EEPROM segment set aside for your own custom
settings for those variables. As a result, EEPROM maintains a default set of
values and a separate set that is whatever you have made them.
The last function call in the if statement block (i.e.,
InitDisplayCalibration()) is the routine that allows you to calibrate
your display. If you place this statement:
MyDelay(10000UL);
immediately before
InitDisplayCalibration(), you will have 10
seconds to turn off your rig. (Note: there is a standard Delay()
function provided by the standard library, but it is a "blocking"
function. That is, it blocks any interrupts that might occur while processing
its delay. I wrote MyDelay() as a replacement because it does not block
interrupts. So, if you plan to do any code that needs a program delay, you
most likely will want to use MyDelay() instead of the stock
Delay().)
Anyway, I'm not sure I answered your question, but perhaps this
info will help you do what you need to do.
Jack, W8TEE
On Saturday, January 26, 2019, 6:42:18 PM EST, PeteWK8S via Groups.Io
< pmeier@...>
wrote:
Ok I've built my JackAl in such a way I cannot program the Teensy with it
in place. Not enough room to plug a cable in. So I have to program it out of
the JackAL board. I'm working out a workaround. However, in the meantime, how
do delay the Touch calibration routine so that is doesn't execute upon
completion of the load ? ?Insert a long enough DELAY so I have time to
turn off the Teensy before it the routine executes?
Pete WK8S
|
Re: Touch Display...was Built but not yet working
Thanks Jack, you did answer it. At the moment I must program my Teensy on a breadboard then put it into the JackAl board because there isn¡¯t room on the JackAl bd. to plug a USB. The heatsink interferes.? The delay will be a viable workaround.?
toggle quoted message
Show quoted text
On Jan 26, 2019, at 10:24 PM, jjpurdum via Groups.Io < jjpurdum@...> wrote:
Pete:
Perhaps I don't understand the question. However, setup() calls this code, which is at line 14 in 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.
?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? ?
? 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
??? InitDisplayCalibration();?????????????????????????????? // Now have them calibrate display
? }
? ReadEEPROMSettings(EEPROMUSEROFFSET);
}
The second lines causes a read of the first EEPROM byte and save that value in val. If val is not equal to EEPROMINITVALUE, which is 150, then the code sets a bunch of default values for variables. (If you uncomment the line immediately below the EEPROM.get() call, it will force the if statement block to execute.) The second statement in the if block writes those default values to one segment of EEPROM reserved for default values. I did this so you can always return to a default set of values. (This is what the Restore button you see in the lower right of the main program screen does when you press it.) Those same set of values are then also written into the EEPROM segment set aside for your own custom settings for those variables. As a result, EEPROM maintains a default set of values and a separate set that is whatever you have made them.
The last function call in the if statement block (i.e., InitDisplayCalibration()) is the routine that allows you to calibrate your display. If you place this statement:
MyDelay(10000UL);
immediately before InitDisplayCalibration(), you will have 10 seconds to turn off your rig. (Note: there is a standard Delay() function provided by the standard library, but it is a "blocking" function. That is, it blocks any interrupts that might occur while processing its delay. I wrote MyDelay() as a replacement because it does not block interrupts. So, if you plan to do any code that needs a program delay, you most likely will want to use MyDelay() instead of the stock Delay().)
Anyway, I'm not sure I answered your question, but perhaps this info will help you do what you need to do.
Jack, W8TEE
On Saturday, January 26, 2019, 6:42:18 PM EST, PeteWK8S via Groups.Io < pmeier@...> wrote:
Ok I've built my JackAl in such a way I cannot program the Teensy with it in place. Not enough room to plug a cable in. So I have to program it out of the JackAL board. I'm working out a workaround. However, in the meantime, how do delay the Touch calibration routine so that is doesn't execute upon completion of the load ? ?Insert a long enough DELAY so I have time to turn off the Teensy before it the routine executes?
Pete WK8S
|
Mornin' Dave:
1. The ones marked in Green are already installed in the Arduino libraries directory. The ones in Yellow go in the Teensy library directory (e.g., C:\Arduino1.8.8\hardware\Teensy\avr\libraries).
#include <Arduino.h>????????? // Standard with IDE
#include <EEPROM.h>?????????? // EEPROM distributed with Teensy libraries
#include <math.h>???????????? // Standard with IDE
#include <Wire.h>???????????? // Standard with IDE
#include <SPI.h>????????????? // Standard with IDE
#include <stdio.h>??????????? // Standard with IDE
#include <OpenAudio_ArduinoLibrary.h> // http://hamradiodesigns.com/index.php/content/
#include <Adafruit_GFX.h>???? // Now supplied with Teensy Library install
#include <Audio.h>??????????? // Now supplied with Teensy Library install
#include <RA8875.h>?????????? // http://hamradiodesigns.com/index.php/content/
#include <Rotary.h>?????????? // https://github.com/brianlow/Rotary
#include <SerialFlash.h>????? // Now supplied with Teensy Library install
#include <Time.h>???????????? // Now supplied with Teensy Library install
#include <TimeLib.h>????????? // Now supplied with Teensy Library install
#include <TimerOne.h>???????? // Now supplied with Teensy Library install
#include <UTFT.h>???????????? // Now supplied with Teensy Library install
#include <URTouch.h>????????? // http://www.rinkydinkelectronics.com/library.php?id=92
#include <UTFT_Buttons.h>???? // http://www.rinkydinkelectronics.com/library.php?id=61
2. When you tell the compiler that you are using the Teensy board via the menu option Tools --> Boards, it knows the path names to the necessary files.
3. I started to write the code for it, but got distracted. The function getTeensy3Time() around line 821 in the INO file shows the start. There is a button defined for it, too. The time appears where the S Meter is, but could be put at the bottom of the display if you're not working CW. You will need to add a 3.3V battery to power the RTC when the rig is shut down. Right now, that's pretty far down my to-do list.
Jack, W8TEE
On Sunday, January 27, 2019, 12:53:07 AM EST, k7da <k7da@...> wrote:
3 questions.
1. when installing the extra library parts.? where should they be
installed and how does one get them there?
2. how does the compiler know to look for the teensy stuff in the
hardware directory
3.? does the JackaL board support RTC.? if so where and how.
dave k7da
|
Dave, Here are my thoughts... 1.? I put them in C:\Arduino1.8.7\hardware\teensy\avr\libraries and now have it working after having some compile trouble.? See my other post with details...? /g/JackAl/topic/new_document_file_installing/29417438?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,294174382.? I would imagine installing the teensy add on software and selecting the teensy3.6 as the target board in the IDE has something to do with this. Jim KM4TXR
|
Re: New Document File: Installing the IDE
Hi Jack & others,
I did download & install the RA8875, Open Audio, and some other libraries.? However I missed the part about them needing to be in the Teensy library which is why they were out of place. Concerned about conflicts I decided to wipe out everything and re-install the IDE and Teensy add on.? Then I added any missing libraries listed in the instructions into the Teensy library folder.
After that the next compile took significantly longer to complete.? However I still had some complaints from the compiler.?
I noticed that some of the complaints were referencing library files stored in: c:/users/admininstrator/my documents/arduino. ? I believe this folder was from my first IDE & Teensy installation before doing the install into the c:/arduino1.8.7 folder as advised. ? So I deleted the c:/users/admininstrator/my documents/arduino folder, ran a compile, and the compile finished with no errors.
I figured I'd mention this in case anyone else had issues from previous IDE installs.
Jim KM4TXR
|
3 questions.
1. when installing the extra library parts.? where should they be installed and how does one get them there?
2. how does the compiler know to look for the teensy stuff in the hardware directory
3.? does the JackaL board support RTC.? if so where and how.
dave k7da
|
If I am not too late, please include me in on the parts kit.
Tom Clark, KT4TC
|
Re: Touch Display...was Built but not yet working
Pete:
Perhaps I don't understand the question. However, setup() calls this code, which is at line 14 in 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.
?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? ?
? 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
??? InitDisplayCalibration();?????????????????????????????? // Now have them calibrate display
? }
? ReadEEPROMSettings(EEPROMUSEROFFSET);
}
The second lines causes a read of the first EEPROM byte and save that value in val. If val is not equal to EEPROMINITVALUE, which is 150, then the code sets a bunch of default values for variables. (If you uncomment the line immediately below the EEPROM.get() call, it will force the if statement block to execute.) The second statement in the if block writes those default values to one segment of EEPROM reserved for default values. I did this so you can always return to a default set of values. (This is what the Restore button you see in the lower right of the main program screen does when you press it.) Those same set of values are then also written into the EEPROM segment set aside for your own custom settings for those variables. As a result, EEPROM maintains a default set of values and a separate set that is whatever you have made them.
The last function call in the if statement block (i.e., InitDisplayCalibration()) is the routine that allows you to calibrate your display. If you place this statement:
MyDelay(10000UL);
immediately before InitDisplayCalibration(), you will have 10 seconds to turn off your rig. (Note: there is a standard Delay() function provided by the standard library, but it is a "blocking" function. That is, it blocks any interrupts that might occur while processing its delay. I wrote MyDelay() as a replacement because it does not block interrupts. So, if you plan to do any code that needs a program delay, you most likely will want to use MyDelay() instead of the stock Delay().)
Anyway, I'm not sure I answered your question, but perhaps this info will help you do what you need to do.
Jack, W8TEE
On Saturday, January 26, 2019, 6:42:18 PM EST, PeteWK8S via Groups.Io <pmeier@...> wrote:
Ok I've built my JackAl in such a way I cannot program the Teensy with it in place. Not enough room to plug a cable in. So I have to program it out of the JackAL board. I'm working out a workaround. However, in the meantime, how do delay the Touch calibration routine so that is doesn't execute upon completion of the load ? ?Insert a long enough DELAY so I have time to turn off the Teensy before it the routine executes?
Pete WK8S
|
Re: Wiring hints... was Fw: [JackAl] Wiring error in Assembly Manual?
Ok now I see what Jack and Al did with J4 and J5 cables! They combined 4 GND wires into 2 pin holes from the J4 connector to uBitx header!
So that left pins 1 and 2 of the Ubitx Radino connectors empty (don't want to connect pin 2 12volts to JackAl J4!) Believe me I know :-(
So they use all 10 wires at J4 connector to make it crimp properly but effectively only connected 8 wires to the 10 pin header going to the uBitx board.?
This was not evident to my eyes in previous pics in the manual.?
Take-a-ways.... IDC connectors require all wires to be used either 10 or 6 (filling all the slots) and of the correct wire gauge, to allow a good crimp to occur. This also means sometimes you may be ?be required to solder (and heat shrink) larger wire gauges to the smaller wires that are required for IDC connectors.
I tried to use the pre-made Dupont wires, commonly used with breadboards, in the IDC connectors and found they are slightly too large a gauge to crimp properly. Hopefully you won't waste IDC connectors trying this as I did.
|
Touch Display...was Built but not yet working
Ok I've built my JackAl in such a way I cannot program the Teensy with it in place. Not enough room to plug a cable in. So I have to program it out of the JackAL board. I'm working out a workaround. However, in the meantime, how do delay the Touch calibration routine so that is doesn't execute upon completion of the load ? ?Insert a long enough DELAY so I have time to turn off the Teensy before it the routine executes?
Pete WK8S
|
New DOC files and Source Code
All:
We have updated the source code to upgrade the decoder, some pin states, and a few other minor changes. The versions is called Version 0.91a. Also, Al has added a closeup photo of the control/clock harness.
Jack, W8TEE
|
I used to solder 2 pins while holding with a fat finger and using old eyes, flip it over and check, reheat and move it a little, check again and repeat until perfect.? This works for me the first time perfectly? Sorry for sharing an idea that may help someone with the same skills as me. --
Lee - N9LO
"I Void Warranties"
|
Fw: [JackAl] Wiring error in Assembly Manual?
Just got this from Al. Everyone should check the site from time-to-time because we are updating DOC files and the source code when needed.
Jack, W8TEE
If you follow the photo all will be OK.? The photo shows the connector from the side where the male pins are inserted.? I believe the diagram is consistent. ? Hope this helps.? I will inset a closeup of the connected in a while. Al ? Sent from for Windows 10 ?
From: Jack PurdumSent: Saturday, January 26, 2019 9:42 AM To: Albert PeterSubject: Fw: [JackAl] Wiring error in Assembly Manual? ? Which is correct?? ----- Forwarded Message ----- From: Rick Price <rickprice48@...> Sent: Saturday, January 26, 2019, 9:32:51 AM EST Subject: Re: [JackAl] Wiring error in Assembly Manual? Jack and AL, Now I'm totally confused on the orientation of the 2X3 IDC plug.? I had been viewing the plug from the top down (wire insertion/contact side using the interlock? bump as a reference.? Diagram 2-18 says connector view from above with pin 1 on the interlock side outside comer.? Looking at new diagram new diagram 2-22 (1-20-2019?shows the interlock on the bottom with pin 1 on the opposite corner from diagram 2-18. Diagram says "view is toward the female connector opening" not sure what that means is that the wire insert side or the side where the pin from the male jack is inserted.? As the connector is unmarked I have been unable to tell which is really pin 1 for a reference and it appears from my view the diagrams don't agree with each other on what is pin 1.? Had this cable already built but do not want to change it until there is some clarification.? Thank you for both of your efforts in the JackAL.? ? Rick KN4AIE ? 
From: [email protected] [mailto:[email protected]] On Behalf Of jjpurdum via Groups.Io
Sent: Friday, January 25, 2019 3:30 PM
To: [email protected]
Subject: Re: [JackAl] Wiring error in Assembly Manual? Jack, I updated this once, but apparently it did not take.? I believe it is correct now.? Tell Pete we had some pilot error.? I should have checked. Al On Friday, January 25, 2019, 12:08:55 PM EST, PeteWK8S via Groups.Io <pmeier@...> wrote: On page 18 of Section 2 of the manual Figure 2-23 seems to be in conflict with the control connector J5 photo which shows straight through wiring.
When connector J5 is crimped as the photo shows pin 16 will connect to the lower pin in J5 and pin 15 to upper row and other pins are reversed also.
So in the drawing of J5 the upper row of pins should be the lower row according to my continuity meter using the connector orientation as shown.
|
Re: Wiring error in Assembly Manual?
Jack and AL,
Now I'm totally confused on the orientation of the 2X3 IDC
plug.? I had been viewing the plug from the top down (wire
insertion/contact side using the interlock? bump as a reference.?
Diagram 2-18 says connector view from above with pin 1 on the interlock side
outside comer.? Looking at new diagram new diagram 2-22
(1-20-2019?shows the interlock on the bottom with pin 1 on the opposite
corner from diagram 2-18. Diagram says "view is toward the female connector
opening" not sure what that means is that the wire insert side or the side where
the pin from the male jack is inserted.? As the connector is unmarked I
have been unable to tell which is really pin 1 for a reference and it appears
from my view the diagrams don't agree with each other on what is pin 1.?
Had this cable already built but do not want to change it until there is some
clarification.? Thank you for both of your efforts in the
JackAL.?
?
Rick
KN4AIE
toggle quoted message
Show quoted text
Pete:
I just got this from Al:
Jack,
I updated this once, but apparently
it did not take.? I believe it is correct now.? Tell Pete we had some
pilot error.? I should have checked.
Al
Jack, W8TEE
On Friday, January 25, 2019, 12:08:55 PM EST, PeteWK8S via Groups.Io
<pmeier@...> wrote:
On page 18 of Section 2 of the manual Figure
2-23 seems to be in conflict with the control connector J5 photo which shows
straight through wiring.
When connector J5 is crimped as the photo shows pin
16 will connect to the lower pin in J5 and pin 15 to upper row and other pins
are reversed also.
So in the drawing of J5 the upper row of pins should be
the lower row according to my continuity meter using the connector orientation
as shown.
|
jjpurdum
Lee