NetBurner Community Forum

Thanks Paul, It complies and links using gmtime_r() at 91.79% of flash with -O2 optimization and 88.98% with -Os. I also found that it worked with localtime(), but that would require some work-arounds for daylight savings time to get back to GMT from EST/EDT. Good point about thread-safe. That is a ...

Just for clarity, I am not using SSL/TLS.

Support ticket with map file sent.
It is definitely invoking cryptolib.a for the gmtime() function at line 327 in the map file:

C:\nburn\lib\cryptolib.a(wc_port.o)
Graph.o (gmtime)

On a MOD5270B using version 2.9.5 I have a small subroutine for extracting data from the bottom of a std::list. struct GraphData{ time_t time; std::vector <float> value;}; float Graph::GetLastValue(int index){ list<GraphData>::reverse_iterator D_it = plotData.rbegin(); lastSavedMonth = gmtime(&D...

The timer resolution is seconds as set in NBMQTTCountdown.h at lines 36 and 52 using ((TimeTick/TICKS_PER_SECOND) * 1000) to set startTime and time respectively. Seconds should be fine mostly since all the settable parameters are in seconds, except int Client::yield(unsigned long timeout_ms = 1000L)...

MOD5282 and MOD5270B, same on both, with NNDK 2.9.5

Playing with the mqtt-paho example, I found that it uses up 3 of the 4 HiResTimers. It acquires three timers and keeps two active, using them occasionally. The third one is released and re-acquired throughout the publish-subscribe cycle. The app I want to add mqtt to already uses two timers, so it c...

Well, tzsetchar((char*)"EST5EDT4,M3.2.0/01:00:00,M11.1.0/02:00:00") worked. I never thought to try it. I was expecting the putenv() method to continue to work. I guess it was the move to GCC 8.1 that killed it. All's good with Timezones now; just have to make the switch to tzset() in all m...

I am trying to migrate from 2.8.6/7 to 2.9.5 on a MOD5282. Setting the Timezone doesn't work anymore. This code putenv("TZ=EST5EDT,M3.2.0/2,M11.1.0/2"); Now_t = time(NULL); localtime_r(&Now_t,&Now_tm); localtime(&Now_t); cout << "Timezone: " << getenv("TZ") ...

I figured it out. There is a parameter at line 111 of MQTTClient.h with a default set: When I changed the default to 1000, it published my 450 byte message. There doesn't seem to be a more elegant way of changing that parameter.
Hope this helps someone.