Daxl-B

I agree with samjones, this looks like a pretty cool shield and exactly what I am looking for, rightnow I have the SM5100B and a separate RTC, my intention is to make my prototype a production system and this shield will fit great.

...(or if we get enough requests...we'd be happy to expose a managed class)...

Chris;

This will be great, I just got some RTC with the DS3234 since I want to use N+ in production environment and be sure that if something goes wrong it will be always reset to resume normal operation (assuming something more critical didn't happen). Right now I am using TCP to provide some in-the-field configuration and after that I do a soft reset, but some times the N+ hangs after the reset.

Is there an official request page? if no, just count me in.

BTW, 4.2 will do a great Thanks Giving present, no pressure just saying

thanks
Daxl

Hi;

Seems like you close and open the connection each time. What about this: Create a method to attempt connection, once the connection has been establish then just call a method to monitor and answer TCP commands. The follow example will attempt to connect to a TCP client (in your case labview) you can limit the amount of time in microseconds before continuing the execution in the main loop, this will allow the netduino to perform other tasks while waiting for a incoming TCP connection:

In the main() while loop just call this function, once it returns true you do not need call it again.

        private static Socket client;
        private static Socket server;

/// <summary>Waits for an incomming connection.</summary>
/// <param name="timeout">The amount of time in microseconds that the unit should wait for an incomming connection </param>
        public static bool Listen(int timeout)
        {
            // check if a client is available.
            if (server.Poll(timeout, SelectMode.SelectRead))
            {
                try
                {
                    // Connect with the client.
                    client = server.Accept();
                    // Get the buffer size.
                    _bufferSize = client.Available;
                    _rxData = new byte[_bufferSize];
                    _readByteCount = client.Receive(_rxData, _bufferSize, SocketFlags.None);

                    if (_readByteCount > 0)
                    {
                        IsOnline = true;
                    }
                }
                catch (Exception excp)
                {
                    IsOnline = false; 
                }
            }
            return IsOnline;
        }

After having a true condition (meaning a TCP connection was established) that just use:

// Get the buffer size.
                _bufferSize = client.Available;
                if (_bufferSize > 0)
                {
                      // Process your commands here
                }
}

Hope it helps.

Daxl

Wow! impressive, as I was reading your first post I was thinking: did I wrote this?, I have exactly the same idea and I came from the same C# for living background, my initial idea is to use old printers parts and I have several steppers but I have been thinking about using servos with encoders but no sure if a PID controller could be implemented on netduino. At this point I have been focus on implementing a general purpose protocol over TCP to keep communication between netduino and the PC still under development but I have been able to transfer 400kb in 1 minute (writing it to the SD) but I think faster transfers rates can be achieved if data only needs to be processed by netduino but no saved, if you some one is interested I can post code here when I got it complete.

Hi;

I am having the same problems that Aladdin updating the Netduino Plus. I have tried countless time to reflash it but it halt at "executing application" (I notice that the tutorial at http://wiki.netduino...ep-by-step.ashx presents the version 4.1 of MFDeploy.

- I have to use SAM-BA (no SAM-BA cdc) and select \usb\ARM0 as port instead of COM since I was not able to see a COM port. After that I go to MFDeploy and so far so good I can ping the netduino and get this response:
Pinging... TinyBooter
Bootloader build info: Netduino Plus (v4.2.0.0 RC3) by Secret Labs LLC

- Using MFDeploy 4.2: It "works" but after completing the update I am not able to ping the ECU or do something with it.
Response: Pinging... Error: No response from device

I am not able to go back to 4.1 since I have not located the tinybootdecompressor for version 4.1

Thanks
Dan