netmftoolbox Discussions Rss Feed

New Post: NMEAGPS library

ahmedfme — Wed, 24 Apr 2013 11:15:40 GMT

i have got skylab skm53 module and i try to connect to netduino plus 2 .
i connect Rx to d1 and Tx to d0 and 5v and gnd and then used your sample code .
but always i gor slatitude = 8960.0000,N
and slongitude = 00000.0000,E
saltitude = 137.0,M
and fix = false and sat=0
i have tried in home and outdoor and nothing change.
i appreciate any help

New Post: Hd44780 Issue

garrcomm — Mon, 03 Dec 2012 11:21:42 GMT

Sorry for the late reply, I rarely look at the discussions tab here ;)

What type of LCD did you use? I have another library I could recommend; http://microliquidcrystal.codeplex.com which may work?

New Post: Assembly link failure

MikeDent — Fri, 23 Nov 2012 06:23:53 GMT

That did it for me. No errors when downloading the assembly.

Thanks

Mike

New Post: Assembly link failure

garrcomm — Wed, 21 Nov 2012 19:22:00 GMT

Interesting. Just to be sure, I just recompiled all DLLs. Could you download the latest, and try it again please?

http://netmftoolbox.codeplex.com/SourceControl/changeset/view/20014

New Post: Assembly link failure

MikeDent — Fri, 16 Nov 2012 06:12:34 GMT

I'm having the same problem. I'm using a Netduino Plus, SDK 4.1 and Toolbox 19492. My code downloads until a add a ref to Toolbox.NETMF.

When I do that I see the following:

----------------------------------------------------------------------------------------------------------------------

Resolving.

Link failure: some assembly references cannot be resolved!!

Assembly: Toolbox.NETMF (0.1.0.0) needs assembly 'mscorlib' (4.2.0.0)

Assembly: Toolbox.NETMF (0.1.0.0) needs assembly 'Microsoft.SPOT.Hardware' (4.2.0.0)

Error: a3000000

Waiting for debug commands...

The program '[1] Micro Framework application: Managed' has exited with code 0 (0x0).

--------------------------------------------------------------------------------------------------------------------------------------

Any suggestions?

Thanks

Michael Dent

New Post: Assembly link failure

fileark — Sun, 11 Nov 2012 15:37:14 GMT

Thanks for the response. It was VB.net but I went ahead and built it in C# to check and it gave the same exact error.

The code is a sample I found online to use MultiI2C in the toolkit to run a 16 PWM board from adafruit.

Here is the offending class

/* 
* 
*      Adafruit 16 channel 12 bit PWM Servo Driver NETMF 
*      *      Code Translated by Brandon Watt Oct 2012 
*      *       * This board use I2C to communicate, 2 pins are required to  
*      * interface. For Netduino/Arduino Uno, thats SCL -> Analog 5, SDA -> Analog 4 
*      *  * Brandon Watt: Inital release (1.0) Translated arduino code into c# 
*      * Based on driver files found at "https://github.com/adafruit/Adafruit-PWM-Servo-Driver-Library" *
*      */
        
using System;
using Microsoft.SPOT;
using System.Threading;
using Toolbox.NETMF.Hardware;

