defragster
Senior Member+
Msg #6 covers what I saw - adds at the end ...
FWIW - the lps_test ran overnight - Serial send seems fast and clean to uninterrupted PC
Was still running at ~210 lps since fresh restart - it is now in the ~170 range with firefox/sublime text open and active.
These errors are all to be expected and recorded:
9000 lines in dos box buffer when just copied
<update> :
>> multitasking OS seems to be more lossy than Teensy T4 at these rates - but that may just be because T4 is not supporting the 'availableForWrite()' to halt transmission when client gets busy:
> opened EDGE browser and that caused data glitch again - I have 7 EDGE windows open with a combined 38 web pages in tabs
> And opening each EDGE window to count the open tabs caused 3 data glitches with no apparent reason
> came back and the lps_test.exe had exited with NO ERROR - not sure if I did that? - then just reran it and it picked up on a buffer boundary with no T4 restart and no reported data glitch on starting.
Got a BARRAGE of FAILS on PC in use … went from #15 errors to #96 where there was utter garbage in the buffer in two batches - then back to normal operation:
FWIW - the lps_test ran overnight - Serial send seems fast and clean to uninterrupted PC
Was still running at ~210 lps since fresh restart - it is now in the ~170 range with firefox/sublime text open and active.
These errors are all to be expected and recorded:
Code:
> _____MISSED lines____ #2 {cpl=34} count=100000001, lines/sec=214334
#3 was dos box Buffer copy
#4 not in new buffer - safe to assume it showed new digit : #4 {cpl=35} count=1000000001
[B]> _____MISSED lines____ #5 {cpl=36} count=1, lines/sec=205467 [/B]// count=10 in same buffer
[B]> _____MISSED lines____ #6 {cpl=28} count=101, lines/sec=205467
> _____MISSED lines____ #7 {cpl=29} count=1001, lines/sec=205467
> _____MISSED lines____ #8 {cpl=30} count=10001, lines/sec=205467
> _____MISSED lines____ #9 {cpl=31} count=100001, lines/sec=205467
> _____MISSED lines____ #10 {cpl=32} count=1000001, lines/sec=234264
> _____MISSED lines____ #11 {cpl=33} count=10000001, lines/sec=216293
> _____MISSED lines____ #12 {cpl=34} count=100000001, lines/sec=207797
[/B]#13 not shown happened when I copied the dos box buffer
Code:
#33616971[4K] : __>> count=3864923157, lines/sec=197043 << >4> Good lines=____114
#33617850[4K] : __>> count=3865023168, lines/sec=209016 << >4> Good lines=____114
// ...
#41328017[4K] : __>> count=463256201, lines/sec=217812 << >12> Good lines=117____
#41328872[4K] : __>> count=463356261, lines/sec=217812 << >12> Good lines=117____
#41329726[4K] : __>> count=463456203, lines/sec=218953 << >12> Good lines=117____<update> :
>> multitasking OS seems to be more lossy than Teensy T4 at these rates - but that may just be because T4 is not supporting the 'availableForWrite()' to halt transmission when client gets busy:
> opened EDGE browser and that caused data glitch again - I have 7 EDGE windows open with a combined 38 web pages in tabs
> And opening each EDGE window to count the open tabs caused 3 data glitches with no apparent reason
> came back and the lps_test.exe had exited with NO ERROR - not sure if I did that? - then just reran it and it picked up on a buffer boundary with no T4 restart and no reported data glitch on starting.
Code:
#50115385[4K] : __>> count=1478669116, lines/sec=195738 << >15> Good lines=____114
#50116264[4K] : __>> count=1478769127, lines/sec=194467 << >15> Good lines=____114Got a BARRAGE of FAILS on PC in use … went from #15 errors to #96 where there was utter garbage in the buffer in two batches - then back to normal operation:
Last edited:
