ATU100 intermittently switching to auto on TX
#atu-100
Hi all -
My ATU100 is working great - I think it will tune a rusty nail - I was able to tune my 80 meter off center fed dipole on 160 - something I was unable to do with my other name brand tuner!? And then I made my first ever top-band contacts - whoo hoo!
One issue though is the tuner will very occasionally switch in to auto mode on Tx - without pressing the button.? I have caps to ground on the Auto and Bypass buttons.? ?The enclosure is one of the 3D printed plastic ones.? Is some shielding needed or recommended?? Anything else to look for?
73.
Dean
KK4DAS
|
Re: Programming & compiling from github source code
Hi Antti,
? Thanks for the links they will be helpful.? Changing to another processor is a much bigger step than simply changing compilers, but there is no reason it cannot be done.
? ?What we need to be cautious about is to ensure that any changes we make, are made in a way that when David F (the original author) adds any new features, they can be carried over with not much work.??
? ?So I think it breaks down into a few steps.? ?First, we make changes to make the code compiler independent.? Doing this, often means that separating compiler-specific and? processor-specific code out from the core algorithms.? That way the 'smarts' of the algorithms become totally reusable, and the unique parts have to be customized for the CPU/HW/compiler, with the goal of keeping the unique parts as small as possible.
? ?We do need to decide whether to break up the files into smaller chunks.?
? ?Right now I'm torn between trying to minimize the changes in the code, to minimize the disruption (and therefore keep it closer to the original, for support reasons), and reorganizing things heading to the end result looking completely different.? I'm leaning more towards the former as I don't want to end up supporting this permanently.
Dave
?
|
Re: Programming & compiling from github source code
Hi Dave?& all,
?
2) Maybe a macro definition?would be good for the?asm instructions. Or if that is the only asm instruction it would be good to define an inline?function for that. And that could be defined differently for various compilers and processor families.?
?
6) This might help a bit. Button library function is documented here:?
?
I hope that helps. I'm interested in this porting job also and I would like to port the code to ATMEGA328 and STM32 family processors also. I have no experience in PIC's though.
Actually also the softI2C is documented here:?http://download.mikroe.com/documents/compilers/mikroc/pic/mikroc-pic-manual-v101.pdf
?
Antti
Hi Onno,
? ?Sounds like a good plan.??
? ?I've been looking into compiling this under the MPLAB, and found a few things that should help.? My original goal was to try to use the pre-processor and a single additional include file to try to not change any of the code, but I don't see a way this can work.? I found a few areas where the code syntax just needs to change.? (clearly we want NO changes in the functionality of the code, just syntax).
? ?Please note that my findings below are NOT criticisms.? The task here is simply to change compilers while keeping the operation of the code identical.
1) The MikroC compiler identifiers are NOT case-dependent.? So you will find variables like? "my_SW" and "my_sw" and they are identical.? This makes it a little harder to find things, but not impossible.? Just have some good search tools.? And then change them to all have the same case.
2) the assembler constructs are different.? MikroC uses? "asm CLRWDT"? ? and the MPLAB wants to see? 'asm ("CLRWDT").? ?So I'd suggest a global replace.? This seems to be the only assembly statement throughout the code.
3) The manipulation of register bits is different.? The MIkroC compiler has defined 'sbit' and lets you manipulate register labeled bits individually.? For the MPLab compiler, I created a union structure that lets me access the registers as either a byte, or a group of 8 individual bits.? This does force the code that manipulates the bits to change a bit.??
4) I'm now seeing warnings by the compiler about operator precedence.? I think the solution here is to simply add parentheses where needed.? I think we should try to end up with code that has zero warnings.
5) There are some built in libraries that will have to have replacements created.? They should not be hard, but will need to be invented. Things like software I2C bit banging, delay routines, EEPROM access, etc.
6) Lastly, I don't yet understand the details of the 'BUTTON' function.? I'll have to look it up to understand what it does, but I suspect it is a built in library that we will have to replicate.
All for now.? Hope this helps,
Dave
?
?
?
--
ana
|
Re: Programming & compiling from github source code
Hi Onno,
? ?Sounds like a good plan.??
? ?I've been looking into compiling this under the MPLAB, and found a few things that should help.? My original goal was to try to use the pre-processor and a single additional include file to try to not change any of the code, but I don't see a way this can work.? I found a few areas where the code syntax just needs to change.? (clearly we want NO changes in the functionality of the code, just syntax).
? ?Please note that my findings below are NOT criticisms.? The task here is simply to change compilers while keeping the operation of the code identical.
1) The MikroC compiler identifiers are NOT case-dependent.? So you will find variables like? "my_SW" and "my_sw" and they are identical.? This makes it a little harder to find things, but not impossible.? Just have some good search tools.? And then change them to all have the same case.
2) the assembler constructs are different.? MikroC uses? "asm CLRWDT"? ? and the MPLAB wants to see? 'asm ("CLRWDT").? ?So I'd suggest a global replace.? This seems to be the only assembly statement throughout the code.
3) The manipulation of register bits is different.? The MIkroC compiler has defined 'sbit' and lets you manipulate register labeled bits individually.? For the MPLab compiler, I created a union structure that lets me access the registers as either a byte, or a group of 8 individual bits.? This does force the code that manipulates the bits to change a bit.??
4) I'm now seeing warnings by the compiler about operator precedence.? I think the solution here is to simply add parentheses where needed.? I think we should try to end up with code that has zero warnings.
5) There are some built in libraries that will have to have replacements created.? They should not be hard, but will need to be invented. Things like software I2C bit banging, delay routines, EEPROM access, etc.
6) Lastly, I don't yet understand the details of the 'BUTTON' function.? I'll have to look it up to understand what it does, but I suspect it is a built in library that we will have to replicate.
All for now.? Hope this helps,
Dave
|
Ok Onno,
The 1k5 firmware (based on version 2.7) that I
sent has no active memory cells 31-34 (FF FF), so the measuring
path ratio must be set in the Flash memory of the main program.
It is possible that how to enter the correct value (Firmware
3.2) into cell 31 to work properly, but I do not know if the LCD
can display the power in 4 characters, e.g. 1234W?
Regards ,
Marek SQ7BCN
73
W dniu 2021-11-18 o?23:17, Onno PA1AP
pisze:
toggle quoted message
Show quoted text
We can run a diff on the versions to see the real
difference. It is also possible to convert the hex file to
assembly and see the changes.?
I will see what I can do this weekend.?
Regards Onno
Op do 18 nov. 2021 21:36
schreef sq7bcn < sq7bcn@...>:
Hi,
The difference is that the LCD is to
show the power value, e.g. 1500W, which probably
will not be shown by the version with the unadjusted
program (for Flash).
This is what Yuri EU2AV suggested to me ... I found
a correspondence from 2020 ...
Secondly, I am not sure of the gear setting for
correct Power measurement and SWR in my version is
20 turns in the coupling system.
All the time I would like David to speak on this
matter and dispel any doubts.
Regards ,
Marek SQ7BCN
73
W dniu 2021-11-17 o?23:29, Onno PA1AP pisze:
I can only think about the swr bridge being
different with the potentiometers. The pic
controller adc is the same. I have looked for
alignment information but unfortunately.?
Instead the easiest alignment is to
run full power and measure the max voltage towards
the adc. Depending on the pic controller you need
to adjust or 4 or 5 volt. I don't remember the
exact value unfortunately.
For the rest the circuit is exactly
the same as the atu-100. Just bigger components,
larger PCB traces.?
I don't understand why the pic
controller code should be different. Except for
the high power factor and bridge coil turns.?
Hope you can find the information as
eu2av shared with you.
Best regards Onno
Op wo 17 nov.
2021 20:25 schreef sq7bcn < sq7bcn@...>:
Hi Tim,
When it comes to the EE
data, I can make a copy of it, because I
have worked out the topic ... see the
attachment.
But it's not just about EE, so EU2AV
wrote to me that there are even changes
in Flash, I don't remember what it was
about, whether it was a power
measurement gear or something else, and
that's why it was done on version 2.7
because in version 3, x broaks memory
space.
That's why I'm asking, maybe David will
suggest something?
Pozdrawiam ,
Marek SQ7BCN
73
W dniu 2021-11-17 o?19:15, Tim pisze:
Hi Marek,
3.2 works fine in the ATU1000
BUT... Make a copy of the eeprom data
1st. ( this is what I didn't do with
mine and it took a while to work out the
cell values )
This is because the EU2AV version uses
different L & C for the tuner and
you will also need to know the turns
ratio for cell 31 and check that cell 30
is set to 01. All that is in your eeprom
data
When you update the s/w to 3.2 you will
have to input the cell data you copied
from your old version and write that to
the PIC.
You can then do a read of the PIC to
make sure that all is as expected and
then export that as a hex file as a
backup for just-in-case.
regards
Tim
On 17/11/21 7:33 am, sq7bcn wrote:
Hi,
I made a 1500W tuner according to the
EU2AV scheme (PIC 16F1938 processor).
David N7DDC firmware based on old
version 2.7.
Question for David,
is it possible to do it on software
version 3.1 or 3.2 and display the
correct power value?
Hex in the attachment.
Marek SQ7BCN
_
--
VK2XAX : QF56if : ITU59 : CQ30 : BMARC : WIA
|
I need a set of toroids and binocular core.? Anyone have a spare set to sell?
--
Dale Hardin
KS4NS
Elberta, AL
|
Re: Programming & compiling from github source code
I will creat a new GitHub repository and clone the existing one. The main page will obviously cover all the credits towards David and that atu-100 environment / concept.?
After the clone we can start working on the branches and perhaps even use the branches to develop the modules as needed. This is how I manage code and feature development. Each feature has its own branch and with a pull request it can be merged to the main branch. When a feature has to be changed one can pick the feature branch, apply the changes and merge it again to the main branch. This makes it easier to understand and manage the development process.
I will creat and confirm this week. Looking forward!?
Regards Onno
|
Re: Chinese clones - not working as expected
#ATU-10
Thanks David
I had thought you might be adding the fine facility to the standard ATU-10 operation, hence my query.
Glenn
|
Re: Shottky diodes, matching question
Just to close the loop on this... I ended up ordering another kit from a different supplier.? It seems to work reasonably well.? As for the original one?? The seller sent me replacement diodes (axial, to replace the surface mount ones), which I soldered into place.? Unfortunately, no change in behavior. He tells me he will send a replacement board kit, as it's possible there's an issue with something surface mounted.? I haven't seen evidence of it shipping yet, but dare to dream...
As far as VA3RR's offer of the toroids - I'm no longer confident the problem is with them.? If I ever decide to tackle the board again, I'll reach out to see if you still have any.? The offer is certainly appreciated.
Thanks for the comments!
|
Re: Chinese clones - not working as expected
#ATU-10
Glenn .
External control port. 3.5 mm audio jack.
|
Re: Programming failed at Program Memory address 0x000001
#atu-100
Thanks again Onno,
I verified this morning that it reads ok.? I did a read and then a verify and it is 100%.? I loaded the 3.02 Hex file and did a verify and the Program Memory verifies just fine.??
So it looks like as if my issue is an inconsistent behavior on write.? I did see it succeed on write once or twice - but as you do when you are trying things multiple times you start doubting what you saw.
Thanks again and 73,
Dean
KK4DAS
|
Re: Programming failed at Program Memory address 0x000001
#atu-100
Not sure unfortunately. I am using Linux and pickit 4 and it works without changing settings.?
It could have to do with timing and the programmer being to fast. There is an option in my settings to use slow writing. Not sure if it exists within windows. Alternative is to use another USB cable since it have found this sometimes causes issues too.?
Hope you can get it to work. Regards Onno
On Fri, Nov 19, 2021 at 03:56 AM, Onno PA1AP wrote:
Sounds to me you might have forgotten to "release" after programming
Hi Onno,
Thank you.? The Windows software does a verify after write by default.? I click the "write' button and it writes but the verify fails.? It's intermittent where it fails.? Not always at address 1.? And if I just perform a "read' it's clearly not reading properly... Just glancing at the results and I can tell it hasn't read properly. Lots of zeros, even the eeprom read is clearly not working right.
73,
Dean
KK4DAS
|
Re: Programming failed at Program Memory address 0x000001
#atu-100
On Fri, Nov 19, 2021 at 03:56 AM, Onno PA1AP wrote:
Sounds to me you might have forgotten to "release" after programming
Hi Onno, Thank you.? The Windows software does a verify after write by default.? I click the "write' button and it writes but the verify fails.? It's intermittent where it fails.? Not always at address 1.? And if I just perform a "read' it's clearly not reading properly... Just glancing at the results and I can tell it hasn't read properly. Lots of zeros, even the eeprom read is clearly not working right. 73, Dean
KK4DAS
|
Re: Programming failed at Program Memory address 0x000001
#atu-100
Sounds to me you might have forgotten to "release" after programming. I don't know how the windows interface looks like but look for reset / release after the write sequence.?
Best regards Onno
Hi all -?
This is a fun little project!
Just finished my build and realized that there is a newer firmware.? I ordered a PickKit 3 clone from ebay and downloaded the programmer software from the MicroChip archive - PiCkit 3 Progammer V 3.10
The programmer detects the correct MCU and I was able to load the ATU version 3.2 hex file and change the eeprom setting for the display,? However every time I try to write the firmware to the board I get a Programming Failed error and when I try to Verify that fails.? ? When I try to read the device at all it looks like its not reading.
All that said - after loading the firmware and getting the "Program failed..." message I reconnected the display and it booted up.? I tried the test mode and can step through the relays with a satisfying "click".
So any idea what may be going on? Faulty programmer?? Faulty operator?? It feels kind of odd to have a device that is working after a 'failed' programming update.? ?
I really like this kit - its a good one for inexperienced builders.? I may do this as group buildathon with our club's Maker's group.
73,
Dean
KK4DAS
|
Programming failed at Program Memory address 0x000001
#atu-100
Hi all -? This is a fun little project! Just finished my build and realized that there is a newer firmware.? I ordered a PickKit 3 clone from ebay and downloaded the programmer software from the MicroChip archive - PiCkit 3 Progammer V 3.10 The programmer detects the correct MCU and I was able to load the ATU version 3.2 hex file and change the eeprom setting for the display,? However every time I try to write the firmware to the board I get a Programming Failed error and when I try to Verify that fails.? ? When I try to read the device at all it looks like its not reading. All that said - after loading the firmware and getting the "Program failed..." message I reconnected the display and it booted up.? I tried the test mode and can step through the relays with a satisfying "click". So any idea what may be going on? Faulty programmer?? Faulty operator?? It feels kind of odd to have a device that is working after a 'failed' programming update.? ? I really like this kit - its a good one for inexperienced builders.? I may do this as group buildathon with our club's Maker's group. 73, Dean KK4DAS 
|
Re: Chinese clones - not working as expected
#ATU-10
David
What ports do you plan to use for the manual tuning?
There are currently 4 spare port pins on the PIC16F18877.
Glenn
|
We can run a diff on the versions to see the real difference. It is also possible to convert the hex file to assembly and see the changes.?
I will see what I can do this weekend.?
Regards Onno
Op do 18 nov. 2021 21:36 schreef sq7bcn < sq7bcn@...>:
Hi,
The difference is that the LCD is to show the
power value, e.g. 1500W, which probably will not be shown by the
version with the unadjusted program (for Flash).
This is what Yuri EU2AV suggested to me ... I found a
correspondence from 2020 ...
Secondly, I am not sure of the gear setting for correct Power
measurement and SWR in my version is 20 turns in the coupling
system.
All the time I would like David to speak on this matter and
dispel any doubts.
Regards ,
Marek SQ7BCN
73
W dniu 2021-11-17 o?23:29, Onno PA1AP
pisze:
I can only think about the swr bridge being different with
the potentiometers. The pic controller adc is the same. I have
looked for alignment information but unfortunately.?
Instead the easiest alignment is to run full
power and measure the max voltage towards the adc. Depending
on the pic controller you need to adjust or 4 or 5 volt. I
don't remember the exact value unfortunately.
For the rest the circuit is exactly the same as
the atu-100. Just bigger components, larger PCB traces.?
I don't understand why the pic controller code
should be different. Except for the high power factor and
bridge coil turns.?
Hope you can find the information as eu2av
shared with you.
Best regards Onno
Op wo 17 nov. 2021 20:25
schreef sq7bcn < sq7bcn@...>:
Hi Tim,
When it comes to the EE data, I can
make a copy of it, because I have worked out the
topic ... see the attachment.
But it's not just about EE, so EU2AV wrote to me
that there are even changes in Flash, I don't
remember what it was about, whether it was a power
measurement gear or something else, and that's why
it was done on version 2.7 because in version 3, x
broaks memory space.
That's why I'm asking, maybe David will suggest
something?
Pozdrawiam ,
Marek SQ7BCN
73
W dniu 2021-11-17 o?19:15, Tim pisze:
Hi Marek,
3.2 works fine in the ATU1000
BUT... Make a copy of the eeprom data 1st. ( this
is what I didn't do with mine and it took a while to
work out the cell values )
This is because the EU2AV version uses different L
& C for the tuner and you will also need to know
the turns ratio for cell 31 and check that cell 30
is set to 01. All that is in your eeprom data
When you update the s/w to 3.2 you will have to
input the cell data you copied from your old version
and write that to the PIC.
You can then do a read of the PIC to make sure that
all is as expected and then export that as a hex
file as a backup for just-in-case.
regards
Tim
On 17/11/21 7:33 am, sq7bcn wrote:
Hi,
I made a 1500W tuner according to the EU2AV scheme
(PIC 16F1938 processor).
David N7DDC firmware based on old version 2.7.
Question for David,
is it possible to do it on software version 3.1 or
3.2 and display the correct power value?
Hex in the attachment.
Marek SQ7BCN
_
--
VK2XAX : QF56if : ITU59 : CQ30 : BMARC : WIA
|
Hi,
The difference is that the LCD is to show the
power value, e.g. 1500W, which probably will not be shown by the
version with the unadjusted program (for Flash).
This is what Yuri EU2AV suggested to me ... I found a
correspondence from 2020 ...
Secondly, I am not sure of the gear setting for correct Power
measurement and SWR in my version is 20 turns in the coupling
system.
All the time I would like David to speak on this matter and
dispel any doubts.
Regards ,
Marek SQ7BCN
73
W dniu 2021-11-17 o?23:29, Onno PA1AP
pisze:
toggle quoted message
Show quoted text
I can only think about the swr bridge being different with
the potentiometers. The pic controller adc is the same. I have
looked for alignment information but unfortunately.?
Instead the easiest alignment is to run full
power and measure the max voltage towards the adc. Depending
on the pic controller you need to adjust or 4 or 5 volt. I
don't remember the exact value unfortunately.
For the rest the circuit is exactly the same as
the atu-100. Just bigger components, larger PCB traces.?
I don't understand why the pic controller code
should be different. Except for the high power factor and
bridge coil turns.?
Hope you can find the information as eu2av
shared with you.
Best regards Onno
Op wo 17 nov. 2021 20:25
schreef sq7bcn < sq7bcn@...>:
Hi Tim,
When it comes to the EE data, I can
make a copy of it, because I have worked out the
topic ... see the attachment.
But it's not just about EE, so EU2AV wrote to me
that there are even changes in Flash, I don't
remember what it was about, whether it was a power
measurement gear or something else, and that's why
it was done on version 2.7 because in version 3, x
broaks memory space.
That's why I'm asking, maybe David will suggest
something?
Pozdrawiam ,
Marek SQ7BCN
73
W dniu 2021-11-17 o?19:15, Tim pisze:
Hi Marek,
3.2 works fine in the ATU1000
BUT... Make a copy of the eeprom data 1st. ( this
is what I didn't do with mine and it took a while to
work out the cell values )
This is because the EU2AV version uses different L
& C for the tuner and you will also need to know
the turns ratio for cell 31 and check that cell 30
is set to 01. All that is in your eeprom data
When you update the s/w to 3.2 you will have to
input the cell data you copied from your old version
and write that to the PIC.
You can then do a read of the PIC to make sure that
all is as expected and then export that as a hex
file as a backup for just-in-case.
regards
Tim
On 17/11/21 7:33 am, sq7bcn wrote:
Hi,
I made a 1500W tuner according to the EU2AV scheme
(PIC 16F1938 processor).
David N7DDC firmware based on old version 2.7.
Question for David,
is it possible to do it on software version 3.1 or
3.2 and display the correct power value?
Hex in the attachment.
Marek SQ7BCN
_
--
VK2XAX : QF56if : ITU59 : CQ30 : BMARC : WIA
|
Re: Chinese clones - not working as expected
#ATU-10
Hi David
That would be brilliant
73,
Jon G4TSN
toggle quoted message
Show quoted text
----- Original Message ----- From: "David Fainitski" <rolin791@...> To: < [email protected]> Sent: Thursday, November 18, 2021 2:23 PM Subject: Re: [ATU100] Chinese clones - not working as expected #ATU-10 Hi. OK, I will implement zero position for L and C. That is not a big problem. Also I can do a manual tuning L and C with additional buttons + and - connected to Ext port .
|
Re: Chinese clones - not working as expected
#ATU-10
Hi David, thanks a lot for your efforts! Vy 73 de
toggle quoted message
Show quoted text
Am 18.11.2021 um 15:23 schrieb David Fainitski <rolin791@...>:
?Hi.?
OK, I will implement zero position for L and C.
That is not a big problem.
Also I can do a manual tuning L and C with additional buttons + and - connected to Ext port .
|
Dale Hardin KS4NS
Onno PA1AP
Rolf Schroeder