namespace CsAdafruitPWM
{
    class Ada16PWM
    { 
    private MultiI2C _Device;
        private const byte PCS9685_SUBADR1 = 0x2;
        private const byte PCA9685_SUBADR2 = 0x3;
        private const byte PCA9685_SUBADR3 = 0x4;
        private const byte PCA9685_MODE1 = 0x0; 
        private const byte PCA9685_PRESCALE = 0xFE; 
        private const byte LED0_ON_L = 0x6;   
        private const byte LED0_ON_H = 0x7;     
        private const byte LED0_OFF_L = 0x8;   
        private const byte LED0_OFF_H = 0x9;      
        private const byte ALLLED_ON_L = 0xFA;   
        private const byte ALLLED_ON_H = 0xFB;      
        private const byte ALLLED_OFF_L = 0xFC;       
        private const byte ALLLED_OFF_H = 0xFD;       
        private byte _i2caddr;
        public Ada16PWM(byte addr = 0x40, int ClockRateKhz = 200)        
        {            
            _i2caddr = addr; 
            this._Device = new MultiI2C(_i2caddr, ClockRateKhz);
        }        
        public void Begin()        
        {            
            Reset();        
        }        
        public void Reset()       
        {           
            write8(PCA9685_MODE1, 0x0);        
        }        
        public void setPWMFreq(float freq)        
        {            
            float prescaleval = 25000000;            
            prescaleval /= 4096;           
            prescaleval /= freq;            
            prescaleval -= 1;           
            // Debug.Print("Estimated pre-scale: " + prescaleval);            
            byte prescale = (byte)System.Math.Floor(prescaleval + 0.5);           
            // Debug.Print("Final Pre-scale: " + prescale);            
            byte oldmode = read8(PCA9685_MODE1);            
            byte newmode = (byte)((oldmode & 0x7F) | 0x10); // sleep            
            write8(PCA9685_MODE1, newmode); // go to sleep            
            write8(PCA9685_PRESCALE, prescale); // set the prescaler           
            write8(PCA9685_MODE1, oldmode);            
            Thread.Sleep(5);            
            write8(PCA9685_MODE1, (byte)(oldmode | 0x80));       
        }        
        public void setPWM(byte num, UInt16 on, UInt16 off)       
        {          
            write8((byte)(LED0_ON_L + 4 * num), (byte)on);     
            write8((byte)(LED0_ON_H + 4 * num), (byte)(on >> 8));          
            write8((byte)(LED0_OFF_L + 4 * num), (byte)off);         
            write8((byte)(LED0_OFF_H + 4 * num), (byte)(off >> 8));      
        }        private byte read8(byte addr)      
        {            
            byte[] ReadBuffer = new byte[1];           
            this._Device.WriteRead(new byte[] { addr }, ReadBuffer);        
            return ReadBuffer[0];      
        }       
        private void write8(byte addr, byte d)       
        {           
            this._Device.Write(new byte[] { addr, d });        
        }    
    }
}

New Post: Assembly link failure

garrcomm — Sun, 11 Nov 2012 07:52:03 GMT

Hi there!

Quick question: are you using vb.net or c#?

New Post: Assembly link failure

fileark — Sat, 10 Nov 2012 21:07:22 GMT

I am getting the following error when trying to deploy to a Netduino:

--------------------------------

Resolving.

Link failure: some assembly references cannot be resolved!!

Assembly: Toolbox.NETMF.Hardware (1.0.0.0) needs assembly 'Microsoft.SPOT.Hardware.PWM' (4.2.0.1)

Assembly: Toolbox.NETMF.Hardware (1.0.0.0) needs assembly 'Toolbox.NETMF' (0.1.0.0)

---------------------

Here are the versions of my software:

.net micro framework SDK 4.2 (QFE2)

Netduino SDK 4.2.1 November 2012

I downloaded the toolbox yesterday.

I found Moicrosoft.Spot.Hardware.PWM 4.2.0.1, and added it to my project but it does not help

I don't know how to resolve the assembly issue where Toolbox.NETMF is the wrong version, they all came in the same package.

Any help would be appreciated as I have no idea how to proceed.

Thanks!

New Post: Hd44780 Issue

padesso — Mon, 01 Oct 2012 23:36:46 GMT

When I to run the Hd44780Lcd sample all I get is a blinking cursor at the first position.

I've tried with it with two different Netduinos running 4.1 and a Netduino+ running 4.2. I've also tried creating my own project and importing the projects/references and everything builds and deploys ok but no text is shown.

Triple checked the wiring as in the example.

New Post: event driven socket client

garrcomm — Mon, 17 Sep 2012 07:03:49 GMT

Hi Patrick,

The best approach for an event driven client would be using a background thread polling for data. I don't have a sample code for that, but maybe knowing this approach can help you find a neat solution?

