Crash_Override/FreeDATA
1
0
Fork 0
mirror of https://github.com/DJ2LS/FreeDATA synced 2024-05-14 08:04:33 +00:00
Code Issues Projects Releases Packages Wiki Activity
1220 commits 13 branches 131 tags 69 MiB
Commit graph

142 commits

Author SHA1 Message Date
Paul Kronenwetter
0e43f65bc2 Add function docstring to received_session_close. 2022-05-01 11:41:40 -04:00
Paul Kronenwetter
d2e38b77eb Implements another TODO from #173 . 
Corrects previous fix as well.
 2022-05-01 11:34:31 -04:00
Paul Kronenwetter
7b4f75f66c Implements TODO from #173 . 2022-05-01 11:07:54 -04:00
dj2ls
0e8e3d1b67 fixed file transfer for 24bit crc 2022-05-01 11:19:59 +02:00
dj2ls
ffff256623 arq disconnect improvement 
this should fix and closes #173
 2022-04-30 13:03:24 +02:00
Paul Kronenwetter
e4b901adad Adding callsign for ID after stop transmission. 2022-04-24 18:43:50 -04:00
Paul Kronenwetter
aefee60bad Initial attempt to fix issue #179. 2022-04-24 13:30:43 -04:00
dj2ls
107daa1b47 increased disconnect bursts 
lets see if this improves
#173
 2022-04-24 16:11:36 +02:00
dj2ls
57e4af83af first test with 24bit crc 
moved from 16bit crc to 24bit crc...First test for ping and file transfer seems to be working... This has been too easy... 🤔
 2022-04-19 11:09:11 +02:00
dj2ls
a90abb122f enable/disable cq response 
Enable and disable CQ response via GUI. Also moved settings to settings modal - with a small redesign. Auto updater still WIP
 2022-04-18 17:17:53 +02:00
dj2ls
88149830df first test with 6bit gridsquare encoding 
same for grid as call - we should think about saving the callsign and gridsquare as string and not as bytes. Also increased disconnect burst number where a toggle loop occured...
 2022-04-17 22:30:15 +02:00
dj2ls
53af74f757 first test with 6bit callsign encoding 
seems to work, but we have to redesign the way how we handle callsigns. This is really confusing...
 2022-04-17 22:16:13 +02:00
dj2ls
2daafd183a removed some info lines 2022-04-16 16:28:04 +02:00
Paul Kronenwetter
62b939fbc9 Replaced sleep with helpers.wait in transmit_qrv. 2022-04-15 19:59:12 -04:00
Paul Kronenwetter
9f9b5e98e2 Remove errant inclusion of NOCALL ping logging. 2022-04-15 15:24:12 -04:00
Paul Kronenwetter
82935dcaae Proof of concept automatic response to CQ. 
Uses new QRV frame rather than new BREPLY frame. Also changes CQ
behavior to send only one frame instead of 3.
NOTE: This implementation will respond *three* times to previous release
software (v0.3.3-alpha.3 and earlier).
 2022-04-15 15:17:14 -04:00
Paul Kronenwetter
08faa53f26 WIP: Proof of concept using BEACON and new BREPLY frames. 2022-04-15 14:41:20 -04:00
Paul Kronenwetter
195310dda1 Removing unneeded code. 
Bytearray fills with zero upon allocation.
 2022-04-15 11:26:53 -04:00
Paul Kronenwetter
802185b31a Removing commented frequency_offset code. 2022-04-15 11:03:14 -04:00
Paul Kronenwetter
02bc780dce Remove frequency_offset from received_ping. 2022-04-15 09:01:33 -04:00
DJ2LS
faefd84ae5 Revert "black code formatting" 
This reverts commit 92cfa367f3.
 2022-04-11 11:10:32 +02:00
