Ethernet and aggressive buffering reports error 22 or 33 and locks up

[Meliusja]

I was hoping the new teensyduino would fix my Ethernet problems but they seem to still be there. First off I am using Teensyduino 1.55 because I can't figure out how or where to download 1.54. I am running a version of grblhal from 12/5/2021 with the only build option changes from default being Ethernet and backlash comp enabled. It errors almost immediately in check mode on the attached file. My machine is 3 axis with speed 5000 and acc 500. I see Phil Barrett had a similar thread which was closed due to teensyduino 1.54. It runs to completion with aggressive buffering turned off. Any help will be greatly appreciated. I'm more than happy to provide anything else like setting files exact versions etc.

Update:
I found Teensyduino 1.54 and tried it but it does not help.

Thanks
Jeff Melius

1 FrameBack 6mm Flat 3F.zip

[phil-barrett]

With a build from July (20210715) and built with TD 1.54, I get several different errors running when connected via ethernet. I do not get those errors when connected via USB. The screens shots are with the XL version of IO sender but same error with ioSender 2.0.35. Also, when terminating ioSender, I get an exception (shown below). I do not get the error with ioSender 2.0.35. (will report on ioSender github repo. Jeff, if you don't mind, I will submit your gcode file with it as well).

[terjeio]

There is a bug somewhere when connecting via telnet, via websocket it works. The STM32F756 driver does not fail indicating this is a Teensy issue, perhaps in the network stack as the telnet code is exactly the same for both.

[Meliusja]

I just tried websockets and they work great and fast with buffering enabled. This solution works fine for me.
Thanks,
Jeff

[Meliusja]

Phil,
Feel free to attach Gcode to sender issue.
Jeff

[terjeio]

I have successfully made a workaround for this issue but I guess I have to dig deeper into lwIP programming since the other drivers do not show this problem. I will commit the fix soon.

Phil, when you have time can you change the links you have to the new repo - I am planning to archive this.

[terjeio]

Workaround now committet in the new repo.

[Meliusja]

I'm just curious, is the work around the change to slightly slow polling rate?
Thanks,
Jeff

[terjeio]

No, it is mainly about polling when data arrives. What is strange is that other drivers did not play well with this change.