New Post: event driven socket client

es000411 — Sat, 15 Sep 2012 15:59:02 GMT

Hi, I'm using your integrated socket class. Really a nice piece of software. I'm using it pretty straight forward but now I'm in the need of using an event driven client. Do you have an example or can you help me?

Thanks

Patrick

New Post: "Modulairity" of the wifly GSX driver

jamesjl — Wed, 12 Sep 2012 17:47:09 GMT

Guys, has anyone had any more thoughts on this discussion. Is there any move to adding socket server functionality (instead of just client) to this driver? Also, the link in the source to the Roving PDF appears broken (http://www.rovingnetworks.com/files/resources/WiFly-RN-UM-2.31-v-0.1r.pdf.) Can anyone get me the link to the correct file?

Edit: I found the link to the user manual. http://www.rovingnetworks.com/resources/download/93/WiFly_User_Manual

New Post: "Modulairity" of the wifly GSX driver

engramdesign — Thu, 23 Aug 2012 22:21:41 GMT

@garrcomm No worries, completely understand that you've got better stuff to do! :) That sounds good - I'll see if I can make a start on sorting that out!

New Post: "Modulairity" of the wifly GSX driver

garrcomm — Wed, 22 Aug 2012 09:04:46 GMT

Sorry, I haven't looked into this much recently due to some other stuff that's on my mind :)

To keep things small and compact (as supposted to with a micro framework imho), I think the easiest way will be making some protected hooks.
I think the best way to start, would be to make the CommandMode-methods protected. Also, add in a check to see if a socket connection is active (command mode shouldn't work in those cases).
I think most addons could be done with command mode.

I hope to have some free time soon, so I can work this out.

New Post: "Modulairity" of the wifly GSX driver

engramdesign — Mon, 20 Aug 2012 21:26:23 GMT

Just wondering if you need any assistance with getting this going? I'm happy to help out, if you've got a plan of action!

New Post: "Modulairity" of the wifly GSX driver

garrcomm — Wed, 18 Jul 2012 09:50:53 GMT

Thanks both, for replying.

I hope by the end of this month, or in the first week of August, I can work on this. I'm think the approach will be to make a few methods protected.

New Post: "Modulairity" of the wifly GSX driver

engramdesign — Wed, 18 Jul 2012 09:38:17 GMT

I think it'd be a great idea to implement some additional features for the driver. I certainly agree that the core driver should be as simple as possible to keep things slim.

For what it's worth, I've already extended and created some functions to add support for a few other useful commands for the module (scan for networks for instance). I'm happy to share with the project, but it's probably not that helpful just yet until some further direction is made on how is the best way to implement further functionality.

New Post: "Modulairity" of the wifly GSX driver

ahartman00 — Mon, 09 Jul 2012 14:56:21 GMT

Here are my ideas,

Creating an interface for the wifly, and having base classes for different behaviors. This would be kind of nice, you could do WiflyGsx wifly = new AutoConnectOnUartWifly, and have the constructor take in the additional parameters needed for this mode(using my auto connect on uart data mode as an example).

Or keeping the wifly class, and using the strategy pattern for sending requests. I am not as sure about this one, as some of the modes can be pretty different.

I would be kind of nervous 'un-privatizing' methods, although if we added checks to make sure you couldn't do anything stupid(checking which mode we are in for example).

New Post: "Modulairity" of the wifly GSX driver

Garrcomm — Mon, 09 Jul 2012 14:37:02 GMT

I received multiple feature requests for the wifly driver I created. I am grateful for the enthousiasm everyone shows in working with and extending my code. I also wish to implement as many features as possible, but with a micro framework, there's one big rule in my humble opinion: "Keep it small and simple".

Of course, this doesn't mean features can't be impelemented, but I would like to create a more modulair approach. I'm not sure yet how to do so, so I want to create a discussion about this.

My first idea would be making some private methods protected, so other files could communicate with the main class. I'm curious to other thoughs about this.