Date   
Re: W0EB/W2CTX Latest uBITX software release #ubitx

Jim Sheldon
 

Arigato - hi hi

Re: W0EB/W2CTX Latest uBITX software release #ubitx

Jim Sheldon
 

Arigao gozaimasu Mitani San, 

73, 
Jim, W0EB

Are you looking for a case for your Bitx?

Dr Fred Hambrecht
 

Looking at stuff on EBay there is a ton of EXTON equipment for sale. I bring it up because the equipment is cheaper than cases and many already have 16X2 or 20X4 displays already installed. Lots of connectors as well. A search of "EXTON" will give you a ton of ideas.

v/r
Fred W4JLE

Re: CAT Support uBITX Firmware CEC Version 1.0 Release #ubitx

Ian Lee
 

Jerry.

You wrote while I was writing a long story.

Yes. There is a problem when writing to the eeprom periodically. so Various avoidance methods are used.
Increased conditions for writing eeprom, sequential writing of multiple eeproms, random access, 
If you are interested, you can see how I avoided the eeprom life time in my code.
I've used Arduino for the first time, but the firmware has been working in various project for quite some time. 
So I check the datasheet before you start the project like you.
For parts with life cycle such as eeprom, relay, etc., calculations must be done first.

Thanks you good information.

Ian KD8CEC

2018-02-08 10:43 GMT+09:00 Jerry Gaffke via Groups.Io <jgaffke@...>:

In section 8.4 of the ATmega328P datasheet (used on the Nano, which is used on the Raduino) 
    (EEPROM) is organized as a separate data space, in which single bytes can be read and written.
    The EEPROM has an endurance of at least 100,000 write/erase cycles.
So can update each individual byte 100,000 times.
Hard to imagine burning out an EEPROM byte if it involved twiddling knobs and pressing some buttons for each update.

Where you get into trouble is when the code writes to EEPROM with no operator intervention.
Takes about 3.4ms to erase and write an eeprom byte, so a code loop could burn out a byte of eeprom in about an hour.


On Wed, Feb 7, 2018 at 03:49 pm, Ronald Pfeiffer wrote:
would be careful since EEPROM has a finite write life!
These nano's are soldered in.
 
rOn
 
From: Mike Woods <mhwoods@...>   Sent: Wednesday, February 7, 2018 6:27 PM
There are 20 memory channels in the latest versions (0.35 and 1.0) and they are stored in EEPROM



--
Best 73
KD8CEC / Ph.D ian lee
kd8cec@...
www.hamskey.com (my blog)

Re: CAT Support uBITX Firmware CEC Version 1.0 Release #ubitx

Ian Lee
 

Thanks for very important information.

The lifetime of the eeprom guaranteed by the vendor is 100,000 write cycle. read cycle is unlimited.
One thing to note is 100,000 times per memory address.
It is not important how many eeprom addresses are used, but how much is written to one eeprom address is important.
There is no problem with using a typical eeprom. 100,000 times more than thought is very large.
Some people say that they have used more than 100,000 through the experiment, but it is better to use the range that the vendor guarantees.

Experience has shown that the eeprom lifetime error is one case.
It is a periodic write to one memory address.
The most vulnerable is to use eeprom in loops like for and while, or to use the eeprom periodically in the timer.

In case of uBITX, cyclic frequency(with mode) storage to eeprom will be a problem to automatically display the frequency that was used previously when the radio is turned on and off.

If you save every 5 seconds, 720 writes occur in 1 hour. The life of the eeprom guaranteed by the vendor is only 138 hours. If use it for 2 hours every day, the life time of 70 days is over.
Of course, the actual life of the eeprom is much longer than the number of times it is guaranteed by the business. Because we are not always lucky, i will not discuss it here.

So, I am actively agreeing with ron's important information.

I have put some of safeguards in my firmware to take into account the life of the eeprom.
The first is virtual eeprom. I created the same variable as eeprom that I had to write periodically and put it in memory.
Compared to the contents of memory before writing to eeprom, I made it write if it changed.
This avoids unnecessarily wasting the write cycle on a periodic basis and preventing the CPU usable
Another was to identify the intent of the user. In other words, if the frequency is changing rapidly, the user is turning the knob.
That is, if the frequency is changing, it will skip even if the periodic storage time is reached.

