I’m finding that when using the UDP library, if I send messages continuously, say, once a second in the main loop, it sends them almost indefinitely (until the core restarts, flashes green, flashes cyan etc…). But if I instead attach the send function to a button press, and do it now, and in a minute from now, the messages no longer send, and wont until I reboot the core. The LED is still breathing cyan, and the D7 led flashes to indicate my sending function is executing, but nothing comes over the network.
If this is related to the CFOD then it can be ignored, but if not, is the team aware of this?
I’ll be honest, I’m pretty disappointed after spending $400+ on 10 cores and find that they are totally unreliable/unusable. I know the team and others are working on the CFOD bug, and I appreciate everyones effort, but I would’ve hoped finding a fix for such a critical bug would have been given more priority by the spark team. A $100 credit note is a bit on the cheap side as a bounty to fix basic functionality of your only product.
I know I’m probably coming across as impatient, but I’ve been experiencing this bug for over 6 weeks now, constantly, and combined with the money i’ve spent on these, compared to the value spark is putting on fixing it (about an hours wages for a developer?) I’m kind of feeling a little bit screwed over.