Hi DrJaymz,

1. Install the .NET MF 4.2 QFE2 SDK
2. Install the Netduino 4.2 SDK (latest version)
3. Upgrade your board to the latest Netduino firmware

Please let me know how it works for you,

Chris

Done.

It will not deploy now. Whatever I try to do.

Incrementally deploying assemblies to device
Deploying assemblies for a total size of 1456 bytes
Assemblies successfully deployed to device.

You'd think its deployed then? No. The error comes up:

Error 1 Device not found or cannot be opened - USB:Netduino

Using MFDeploy I can get

HalSystemInfo.halVersion: 4.2.0.0
HalSystemInfo.halVendorInfo: Netduino Plus (v4.2.0.1) by Secret Labs LLC
HalSystemInfo.oemCode: 34
HalSystemInfo.modelCode: 177
HalSystemInfo.skuCode: 4097
HalSystemInfo.moduleSerialNumber: 00000000000000000000000000000000
HalSystemInfo.systemSerialNumber: 0000000000000000
ClrInfo.clrVersion: 4.2.0.0
ClrInfo.clrVendorInfo: Netduino Plus (v4.2.0.1) by Secret Labs LLC
ClrInfo.targetFrameworkVersion: 4.2.0.0
SolutionReleaseInfo.solutionVersion: 4.2.0.0
SolutionReleaseInfo.solutionVendorInfo: Netduino Plus (v4.2.0.1) by Secret Labs LLC
SoftwareVersion.BuildDate: Sep 19 2012
SoftwareVersion.CompilerVersion: 410894
FloatingPoint: True
SourceLevelDebugging: True
ThreadCreateEx: True
LCD.Width: 0
LCD.Height: 0
LCD.BitsPerPixel: 0
AppDomains: True
ExceptionFilters: True
IncrementalDeployment: True
SoftReboot: True
Profiling: False
ProfilingAllocations: False
ProfilingCalls: False
IsUnknown: False

So presumably the device is working. The output is set to deploy to netduino over USB.

So surprised it still can't really be used seriously.

OK, trying now, BRB

Hi DrJaymz,


Can you please try two things really quickly?

1. Open up your project properties and go to the ".NET Micro Framework" tab. Change transport from USB to Serial. Then change it back to USB. Try to run your app again.
2. If that doesn't work, please try switching back to the MFUSB drivers.

If all that fails, there are two final options:
1. If you're running Visual Studio 2012 (or would like to try Visual Studio Express for Windows Desktop), upgrade to the .NET MF 4.3 beta SDK. It has dramatically better diagnostics when deploying and it supports .NET MF 4.2 boards as usual.
2. Reflash your Netduino with the production 4.1 firmware. That's really a last resort, but if Visual Studio is failing to connect...it may b a bug which needs to be fixed in the NETMF 4.3 SDK.

Chris

P.S. If you're running inside a virtual machine, the standard WinUSB drivers may not be set up to handle that. Switching to the MFUSB drivers may be a solution there.

You could always argue that the netduino is a really big CPLD. I guess it depends on what you are trying to do and quite a lot can be implemented in software and I never cease to be amazed how ingenious some peoples solutions are. I guess most uses for the netduino are not concerned with outright speed but (in my case) out of lazyness. happy coding.

Try ToString("#.##")

ToString("F2")

??

Yes Thats the solution, thank you Dr Jaymz.

Yay.... I am so used to using String.Format that I really miss it, but obviously handling strings on a puny system like this is always going to be slow or memory intensive. I'm glad that F2 works for you and I don't know why I can't find it documented anywhere.

You don't need to be concerned with the debug statements, if no debugger is attached they do nothing. With no debugger attached watch out for much faster execution which may change how your program executes if you have not been careful with delays. I had been using I2C and effectively closed it immediately after sending a shut down, in debug this worked well, with no debugger it shut the port down before it had chance to send shut down!

I'm using a serial qVGA graphic display that draws about 200+mA, the Netduino can draw a couple of hundred as well, sooner or later I often wonder if my issues with stuck deployment and general shakeyness could be lack of power. Also my project behaves differently when running from a USB charger as opposed to connected to a PC. The timings appear to change on the UART which should be fixed surely or else it wouldn't work properly.

