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.

StefanUSMC

Member Since 12 Aug 2012
Offline Last Active Aug 11 2015 03:23 PM
-----

Topics I've Started

Maximum Sockets

28 July 2015 - 02:46 PM

Hello,

 

I have spent the better part of an hour attempting to find a straight answer on the maximum number of simultaneous sockets I can have open at one time. It seems that Netduino.IP will give me access to at least 7, but with my NP+2 I obviously do not have the option to use the new hybrid stack. Simply put, I have an application in which I need to run FTP client / server and Telnet client / server. I will never have more than either client or server for each protocol at a time, but I would like to avoid having to close my server listeners to run outgoing connections. Using the telnet side I am not worried, but when running FTP I will need 2 sockets at once with the client, and the server will consume 3 sockets during file transfer (Listener, Command, Data). 

 

Am I able to use 4-5 sockets at once? I found some older information that stated there was a max of 4, but one socket *may* be tied up for DNS. Is that accurate?

 

Also, is Netduino.IP going to be headed to the older ND+2? The 3 looks promising, but I have quite a few custom PCBs for NP+2 (and wireless is not an option, anyways).

 

Thanks in advance,

Brandon


Fails to reconnect debugger

16 July 2015 - 08:46 PM

Hello,

 

I am having a heck of a time getting consistent communication with my N+2 in VS2012. I have installed the new SL drivers, installed the VS plugin, NETMF 4.3 QFE2, most recent secretlabs SDK, and flashed my ND countless times. I have even ordered a brand new board, just in case there was something wrong with the hardware. I get all sorts of issues when attempting to debug (like even communicating with the ND at all), but very consistently I am wrestling with issues after assemblies are deployed, while attempting to reattach the debugger. I am fairly certain my code is not the issue, as occasionally it will deploy and properly debug. I have used new USB cables, and attempted in USB 2.0 & 3.0 ports. I have even go so far as to remove all portions of NETMF and secretlabs software and start fresh. This seems to be a new issue for me with the rollout of 4.3.2. I am running up against a deadline with this project, and spending the better part of a week connecting my ND was not an anticipated delay. Hopefully someone else has had this same issue, and can point me in the right direction. I should note that I never seem to have an issue communicating with MFDeploy, only when attempting to debug in VS.

 

Output in VS

 

Querying device assemblies...
Found Assembly mscorlib 4.3.1.0
Found Assembly Microsoft.SPOT.Native 4.3.1.0
Found Assembly Microsoft.SPOT.Hardware 4.3.1.0
Found Assembly Microsoft.SPOT.Net 4.3.1.0
Found Assembly System 4.3.1.0
Found Assembly Microsoft.SPOT.Hardware.SerialPort 4.3.1.0
Found Assembly Microsoft.SPOT.IO 4.3.1.0
Found Assembly System.IO 4.3.1.0
Found Assembly Microsoft.SPOT.Hardware.PWM 4.3.1.0
Found Assembly Microsoft.SPOT.Hardware.Usb 4.3.1.0
Found Assembly SecretLabs.NETMF.Diagnostics 4.3.1.0
Found Assembly SecretLabs.NETMF.Hardware.Netduino 4.3.1.0
Found Assembly Microsoft.SPOT.Hardware.OneWire 4.3.1.0
Found Assembly Microsoft.SPOT.Time 4.3.1.0
Found Assembly SecretLabs.NETMF.Hardware.NetduinoPlus 4.3.1.0
Found Assembly SecretLabs.NETMF.Hardware 4.3.1.0
Found Assembly RC_CSI_KS01_0_1_0 1.0.0.0
Adding pe file C:\Program Files (x86)\Secret Labs\Netduino SDK\Assemblies\v4.3\le\secretlabs.netmf.hardware.netduinoplus.pe to deployment bundle
Adding pe file C:\Program Files (x86)\Secret Labs\Netduino SDK\Assemblies\v4.3\le\secretlabs.netmf.hardware.pe to deployment bundle
Adding pe file XXXXXX\RC_CSI_KS01_0_1_0.pe to deployment bundle
Attempting deployment...
Incrementally deploying assemblies to device
Deploying assemblies for a total size of 15652 bytes
Assemblies successfully deployed to device.
Restarting interpreter...
Attaching to device...
Deployment error: failed to (re)connect debugger engine to debugging target.
The debugging target and the debugger engine failed to initialize because of unspecified device errors.
The debugger engine thread has terminated unexpectedly with error 'Debugger engine could not attach to debugging target.'.
 
 
 
Thanks,
Brandon
 

Looking for 4.3.0 SDK

20 January 2015 - 01:09 AM

Hello,

 

Some time ago I developed a project using N+2 controllers on a custom PCB. Units are used to relay data between a RS232 device and TCP/IP. I developed on 4.3.0, and even with the issues on the beta firmware none had an affect on my specific needs. I just had to replace a few units due to physical abuse, and set them up with 4.3.1. I am now having a horrendous timing issue with the bi-directional RS232 (Multiple "messages" get strung together, whole or in pieces). In an attempt to pinpoint if the issue is on the N+2 or my other device, I need to put the original working and tested firmware on the new boards. Is there any place I can get a hold of the 4.3.0 SDK? The link that used to point to those libraries now downloads 4.3.1. 

 

Thank you in advance!


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.