Netduino home hardware projects downloads community

Jump to content


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.

Joshua

Member Since 12 Dec 2012
Offline Last Active Feb 02 2014 06:57 PM
-----

Posts I've Made

In Topic: Netduino Plus 2 Firmware v4.2.2 (update 2)

14 June 2013 - 12:57 AM

I noticed in this new firmware the soft reboot device capability is set to false.  Any way to change this?


In Topic: MG811 CO2 Sensor and Netduino Plus 2

15 January 2013 - 06:34 PM

Hi Joshua,

 

Have you succeeded ?

 

 

Rocca

I actually didn't end up using this because I needed more pins than I had on the Netduino so I utilized an Arduino and one of the Netduino's serial ports to get readings from multiple devices.


In Topic: NeonMika.Webserver

09 January 2013 - 07:11 PM

That will get the header for sure, but I think there will still be more data on the socket after the first receive because of the multipart.  I'm seeing all of the json being sent in firebug, so it's sitting somewhere ....just got to find it.

Maybe doing another receive from the socket after tempRequest is created.  I'm still seeing a difference between availableBytes and clientSocket.Available when tempRequest is being created.

Maybe.  Give it a shot.  Maybe when the client receives the ack, it sends the content?  If you look at the latest version of NeonMika from git, it has code to do this.. and I think that's one of the pieces of code I had used when I was testing it out.. it receives the header and then does another receive loop to get the rest of the content but it just locks up waiting to receive the amount of bytes up to the content length because it never gets them.


In Topic: NeonMika.Webserver

09 January 2013 - 06:59 PM

So I'm guessing that the tempRequest contains the header information, but we'd need to pull more data from clientSocket to get the actual json.  So maybe playing with the RequestReceivedEventArgs will help as it's still got access to the Socket, while tempRequest doesn't.

What i did was read the entire available bytes until the client stopped sending for more than 300ms and then printed the string it received.  All that was in the string was the header.. I did this right after the clientSocket.receive().. so I don't think its actually getting the json data in that request.


In Topic: NeonMika.Webserver

09 January 2013 - 06:40 PM

Thanks Josh, I'll give that a shot.

When you're hitting the 'save' button on the front end, do you see the json in the raw byte buffer? Or does that not come through?

it never comes through the raw byte buffer.. but if you inspect element in chrome.. it says it sent it.  It's odd.. kinda feels like were missing something in the rfc.


home    hardware    projects    downloads    community    where to buy    contact Copyright © 2016 Wilderness Labs Inc.  |  Legal   |   CC BY-SA
This webpage is licensed under a Creative Commons Attribution-ShareAlike License.