Hi, 0.4.9 is generally FAR better than its predecessors, faster and more stable. I am however still experiencing UDP failure - which are NOT being fixed by a re-initialisation of my UDP. My code sends UDP packets out (approx every 10 seconds at the moment), and I am using Serial1 as a debug port …

Sorry forgot to say that everything else seems to be working just fine. Cloud is UP, publishes happening on a regular basis etc. I have a built-in reboot command I can send and that works perfectly well, reboots and the UDP issue ‘goes away’ again for quite some time (sometimes many hours, sometimes…

Hi @GrahamS Have you checked your router logs for something that is logged around the same time as the failure? There are many potential failure points here that you can investigate. It could be something simple like your Photon does not have its IP address after a DHCP hiccup. Have you tried incr…

Hi @bko As mentioned in my second post - everything else is running just fine. The cloud is connected (I can read variables, send commands, and it is ‘publishing’ my data whilst UDP is reporting errors. So yes - I am confident that this is not a network issue. It also happens on two distinctly di…

Does anyone know where are the error codes are defined? I thought someone posting a list before Christmas but despite searching I cannot find the post, or the list of them. I’m running my Core on 0.4.7 at the moment and actually trying to get it to fail so that I can test how my code recovers from i…

I found the post. It's here. [image] Udp error codes listed anywhere? Troubleshooting Hi, Well no response and I trawled the source code and can only find an undocumented reference to a WICED code 26 meaning INVALID_SOCKET. Anyway - I resolved the problem by reviewing my…

The response codes are not the same between the core and the photon since they are defined by the network stack, which is different on each device.

Hi @timx , Glad you found the codes and my earlier posts on this issue ;-). -26 is the only error code I have (yet) seen from my UDP socket. It was present in 0.4.7 and seems to still be there in 0.4.9. As mentioned, mine fails after some hours - of two operational systems, both rebooted yesterday …

Hi, Well two systems now been running for a while with the new code - which 'delete[]'s then 'new’s the UDP if it fails. Seems to be more stable so far…Pity I am only monitoring the serial port and not actually logging, as I would expect to miss any UDP fail events :-(. On another (might be relate…

This sounds like something I’ll need to be able to do in the future so I’ll try to set up a test rig this weekend and then a little longer to gather data; hopefully I’ll find something useful for solving the problem.

Hi, Further feedback… ‘Touch wood’ these two systems are now WAY more stable, been running since 19th with code which deletes the UDP object on a fail code and creates a new one… A single static object really ‘should’ be re-usable but hey ho… Hope this is useful to someone out there ;-)) Graham …

UDP problem 0.4.9

Troubleshooting

timx February 18, 2016, 11:30pm 6

I found the post. It's here.

Topic		Replies	Views
UDP issues and workarounds Troubleshooting	29	15016	September 2, 2015
Strange UDP bug	32	6661	March 10, 2014
Cyan flashing and other issues Firmware	12	3927	January 18, 2016
TCP or UDP issues consolidation Troubleshooting	43	7549	June 14, 2015
Sending UDP multicast fails after several hours Firmware	12	3777	February 16, 2016

UDP problem 0.4.9

Related topics