You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality.

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.

Hi
Did anyone had luck with this new firmware and OneWire? I want to measure the temperature via the DS18B20 OneWire temperature sensor, but I really can't get the OneWire to run.
In the release notes it says "OneWire is provided through a community development effort." - What does that mean?

Hello out there!
I have an question to the differences between 4.1.0 (update 6) and 4.2.0 (update 2):
Are the DHCP- and Ethernet-cable-bugs also resolved ind the v4.2.0 or only in the older one?
I have my Netduino next to me and want to update it and have to choose what Version i should take. I think the extra RAM would be a really great thing, but if there are still the DHCP-Problems (I have to admit, the last time i worked With my netduino was 4 months ago...) i probalby would rather go for the 4.1.0
Thanks for your help!
Greets, Markus

If you need help with NeonMika.Webserver, please just leave a note in the thread and/or contact me via Skype

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------
--- Mistakes teach you important lessons. Every time you make one, you are one step closer to your goal. ----
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------

I just have a Netduino Plus (not 2)
So for firmware-update, could u give me a hint for which Version I should go? v4.2 or v4.1?

v4.1 says

With this firmware, you will have the following resources available for your
code:
64KB Flash
28KB+ RAM
This firmware includes the following
updates:
1. Enhanced Parallels, VMWare, and VirtualBox compatibility
2.
Garbage collection 'status messages' updated
3. Visual Studio debugger
should connect to Netduino easier during deployment (on non-virtual
machines)
4. Bugfixes: DHCP should now work properly on more/all routers
5. Bugfixes: Network cables can now be connected after board is powered up
6. Bugfixes: SerialPort.DataReceived event should now fire properly
7.
Bugfixes: SerialPort.Read() timeout now implemented properly
8. Bugfixes:
Misc. SPI bugfixes

and v4.2 says

With this firmware, you will have the following resources available for your
code:
64KB Flash
42KB+ RAM (50% more RAM than 4.1.0.6)
This
firmware includes the following update:
1. PWM bugfix (period/frequency now
set correctly)
This firmware also includes the following prior
updates:
1. 50% more RAM: 42KB (4.2.0.0) vs. 28KB (4.1.0.6)
2. Visual
Basic is now a supported language for .NET MF
3. New core AnalogInput and
PWM classes; backwards-compatible classes available via add-on assemblies.
4. New WinUSB drivers (to remedy BSOD issues in 4.2 beta)
5. Garbage
collector now fully collects old objects
6. See netmf.codeplex.com for full
details of all bugfixes

So my main question is: Does the v4.2 also contain the bugfixes of v4.1 like "Network cables can now be connected after board is powered up"? =)

If you need help with NeonMika.Webserver, please just leave a note in the thread and/or contact me via Skype

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------
--- Mistakes teach you important lessons. Every time you make one, you are one step closer to your goal. ----
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------

Hi Markus,
Generally speaking, v4.2 should include the bug fixes from v4.1.0.6.
We've found some additional bugs around network cable connection time in NETMF since then. We're hoping that the last one was squashed with NETMF 4.3 (via the upgraded lwIP network stack).
Chris

If you need help with NeonMika.Webserver, please just leave a note in the thread and/or contact me via Skype

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------
--- Mistakes teach you important lessons. Every time you make one, you are one step closer to your goal. ----
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------

Ok, so it seems I may have broken something.
After flashing my N+, I cannot connect to it with MFDeploy. It does not show up in the USB list.
Further investigation shows the root cause is that the USB driver is not correctly installed. When I look in device manager, it shows
Ports
AT91 USB to Serial Converter (COM32)
There is a warning icon on the device, and the status is "The device cannot start (Code 10)"
If I try to set the Driver to the one installed with the SDK (C:\Program Files (x86)\Secret Labs\Netduino SDK\Drivers) it says:
"The folder you specified doesn't contain a compatible driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
In the folder is the following:
amd64 [folder]
x86 [folder]
mfusb_netduino.cat
MFUSB_Netduino.cat
Please help.
Dave

I'm using this version in production environment. It's a pity I can't update clients's systems from remote do you know of a way to update a ND+ via serial from another ND+?

Depending on how happy MFDeployEngine is with the latency, you could switch a Netduino Plus's deployment port to one of the COM ports, tunnel TCP traffic to another Netduino Plus, and then send/receive that data via UART between the two boards.

Remote update is something we can work on with the new hardware, since we have extra flash and RAM.

Running Windows 8 and updating my Plus from 4.1 to 4.2. I managed to get through all the steps in about 15 minutes. Had MFDeploy showing me the new firmware. I was so happy with myself. I then went to deploy my program from VS to the netduino, and that's when the fun started. The deploy started and then was hanging. To make a long story (2 hours) short, I managed to get at least 75% of the errors in this thread as I went through debugging the problem. I'm finally able to deploy. A few hints... Rebooting my PC between device manager changes made a huge difference. Things that wouldn't work magically did after a reboot (obviously since this is Windows). And when unplugging the netduino and plugging it back in, I found i needed at least a 10s pause, otherwise it would show up as an unrecognized device. This led me to perform all sorts of unneeded steps. So throw in some reboots, and count to 10, slowly.