.NETMF V4.2 OneWire Class fails to work
#1
Posted 30 August 2012 - 12:57 PM
#2
Posted 30 August 2012 - 01:31 PM
Unfortunately there is not currently OneWire support for the 4.2 netduino firmware.
For the time being if you need one wire you have to use the 4.1 firmware with one wire support
Nak.
#3
Posted 30 August 2012 - 03:06 PM
Hi AlfaRomeo
Unfortunately there is not currently OneWire support for the 4.2 netduino firmware.
For the time being if you need one wire you have to use the 4.1 firmware with one wire support
Nak.
Hi, thanks for the soon reply!... According to chris walker, one of the ideas is to add OneWire Support with .NETMF v4.2...
but when you say that, i'm thinking that somehow there's no support. But why when you watch the MicroSoft.SPOT.Hardware there'e a dll called Onewire???...
Best regards,
#4
Posted 30 August 2012 - 03:31 PM
#5
Posted 30 August 2012 - 04:27 PM
Thanks a lot!.. I think that meanwhile I could try with the DS2482-100 from maxim (i2c interface master 1wire) to implement a class to handle this device. I hope can finish this today and if it works fine, I will share this code to everyone and get any comments and improvements..
AlfaRomeo.
Hi AlfaRomeo,
OneWire is a new feature of .NET Micro Framework 4.2, but it's a bit too big to fit in the current flash sectors.
We're currently evaluating a "special build" which would reduce the available code space a little bit, but which would add in the OneWire feature.
Chris
#6
Posted 01 September 2012 - 06:17 PM
#7
Posted 04 September 2012 - 10:46 PM
Hi AlfaRomeo,
OneWire is a new feature of .NET Micro Framework 4.2, but it's a bit too big to fit in the current flash sectors.
We're currently evaluating a "special build" which would reduce the available code space a little bit, but which would add in the OneWire feature.
Chris
I look forward for the onewire implementation too. It was a horrible surprise the NotSupportedException beeing thrown .
One remark: We use NotSupportedException to let the programmer know, that this functionality never ever will be implemented, or it does not give any logical sense to implement it. In cases, where it is already not finished, but it should be, we use NotImplementedException instead.
One question: Why didn't you suppose, the .net.mf will be extended in the future, so the additional code space will be needed? Isn't it a problem already in version 4.2 with insufficient code space? What are the options to solve the space problems?
Best regards.
#8
Posted 09 November 2012 - 07:23 PM
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users