Hi DrJaymz,

Does this help?
http://forums.netdui...-5v-header-pin/

Well it states that the 5v regulator on board is good to 800mA we know that the controller uses about 250 so that leaves 550mA to stay in the current spec. So as long as the on board reg doesn't overheat we're good. The reg will shutdown in the event it gets too hot so it should be fine. perhaps my issues could be insufficient supply decoupling.

Yes, pretty sure that could be a power issue.



I would not be comfortable with a constant 800mA draw, even if its not shutting down, I don't like my board to be getting so warm. This could cause the board to get quite warm. I like to power via 5V rail with either a PC power supply, or a similar stand alone supply, and only use the on-board regulator for small projects.

It'll be fine, you worry too much, what could possibly go wrong....... (don't know why they worry at work when I say that)

Does anyone know what the PWM resolution is when using 4.2? (Latest)? I am using PWM at 10Khz and the minimum duty ratio I can get is 0.01. Which suggests that the PWM resolution is 100. The ARM has a resolution of 16bit which is a good deal higher than the 7 bits I seem to be getting. This means when controlling LED brightness it goes from off to about 20% perceived brightness in one jump which is a bit rubbish really. I'm using Microsoft.Spot.Hardware.PWM, am I doing something stupid? Would I get a better result by setting the period and the duration of the pulse? I would have though this had already been posted but I couldn't find anything.

Aha, that makes sense. Will try lower freq.

this works well now. My code was fine.

Does anyone know what the PWM resolution is when using 4.2? (Latest)?

I am using PWM at 10Khz and the minimum duty ratio I can get is 0.01. Which suggests that the PWM resolution is 100.

The ARM has a resolution of 16bit which is a good deal higher than the 7 bits I seem to be getting. This means when controlling LED brightness it goes from off to about 20% perceived brightness in one jump which is a bit rubbish really.

I'm using Microsoft.Spot.Hardware.PWM, am I doing something stupid? Would I get a better result by setting the period and the duration of the pulse?

I would have though this had already been posted but I couldn't find anything.

Really no-one know?

I just about finished my epic project, maybe I should read the book now eh?

As mysteriously as it stopped working, it started again. So, please ignore.

Yeah, it does that. A lot.

Well my master piece is almost finished. Its got pressure transducers, accelerometer, thermopiles and LCD touch screen. Its a piece of avionics. Its awesome. Now, I have accelerometer, thermopile and pressure on a single I2C with some low-pass filtering. This all runs on a thread. My routines for the display use the UART and they also run on their own thread. Then my main execution runs on the main thread. I have logging on yet another thread. And I'm currently using about 38kb of program space. I was wondering if there was any way to determine the CPU load - I mean all those threads have thread.sleep in them at some point and if there is a speed limit my code hasn't reached it limited mainly by the speed of the display and the I2C devices. I was thinking of sticking GPS for ground speed and heading information on the spare com port. This will require constant baby sitting of the NMEA sentences. The question is will the little netduino cope? How to tell?

I am using D4 and D5 with an twiddly knob (encoder). The common is connected to ground and the weak pullups are enabled. Thus when I the encoder connects D4 and Common I get a 0, and same for D5. I have built a state machine and configured it such that 4 - 1 represents a clockwise detent and 1 - 4 is anticlockwise. All good so far. I am using an interrupt on edge for both and when either is interrupted I check both and compare it with my state machine. The problem I am having is that I am not receiving all interrupts. The main weird thing is that it works better in one direction than the other. The speed of the interrupts is not very high perhaps 10 per second or so. If I disconnect my encoder and use push buttons I can see what happens. Holding down Button A first prevents Button B from generating an interrupt. B on its own generates an interrupt. Holding down B doesn't interfere with A. Its nothing to do with A not finishing the interrupt routine, everything ought to be symmetric. For now I have bodged it knowing that 3 - 1 is a clockwise rotation, though its not a valid set of states. I have added 10nF on D4 and D5 to ground, based on the premise that internal pull-up is about 100k, this should filter out glitches and still pass the fundamental that I want. Any ideas why the interrupts are not working as they should.