Always be careful when using eeprom in loop statements or timers.

Ian KD8CEC

2018-02-08 8:49 GMT+09:00 Ronald Pfeiffer via Groups.Io <w2ctx@...>:

I would be careful since EEPROM has a finite write life!
These nano's are soldered in.

rOn



From: Mike Woods <mhwoods@...>
To: BITX20@groups.io
Sent: Wednesday, February 7, 2018 6:27 PM
Subject: Re: [BITX20] CAT Support uBITX Firmware CEC Version 1.0 Release #ubitx

There are 20 memory channels in the latest versions (0.35 and 1.0) and they are stored in EEPROM.

Mike

On Thu, 8 Feb 2018 at 11:14 AM, John P <j.m.price@...> wrote:
Not familiar with your code, but maybe keep the memories in EEPROM. 
--
John - WA2FZW




--
Best 73
KD8CEC / Ph.D ian lee
kd8cec@...
www.hamskey.com (my blog)

Re: CAT Support uBITX Firmware CEC Version 1.0 Release #ubitx

W2CTX
 

You can eat up 100,000 writes.  Each time you change any menu item
it gets stored in EEPROM.  Ian also automatically stores the current
frequency each time you change it.

Also I meant after several years when users get intermittent errors
for no apparent reason!

rOn



From: Jerry Gaffke via Groups.Io <jgaffke@...>
To: BITX20@groups.io
Sent: Wednesday, February 7, 2018 8:44 PM
Subject: Re: [BITX20] CAT Support uBITX Firmware CEC Version 1.0 Release #ubitx

In section 8.4 of the ATmega328P datasheet (used on the Nano, which is used on the Raduino) 
    (EEPROM) is organized as a separate data space, in which single bytes can be read and written.
    The EEPROM has an endurance of at least 100,000 write/erase cycles.
So can update each individual byte 100,000 times.
Hard to imagine burning out an EEPROM byte if it involved twiddling knobs and pressing some buttons for each update.

Where you get into trouble is when the code writes to EEPROM with no operator intervention.
Takes about 3.4ms to erase and write an eeprom byte, so a code loop could burn out a byte of eeprom in about an hour.


On Wed, Feb 7, 2018 at 03:49 pm, Ronald Pfeiffer wrote:
would be careful since EEPROM has a finite write life!
These nano's are soldered in.
 
rOn
 
From: Mike Woods <mhwoods@...>   Sent: Wednesday, February 7, 2018 6:27 PM
There are 20 memory channels in the latest versions (0.35 and 1.0) and they are stored in EEPROM


Re: CAT Support uBITX Firmware CEC Version 1.0 Release #ubitx

Jerry Gaffke
 

In section 8.4 of the ATmega328P datasheet (used on the Nano, which is used on the Raduino) 
    (EEPROM) is organized as a separate data space, in which single bytes can be read and written.
    The EEPROM has an endurance of at least 100,000 write/erase cycles.
So can update each individual byte 100,000 times.
Hard to imagine burning out an EEPROM byte if it involved twiddling knobs and pressing some buttons for each update.

Where you get into trouble is when the code writes to EEPROM with no operator intervention.
Takes about 3.4ms to erase and write an eeprom byte, so a code loop could burn out a byte of eeprom in about an hour.


On Wed, Feb 7, 2018 at 03:49 pm, Ronald Pfeiffer wrote:
would be careful since EEPROM has a finite write life!
These nano's are soldered in.
 
rOn
 
From: Mike Woods <mhwoods@...>   Sent: Wednesday, February 7, 2018 6:27 PM
There are 20 memory channels in the latest versions (0.35 and 1.0) and they are stored in EEPROM

New file uploaded to BITX20@groups.io

BITX20@groups.io Notification <BITX20+notification@...>
 

Hello,

This email message is a notification to let you know that a file has been uploaded to the Files area of the BITX20@groups.io group.

File: ubitx_I2C_V2_00R.zip

Uploaded By: Jim Sheldon

