saybur
Well-known member
Some more progress: the unknown extended message can apparently just be ignored. If the firmware does that instead of sending MESSAGE REJECT things... just work. That's not a very satisfying answer and I hope it isn't creating a hidden problem. On the plus side, large transfers are working, and the files are intact on arrival. Huzzah!
I also did some work on the packet reception code in general. The real hardware has some long wait times (~100-150us) as it switches phases during packet reception. I was originally emulating this behavior. However, those do not appear to be important, and after commenting them out packet reception is noticeably faster. A speed test using the same dataset as in previous post:
"scuznet" emulated device: 38.6 MB in 3m49s, or ~1.35 Mbit/sec
That's about 15% faster than the same test on the real Nuvolink, which I'm pretty happy to see! It'll need more testing to verify if there's an actual improvement overall, but it's encouraging none the less.
I also did some work on the packet reception code in general. The real hardware has some long wait times (~100-150us) as it switches phases during packet reception. I was originally emulating this behavior. However, those do not appear to be important, and after commenting them out packet reception is noticeably faster. A speed test using the same dataset as in previous post:
"scuznet" emulated device: 38.6 MB in 3m49s, or ~1.35 Mbit/sec
That's about 15% faster than the same test on the real Nuvolink, which I'm pretty happy to see! It'll need more testing to verify if there's an actual improvement overall, but it's encouraging none the less.