- Netduino Forums
- → Viewing Profile: Topics: MaYHeM
The Netduino forums have been replaced by new forums at community.wildernesslabs.co.
This site has been preserved for archival purposes only
and the ability to make new accounts or posts has been turned off.
Community Stats
- Group Members
- Active Posts 8
- Profile Views 4080
- Member Title New Member
- Age Age Unknown
- Birthday Birthday Unknown
-
Gender
Not Telling
0
Neutral
User Tools
Friends
MaYHeM hasn't added any friends yet.
Topics I've Started
DPWS Substitute
07 November 2012 - 01:54 PM
Ultimately, I wish to have two Netduino Plus that communicate to each other with Streams over Sockets and both also communicate with a Desktop application in the same manner.
What I'm struggling with is discovery. I would like the Netdiunos and the Desktop app to be able to find each other on the network without manual configuration of IP addresses at runtime.
Any suggestion on how I could achieve that?
Out of Memory - Debug.GC(true) says I'm not?!
22 October 2012 - 10:18 PM
I'm having a problem, where in the Netduino begins first with failed allocations, culminating to out of memory exceptions.
However, I'm checking Debug.GC(true) before each request/response and it reports between 14k-7k.
The Netduino accepts a socket connection and parses the request.
The request contains arguments of duration and recurrence.
psuedo code
With each toggle of the LED, the Netduino connects to a socket and sends a small string indicating the LED status has changed.
After a short interval of toggling the LED and sending the status, the Netduino begins to run out of memory. It is however reporting that it still has memory to work with.
Any ideas?
1.) Why is it running out of memory
2.) Why does it report runtime memory remains yet throws out of memory exceptions
However, I'm checking Debug.GC(true) before each request/response and it reports between 14k-7k.
The Netduino accepts a socket connection and parses the request.
The request contains arguments of duration and recurrence.
psuedo code
int x = 0 loop { LED ON Sleep [duration] LED OFF Sleep [duration] }while x < recurrence
With each toggle of the LED, the Netduino connects to a socket and sends a small string indicating the LED status has changed.
After a short interval of toggling the LED and sending the status, the Netduino begins to run out of memory. It is however reporting that it still has memory to work with.
Any ideas?
1.) Why is it running out of memory
2.) Why does it report runtime memory remains yet throws out of memory exceptions
- Netduino Forums
- → Viewing Profile: Topics: MaYHeM
- Privacy Policy