Hi everyone, here’s the latest state of codec2-FreeDATA:

https://github.com/DJ2LS/codec2-FreeDATA/blob/main/documentation/codec2-FreeDATA_05.09.2021_11_29_05.mp4?raw=true


The project is moving forward - step by step - but still a lot of work to do. 
But as you can already see, I integrated the data module into the application, 
so no additional software is needed for sending data. All application settings 
are visible on the main screen. No hidden settings. Just those who are visible 
and necessary. Lets see If I can continue with this idea.

As soon as its possible to send data (which is already working, but unstable)  
and the GUI + TNC is in a more stable state, I will make another announcement.

Have a good time!
Simon, DJ2LS




> 
>> Am 19.07.2021 um 05:33 schrieb Simon Lang <lang.si...@gmx.net 
>> <mailto:lang.si...@gmx.net>>:
>> 
>> Hi everyone,
>> 
>> I’m Simon, DJ2LS, and I'm working on my project „codec2 - FreeDATA“ since 
>> some month.
>> 
>> My goal is to create a multiplattform, open-source TNC, with an easy to use 
>> GUI.
>> At the moment the project is Linux only and not usable yet. It's a prototype 
>> and I’m improving my programming skills „learning by doing“. So expect a lot 
>> of failures, problems, uncommon programming stuff. But at least I thought - 
>> Just do it!  And here are the first results:
>> 
>> 
>> ##### GUI 
>> The basic GUI is already working. Easy selection of audio devices and radio 
>> via Hamlib. Some status messages of the TNC are working as well. A huge 
>> part, which is still not working, is the waterfall diagram to have a look 
>> over the band / channel and its busy state. 
>> My plans are, to create a GUI with different modules:
>> - Data transfer module
>> - Chat module, with a modern, smartphone like design
>> - Beacon module
>> The entire GUI is a network application. So you can control and send data 
>> within your private network by default. The future idea is, sitting on the 
>> couch and chatting via HF...
>> 
>> ##### TNC
>> The TNC itself is written in Python and will be a CLI application. But you 
>> don’t have to fight with a lot of CLI commands - Just start the TNC and 
>> everything can be configured via network GUI.
>> I’m also doing some basic TNC behavior a little bit different:
>> - You don’t have to connect to another station to send data and keeping the 
>> channel opened ( and the channel busy as well )
>> This means, that if you want to send data to another station, you have to 
>> open a data channel ( automatically), which will be closed as soon as the 
>> data has been transmitted. 
>> 
>> 
>> ##### ARQ
>> I already created support for different ARQ modes :
>> - Stop-and-Wait
>> - Go-Back-N
>> - Selective Repeat 
>> You can also mix them together by selecting the amount of data frames per 
>> acknowledge burst and repeating lost frames. This is working in my 
>> development environment with some restrictions, but needs some more real 
>> tests with some kilometers between the stations. Somewhen in the future 
>> "path measurement" will automatically select the best constellation between 
>> frames per burst, amount of data and channel quality.
>> 
>> 
>> 
>> You can find everything in my Github repository:
>> https://github.com/DJ2LS/codec2-FreeDATA 
>> <https://github.com/DJ2LS/codec2-FreeDATA>
>> 
>> I don’t have that much time because of my job, so I’m doing everything step 
>> by step. 
>> Actually I’m working on the data module and a huge amount of documentation 
>> needs to be done as well.
>> But everything looks promising.  
>> 
>> 
>> Have a good start into the week! 
>> Simon, 
>> DJ2LS 
>> _______________________________________________
>> Freetel-codec2 mailing list
>> Freetel-codec2@lists.sourceforge.net 
>> <mailto:Freetel-codec2@lists.sourceforge.net>
>> https://lists.sourceforge.net/lists/listinfo/freetel-codec2
> 

_______________________________________________
Freetel-codec2 mailing list
Freetel-codec2@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freetel-codec2

Reply via email to