Description:
W0EB/W2CTX latest I2C modification and software for the uBITX. This version is an almost total overhaul of our first I2C release - simpler menu system, extra A/B SPLIT pushbutton mod - A3 A6 and A7 analog lines now available for programming. Keyer inputs have been moved to D8, D11 and D12 as well as PTT to D12. Complete, illustrated instruction manual included in the zip file along with the extra, required LiquidCrystal_I2C library for the Arduino IDE (IDE Version 1.8.5 or later required to compile).

You can access this file at the URL:
https://groups.io/g/BITX20/files/ubitx_I2C_V2_00R.zip

Cheers,
The Groups.io Team

Re: CAT Support uBITX Firmware CEC Version 1.0 Release #ubitx

Ian Lee
 

Philip 

Yes, that's right. I made various attempts to put a lot of features into a small space.
Any attempt was good. (ex:change method using strings, Applying new logic to display frequencies ...)
However, there were times when I did not see the effect. (ex : Merge menus - Put all the toggle menus functionality in one function, Put all the use encoder menus functionality in one function)
I was able to save a little bit of flash memory, but the code was quite complicated. So I erased those codes and recover before sources.
For CAT communication, i implemented only protocols that uBITX can use.

Ian KD8CEC



2018-02-08 7:11 GMT+09:00 Philip <philip.g7jur@...>:

Hi Max.
I think the firmware has left no room for memory's.

Philip Lock G7JUR



--
Best 73
KD8CEC / Ph.D ian lee
kd8cec@...
www.hamskey.com (my blog)

Re: W0EB/W2CTX Latest uBITX software release #ubitx

Jim Sheldon
 

Anyone else using our software that can confirm this behavior?  Not sure Here.

jim - W0EB

Re: CAT Support uBITX Firmware CEC Version 1.0 Release #ubitx

Ian Lee
 

Max
I have not used rigctl in command mode.  I'll try the rigctl command if I have a chance. 

In FT-817 compliant CAT control, eeprom read / write is rarely used. 
VFOA / VFOB conversion, get / set cw speed, get / set side tone, and get split status. 
I have run several programs and checking which using protocol with the logic analyzer.
and uBITX emulated only necessary protocols. So things that are not needed in uBITX like FT-817's output adjustment, antenna connector position, etc. will not be controlled.

Instead I created a new protocol for just uBITX eeprom control.
I made it so simple that it can be applied to all firmware within 20 lines of code.
uBITX Manager uses this protocol. 
uBITX Manager does not use FT-817 protocol but uses uBITX proprietary protocol, so it can not be controlled by general purpose program.


I am happy to get a lot of information while starting amateur radio again.

Ian KD8CEC

2018-02-08 6:17 GMT+09:00 Max Lock <max@...>:

Thanks Ian for all your hard work, it's really appreciated! :)

I've not played with the ubitx manager as I use Linux, but is the CAT functionality ever likely to emulate the ft-718 memory read/write functionality?

eg.

maxwell@nimbus:~/Desktop$ rigctl --model=120 --set-conf=rig_pathname=/dev/ttyUSB0 -v e
Opened rig model 120, 'FT-817'
get_mem: error = Feature not available


-Cheers Max, G7UOZ.






--
Best 73
KD8CEC / Ph.D ian lee
kd8cec@...
www.hamskey.com (my blog)

Re: CAT Support uBITX Firmware CEC Version 1.0 Release #ubitx

Ian Lee
 

Konstantinos

Thank you for information.
I ended up trying to starcraft Linux on Linux a long time ago.
using wine is good idea!!!.
If you're using wine on Linux, would you give it a try? I will challenge when the project is over.  And I also trying execute it on mono base.

Your opinion will be helpful.
Thanks agian   Konstantinos

Ian KD8CEC

2018-02-08 7:50 GMT+09:00 Konstantinos Konstas <constantine170@...>:

Ian,
Speaking of the Manager, it would be nice to run under Linux.
Any chance to play under Wine for example?

73 de Konstantinos, SV1ONW

On 7 February 2018 at 23:17, Max Lock <max@...> wrote:
Thanks Ian for all your hard work, it's really appreciated! :)

