RE: [V4Protocol] FEC works great
I changed the settings within Power SDR software to those shown in the WINMOR setup files. Actually those setting aren’t much different than what I already had. Also made some minor changes in the VAC settings. Today was the first time I’ve had the opportunity to run a test. Made a contact with Bob, W0FYI and I was able to send data (ARQ) which he saw. However, he told me that although he had data in the buffer to send, it never did send. It also seemed to me that it took a long time for the my data transmission to trigger transmit. At this point I’m not sure what needs to change. I did reinstall WINMOR and sent myself a test email message through a node. It worked fine. Very perplexing.
Almost certainly the problem is related to the Flex. We have used WINMOR successfully (in ARQ mode) with a flex but it requires careful Flex setup to minimize the latency. The flex can add considerable latency to the audio which adds up to a problem in some ARQ modes. I don’t know the timing of ALE-400 ARQ. The other problem could be any hang or hold of the PTT blocking off the reception of initial leader. If it works on FEC the same exact data mode and modulation is used for ARQ...The only difference is the frame ID code and the ARQ protocol. If you have setup WINMOR on the Flex the same setup should work for V4. The WINMOR help file has the details for the flex setup. If you don’t have a WINMOR setup I can probably send you the help file for WINMOR and that may help you with the setup. The latency that the flex can add can be a problem especially on fast ARQ turn around modes like Pactor 2, 3, or 4.
- Kirk,It sounds like may not understand the operation of the ARQ and when and how data is transferred. Read the help on ARQ operation. You can only send when you are the ISS but you can still queue outbound data while you are the IRS.While we are still debugging the software in early beta testing casual descriptions don’t help much....In software the devil is in the details.If you see something strange here is the way to help improve the problem:1) Be sure you have debug logging enabled ...without that there is little data captured for debugging.2) Describe the problem in words. Note the approximate time (UTC) the problem was observed. I don’t have the time to wade through hundreds of K of debug logs.3) Describe your setup (Radio, Sound card/interface, OS, CPU Type, RAM, Keying Setup)4) Send me the file V4 TNC Debug <date>.log as an attachment. Send directly to rmuethingATcfl.rr.com not posted through the reflector.With the above I can do something. With generalized comments it is very difficult.73,