NetBurner Community Forum

On bootup, RTCSetSystemFromRTCTime() is called to restore time from an external real-time clock, PFC8563. When queried for the current time, this function is used: //Formats 16 bytes time into "string" as 1999/12/31,23:59 void FormatDateTime( char *string, bool add_sec ) { time_t t; time( ...

I'm using v2.9.5 tools. I wouldn't think that would make a difference. The ticks per second has not been changed.
Not sure what is meant by the distinction of real-time clock vs system clock. It's the clock we get the date and time from.

We have several units using the NANO and the system clock gains about 5-minutes every 12-hours. Is there anything to be done?

The module was missing a gateway address because the module was configured for Static IP. I switched it back to DHCP, and now it's visible.
Thanks.

Using the discover.netburner.com webpage, I can normally find all modules that are using v3.x apps, regardless of the subnet. However, with one particular subnet I can't find anything, even when the PC is on the same subnet as the module. This is not a Netburner issue. I believe the subnet in questi...

Normally, when programming a NANO via the discover webpage, I would get a "Success" message when it completed. Lately, I am getting error message: "The server provided an invalid message! Content-Length: 0". However, the board programs successfully. I have tried both Firefox and ...

That would be a good test, but the configuration of the cable will not allow it. Because our product is an outdoor device, it has a waterproof circular cannon plug-type connector for the user interface. It contains RS-485, RS-232, and Ethernet. Our test cable splits off the signals for each interfac...

I'm using a NANO, and we built our own Ethernet 20ft test cable. Using the test cable we communicate fine over Ethernet, but the link & speed LEDs don't light up. If we use a normal store-bought Ethernet cable they do. I'm looking ideas on what to look for.

I found the error. I wasn't calling the correct accept function. It works now.

Today, I get a totally different response from attempting an openssl connection. It still doesn't connect. I rebooted and get the same response, printed below. I still had Friday's output in an open command window, so I took two screenshots to capture then entire output and put them in the attached ...