I've not played with the ubitx manager as I use Linux, but is the CAT functionality ever likely to emulate the ft-718 memory read/write functionality?

eg.

maxwell@nimbus:~/Desktop$ rigctl --model=120 --set-conf=rig_pathname=/dev/ttyUSB0 -v e
Opened rig model 120, 'FT-817'
get_mem: error = Feature not available


-Cheers Max, G7UOZ.







--
73 de SV1ONW



--
Best 73
KD8CEC / Ph.D ian lee
kd8cec@...
www.hamskey.com (my blog)

Re: W0EB/W2CTX Latest uBITX software release #ubitx

Jim Sheldon
 

It has just been called to my attention that there may be a bug in this version.  When entering the menu, it works fine for several iterations and then begins immediately returning to the main operation screen as soon as the encoder button is released rather than staying in the menu to allow selection of an item to change. 

We're looking into this and will post a fixed file as soon as possible.

W0EB and W2CTX

Re: CAT Support uBITX Firmware CEC Version 1.0 Release #ubitx

W2CTX
 

I would be careful since EEPROM has a finite write life!
These nano's are soldered in.

rOn



From: Mike Woods <mhwoods@...>
To: BITX20@groups.io
Sent: Wednesday, February 7, 2018 6:27 PM
Subject: Re: [BITX20] CAT Support uBITX Firmware CEC Version 1.0 Release #ubitx

There are 20 memory channels in the latest versions (0.35 and 1.0) and they are stored in EEPROM.

Mike

On Thu, 8 Feb 2018 at 11:14 AM, John P <j.m.price@...> wrote:
Not familiar with your code, but maybe keep the memories in EEPROM. 
--
John - WA2FZW


Re: CAT Support uBITX Firmware CEC Version 1.0 Release #ubitx

Mike Woods
 

There are 20 memory channels in the latest versions (0.35 and 1.0) and they are stored in EEPROM.

Mike


On Thu, 8 Feb 2018 at 11:14 AM, John P <j.m.price@...> wrote:
Not familiar with your code, but maybe keep the memories in EEPROM. 
--
John - WA2FZW

Re: CAT Support uBITX Firmware CEC Version 1.0 Release #ubitx

W2CTX
 

What minimum functions exactly are you looking for in a linux manager?

rOn

Re: CAT Support uBITX Firmware CEC Version 1.0 Release #ubitx

Konstantinos Konstas
 

Ian,
Speaking of the Manager, it would be nice to run under Linux.
Any chance to play under Wine for example?

73 de Konstantinos, SV1ONW

On 7 February 2018 at 23:17, Max Lock <max@...> wrote:
Thanks Ian for all your hard work, it's really appreciated! :)

I've not played with the ubitx manager as I use Linux, but is the CAT functionality ever likely to emulate the ft-718 memory read/write functionality?

eg.

maxwell@nimbus:~/Desktop$ rigctl --model=120 --set-conf=rig_pathname=/dev/ttyUSB0 -v e
Opened rig model 120, 'FT-817'
get_mem: error = Feature not available


-Cheers Max, G7UOZ.







--
73 de SV1ONW

Re: CAT Support uBITX Firmware CEC Version 1.0 Release #ubitx

John P
 

Not familiar with your code, but maybe keep the memories in EEPROM. 
--
John - WA2FZW

Re: CAT Support uBITX Firmware CEC Version 1.0 Release #ubitx

Philip
 

Hi Max.
I think the firmware has left no room for memory's.

Philip Lock G7JUR

Re: CAT Support uBITX Firmware CEC Version 1.0 Release #ubitx

Max Lock
 

Thanks Ian for all your hard work, it's really appreciated! :)

I've not played with the ubitx manager as I use Linux, but is the CAT functionality ever likely to emulate the ft-718 memory read/write functionality?

eg.

maxwell@nimbus:~/Desktop$ rigctl --model=120 --set-conf=rig_pathname=/dev/ttyUSB0 -v e
Opened rig model 120, 'FT-817'
get_mem: error = Feature not available


-Cheers Max, G7UOZ.