dj2ls
92cfa367f3 black code formatting 2022-04-11 11:03:54 +02:00
Paul Kronenwetter
8e8a2c8432
Merge branch 'DJ2LS:main' into correct_typos 2022-04-10 17:32:50 -04:00
Paul Kronenwetter
ec490376a6 Additional corrections. 2022-04-10 17:31:49 -04:00
Paul Kronenwetter
cdefbb841f Better handle check_callsign changes. 2022-04-10 16:45:05 -04:00
Paul Kronenwetter
4358dd9c8a Correcting some typos. 2022-04-10 13:20:58 -04:00
dj2ls
c89e4beebf fixed audio device list 
audio device list not complete when init after multiprocessing init. #153
 2022-04-08 11:35:13 +02:00
dj2ls
500c657099 extended status message 
now we are able viewing a unique transmission status within chat messages. One step closer to a better way of handling status
 2022-04-07 11:19:29 +02:00
dj2ls
a2552be843 repeat frame ack and fixed repeat transmission from gui 2022-04-06 10:15:14 +02:00
dj2ls
47aff1a9f6 fix file transfer issue 
closes #151
 2022-04-05 11:29:20 +02:00
dj2ls
8f3f046655 improved logging and chat 2022-04-02 18:40:12 +02:00
dj2ls
04f6c49ac5 audio tuning and chat optimisation 
closes #117
 2022-04-02 14:54:43 +02:00
dj2ls
3f35a01b94 adjust volume level on TX 2022-03-31 21:13:30 +02:00
dj2ls
d3ee911186 enable/disable fsk mode 2022-03-31 12:45:44 +02:00
dj2ls
15217b2521 moved to sounddevice 
changed audio library, changed ssid behavior, minor chat changed
 2022-03-24 20:49:13 +01:00
dj2ls
4b296a48df added tuning range selector 2022-03-19 12:42:10 +01:00
dj2ls
fed075451a first release of chat 
several bug fixes
 2022-03-14 20:21:15 +01:00
dj2ls
f5f7060672 different changes 
network fixes, chat fixes, gui fixes...
 2022-03-12 15:06:49 +01:00
dj2ls
52a7714fd3 hotfix for data handler 
forgot numpy import...Ooops
 2022-03-11 21:52:44 +01:00
dj2ls
f190afa94a additional arq session state information 2022-03-11 20:38:28 +01:00
dj2ls
52310ffd4e moved beacon into own thread 
this should avoid blocking states caused by the beacon
 2022-03-10 20:46:34 +01:00
dj2ls
7134361267 improved rigctld network integration 2022-03-06 17:23:04 +01:00
dj2ls
1519c22358 connection mode, documentation, ... 
changes in all areas
 2022-03-04 16:50:32 +01:00
dj2ls
a358560c9f updated build action 
new day ...
 2022-02-25 09:28:42 +01:00
dj2ls
326391ccd8 moved to native bootstrap-icon usage 
also introduced a speed level field for tnc_state
 2022-02-22 21:05:48 +01:00
dj2ls
25392303e4 increased callsign length and added ssid 
this now more compatible to VARA to avoid confusion. Callsign length now 7 char + 1 ssid
 2022-02-21 12:20:36 +01:00
dj2ls
34cf0a4b05 cleanup 2022-02-19 20:45:57 +01:00
dj2ls
879ba00137 search for chunk from end 
according to the last commit we are now searching for data chunks from the end of the existing data. If a data chunk exists twice or more in our already received data, only the last one will be replaced
 2022-02-18 10:04:00 +01:00
dj2ls
6e0796f5a0 protocol adjustment 
if we are loosing a burst ACK because of fading signals or bad conditions or just because - combined with a changing speed level -  theres now a good chance we are not loosing the entire data frame because of a corrupted CRC, anymore. We are now searching in already received data, if our new (smaller) data chunk already exists. If so, we are stripping the entire data to this position and adding our new data chunk. If not, it seems we received new data the regulary way. However, this could cause problems if we have a too small data entropie. We might also check if we have an increased NACK counter or if a data chunk exists, twice or more -  in a further step
 2022-02-18 09:58:49 +01:00
dj2ls
a8d1d576ad sending twice before lowering speed-level 
possible this helps avoiding a problem with lost burst ACK
 2022-02-17 12:30:38 +01:00