NetBurner Community Forum

Have the standard networking functions been removed from the 2.5.2 release?

I am getting errors in my code stating:

'connect' was not declared in this scope
'write' was not declared in this scope

All of the example appear to be using a BufferedTcpObject instead of the standard read/write calls, and there does not appear to be a way to send byte data using the BufferedTcpObject's Printf or Write - and there appears to be zero documentation recarding the BufferedTcpObject. Or, at least none was included with the development board we received...

Tough to answer unless we know what platform you are using.

No, the networking functions have not been removed from the 2.5.2 release.

I would suspect you're just missing the proper include directories or your Path variable got munged up and your netburner directory is no longer on it.

(I might elaborate slightly on rnixon's answer - some of the new boards like the SBL2E use a completely different TCP/IP Stack so you might need to refer to board specific documentation for those. )

Probably shouldn't have been that short. My guess was that he was using standard stack calls on the SBL2e platform, which is a totally different stack, and the processor doesn't have enough memory to buffer calls like connect, write, etc, so the buffered class is used instead.

I should have provided a bit more details, this is for use with the SBL2e.

Perhaps I'm missing some documentation. I have reviewed the PDF documentation and all files provided. After finding the include files I made some progress using the BufferedTcpObject, but would really prefer to read through the documentation to find out the limitations.

As mentioned, memory availability is a bit of a concern, so I'd like to understand the limitations better.

I have located the SBL2e Network Programming Guide on the NetBurner website, hopefully this will provide the information I'm looking for.

Thanks!

If you're not hemmed in by cost the SB-70LC gets you twice the flash and something like 250X the RAM for about double the money (at the board level). I'm not that familiar with this end of the NB family but just wanted to make sure you were aware of similar chips. I've only worked with the SBL2e once, and the 32K RAM was a serious limitation. (Says the guy who likes to use the C++ Library).

I just updated to 2.5.2 also, and I'm getting link errors on UDPPacket::GetDataSize(), which worked just fine before! This is with the PK-70, by the way.

What gives?

Thanks!

Abort, abort - My error!

I realized I didn't do a clean rebuild; when I did, the error went away. Must be senility setting in to make such a rookie mistake!

Please disregard my last post, and excuse the noise...