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.
Photo

.NETMF V4.2 OneWire Class fails to work


  • Please log in to reply
7 replies to this topic

#1 AlfaRomeo

AlfaRomeo

    New Member

  • Members
  • Pip
  • 6 posts

Posted 30 August 2012 - 12:57 PM

Hi, everyone I've installed the new v4.2.0 firmware and everything works fine, but the OneWire class. When I try to instanciate the Object it gives me this: "A first chance exception of type 'System.NotSupportedException' occurred in Microsoft.SPOT.Hardware.OneWire.dll" I'm doing a simple 1wire port interface to read an id only ibutton and i don't understand why this occurs???.. Some guys at tinyclr.com shows an example: http://www.tinyclr.c...m/topic?id=7297 and it seems that it's working fine for them... SO?.. I'd appreciate all your help on this!.. Best regards to all.

#2 nakchak

nakchak

    Advanced Member

  • Members
  • PipPipPip
  • 404 posts
  • LocationBristol, UK

Posted 30 August 2012 - 01:31 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.

#3 AlfaRomeo

AlfaRomeo

    New Member

  • Members
  • Pip
  • 6 posts

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 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 30 August 2012 - 03:31 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

#5 AlfaRomeo

AlfaRomeo

    New Member

  • Members
  • Pip
  • 6 posts

Posted 30 August 2012 - 04:27 PM

Hi chris,

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 AlfaRomeo

AlfaRomeo

    New Member

  • Members
  • Pip
  • 6 posts

Posted 01 September 2012 - 06:17 PM

Ok Folk´s... Now the DS2482-100 is working and reading ROM ID, but as I'm new with this platform, I don´t know how to represent an byte array in their components inside a String with hex pairs... anyone can help? Best regards for all,

#7 p47l4f0n

p47l4f0n

    New Member

  • Members
  • Pip
  • 3 posts

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 HeBeGB

HeBeGB

    New Member

  • Members
  • Pip
  • 1 posts

Posted 09 November 2012 - 07:23 PM

Hello, Just checking on the progress of One Wire support for plus V1... with 4.2 firmware. Thanks!




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

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.