Thank you for explaining now i understand. Time to play with my netduino!

The fun is just begining
The next thing you want to do is check out the projects page.

My guess: CadSoft Eagle (?)

Yep, I use Cadsoft Eagle. But don't ask me for help with it. I am just returning to doing hardware after 40 years and am trying to catch up.I just kindof hack away with Eagle until something works.

I just got my netduino and I'm starting to try to get analog input and I always get 0 when I read my pin(A0). Do you see anything I did wrong?

My setup looks like this

3.3->AREF

A0->Photo Resistor->GND

public class Program
    {
        public static void Main()
        {
            // write your code here
            InterruptPort tester = new InterruptPort(Pins.GPIO_PIN_A0, false, Port.ResistorMode.Disabled, Port.InterruptMode.InterruptEdgeBoth);
            tester.Dispose();

            AnalogInput apin0 = new AnalogInput(Pins.GPIO_PIN_A0);
            apin0.SetRange(0, 100);

            int test = 0;
            while (true)
            {
                Thread.Sleep(250);
                test = apin0.Read();
                Debug.Print("Test: " + test);
            }

        }

    }

You would need another resister to 3.3Vdc to develop a voltage divider. There is no pull-up in the An-in.

I'm confused would it look like
AREF+3.3v->resistor(what resistance?)->ground?->photo resistor->A0?

First you need to know what the resistance of the photo resister is. Mine was 25k full dark.
Second you need to decide if you want it to pull-up or pull-down. I used mine in a pull-up.
Then choose a resitance to give you some kind of reasonable current limit, I chose 10K since I just wanted to play.
So using the attached schematic, I put the photoresister in a R1, a 10k in R2, you can try it either way and pick the one you like.

As soon as I get the all-clear from our users that the new AnalogInput code in the v4.1.0.2 firmware patch is working well for them... It tested out well here, but I'm being extra cautious before I post a tutorial.

The tutorial should work well with the original firmware as well (since the patch only addresses using multiple AnalogInputs at once).

Chris

The new version is working for me so far. I am using it with the SparkFun Joystick shield. http://www.sparkfun....oducts_id=9760. This is the one I was having problems with on Sat.
Thanks for the update!

The problem is that when a pwm period and duration are the same the output is high. Period is the rising edge to rising edge time of the output wave form. While duration is the length of the high time of the period. So period should be 1/frequency and duration should be (duty_cycle * period) where duty cycle is some value < 1. Also if I remember correctly, period is in microseconds so:

Try

  var period = (uint)(1000000 / frequency); 
  pwm.SetPulse(period, period/2); 
 

I used the same buzzer and I just checked my code and the period is in microseconds like I remembered.

Add the following Wiz5100 ethernet shield http://www.seeedstud...l?cPath=101_102 also available from http://www.nkcelectr...eeedstudio.html Like the latest Arduino Ethernet shield it requires an ISPC connection. Sorry about that, I found the schematic and it will work without the ISPC. There are three zero ohm resister used as jumpers that just have to be moved to convert from ISP to DI MOSI. Duh!

Not a shield but I need it so some one else may need one as well http://www.sparkfun....products_id=133, RS232 shifter. It converts from digital to RS232 sufficiently to work with a PC. Just don't forget to use 3.3 Vdc for VCC or you could spend a whole afternoon troubleshoot the hardware ( I wonder how he knew that? )

Well when it comes to prototype shields, there is not much that can go wrong, but thought I would add this one anyway. NKC Electronics has http://www.nkcelectr...hield-kit.html. The only caveat is that you don't want to install the 6-Pin ICSP pass thru. Itdoesn't work with the Netduino anyway since it's not populated

Use a PWM. You can then control the brightness by changing the duty cycle (duration). I would reference the articles in this forum but you can't search for PWM or LED because of the search rules

I have had some success using I2C and I have the data sheet for the MCP23017 here in front of me so I think you are doing things right. I will have to get my hands on one the the chips to be sure.

First, the address should be in the range of 0x20 - 0x27. With the way it is wired, assuming the drawing is correct, the address of the configuration should be 0x20.
It appears that you have this right, but let me explain for those who may not be aware. The I2C address as used by the I2CDevice.Configuration is the 7-bit address. With some other interfaces for I2C, it is common to list two addresses for a device, one write address and one read address. The two addresses differ only in the lsb, where an even number is the write address and an odd number is the read. In the case of those interfaces, the address would be 0x40 for Write and 0x41 for Read.
This gets more confusing since some datasheets list the addresses as the Read/Write address, for instance Newhaven displays and the Sparkfun MPR121 use this method. In those cases to use the device you will often see

new I2CDevice.Configuration(ADDR >> 1, 100);

Second, according to the data sheet, when using the I2C device the speeds are 100kHz, 400kHz and 1.7 MHz so that is correct.

Now for the final point. I will admit that at this time I am just a compitent C# programmer. But I generally avoid using "var" when I know the data type. So, I would avoid using:

var setIOCON = I2CDevice.CreateWriteTransaction(new byte[] { IOCON, 0x24 }); 

instead I would have used:

I2CDevice.I2CTransaction setIOCON = I2CDevice.CreateWriteTransaction(new byte[] { IOCON, 0x24 }); 

Other than that I will see what I can do about duplicating you hardware and see if I can find something else.

I got your latest code to work by adding a pull-up resister on ~RESET(pin18). Not too obvious in the description in table 1-1 "Hardware reset. Must be externally biased" I sort-of had it working without the pull up but it was not reliable. Once I put the resister in there, it became extreemly reliable. Sorry I didn't notice this before. And by the way, I had it working without any of the code changes I suggested. http://www.vimeo.com/20357391

Well after killing one of my Netduino's, I have managed to add listen, bind and accept to the experimental drivers. I think there is a disconnect between the implementation in the Wiz5100 chip and WinSock or Berkley Sockets. So based on my implementation you can only receive one connection request. Maybe someone can find where I am going wrong and post an update. I have changed the namespace so I could keep my changes separate from the original SecretLabs implementation. EDIT KLOTZ: Update the implementation of the bind/Listen/accept code based on some more reading. Also change the test code. Still does not reconnect.

Hi klotz!

I'm trying to get your test project to run, but I must be doing something wrong, because it never gets past this "do loop":

do
{
socketStatus = ReadRegister((UInt16)(socketBaseAddress + 0x0003));
} while (socketStatus != (byte)WiznetStatus.SOCK_ESTABLISHED);

It never returns:
WiznetStatus.SOCK_ESTABLISHED

Do you have any idea what can be wrong?

Thanks,

Ramon

I can't be sure without more details, so I appologize for asking the obvious question, 1) do you have the board connected to a 192.168.11.x network? 2) Have you posted a request from a client computer, "http://192.168.11.98"?
The code waits for a connections from the client, the loop you mentioned so is blocked.

updated the code. I found I was not doing the bind/listen/accept cycle correctly. Not sure I have it right yet, I still can't connect more than once. Hope someone could tell me where I am going wrong.

Probably not the way to do it, but I got it to accept multiple connects by moving these 2 lines of code inside the while(true) loop in the Main()

Socket listenSocket = new Socket(AddressFamily.InterNetwork, SocketType.Stream, ProtocolType.Tcp);
listenSocket.Bind(ep);

So the listening socket gets created and bound every time it finished a connection
No I can connect as many times to the Netduino as I want.

I would never have thought to do it that way. I am used to using sockets under WinSocks and you would not normally have to recreate the socket to get a new connection. It looks to me like it is not dropping the connection when I close the socket. Your solution causes the socket to be desposed and that may explain why it works.

Ramon,
While I'm unfamiliar with this particular code, I've seen that behavior before and in my case it was because my Ethernet Shield (NKC and authentic Arduino Ethernet Shield) require the 6 pin ICSP header. Both shields were stuck waiting until I solder the ICSP header on the Netduino. You might be running into the same issue.

That is a very good point. I did have a problem with my Seeeduino Ethernet board, it would not accept any of the commands. It turned out that I could do one of two things, add an ICSP connector to my Netduino or change some soldered jumpers on the board.
You may want to check to see if the enthernet board has jumpers. The best place to look would be on the schematic.

I fixed that error by updating PhysicalAddress initialization in the sample program with the MAC address printed on sticker on the back of my Ethernet Shield.
Replace the bytes in red with your actual MAC address.

networkInterface.PhysicalAddress = new byte[] { 0x01, 0x23, 0x45, 0x67, 0x89, 0x01 };

Good luck!

I have an Arduino Ethernet shield and there is no MAC address printed on it anywhere. Does the Wiz5100 have one "programmed" into it? If so how do I get it?

Yes the shield pings just fine. >ping 192.168.11.98 Pinging 192.168.11.98 with 32 bytes of data: Reply from 192.168.11.98: bytes=32 time<1ms TTL=128 Reply from 192.168.11.98: bytes=32 time<1ms TTL=128 Reply from 192.168.11.98: bytes=32 time<1ms TTL=128 Reply from 192.168.11.98: bytes=32 time<1ms TTL=128 Ping statistics for 192.168.11.98: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms I should add that I am using the original Arduino shield with no SD card.

I am having the same results. 10060 when running the wiznet test app from here. I am sure we are missing something basic but have no clue what it could be.

Looking at your error code again... DNS is not supported yet. We put that in the release notes next to the download link, but maybe we need to make that more obvious. Can you try connecting via direct IP and see if that works?

Chris

I had read that DNS was not working, but I thought that was the purpose of the proxy in the following segment from the Wiznet test posted in this forum.

            string url = "http://www.secretlabs.com/default.htm";
            // NOTE: since this experimental release does not support DNS yet, we must use the IP address of the web server as the proxy address.
            string proxy = "174.143.45.105"; // ip address of secretlabs.com

            // If the device must go through a proxy server, then set proxy to the 
            // fqdn or ip of the proxy server.
            try
            {
                String html = GetWebPage(proxy, url, 80);
                Debug.Print(html);
            }
            catch (SocketException se)

BTW I don't require a proxy server to access the net.

klotz,

Try the following MAC address; it's an official Secret Labs MAC address (and one we use for testing).
5C-86-4A-00-00-09

Chris

Thanks alot Chris, That was the ticket! It works now. When I get to work in the morning I will get a MAC address from my allocation.
Just out of curiosity, any idea why the default one in the test code would not work?

klotz--any interest in helping get uIP up and running on the Netduino Plus? I might be able to get you one of the lab units. We only have a few, but if you were serious about helping... pascal06 is leading the project.

Chris

Sure. I would be willing. I did want to get around to a Neduino plus when they start shipping again and if this is a way to make sure the network is up and running I'll do my part.
Just need some pointers to the code base and away we go

Ooh, we always love volunteers

Let's keep the Wiznet drives in C# for now, and then translate them to C++ later. They'll be faster as native code, but there are fewer "gotchas" and somewhat more portability if we create them in C#.

If you'd like a copy of the Wiznet communication spec, just PM me your e-mail address and I'll send over a copy. We could create a CodePlex project pretty easily.

All that said, finishing the Wiznet drivers will probably take about 5-10 more days of work. The easiest/fastest solution is probably to have us focus on fleshing out the implementation next week...and to have you and hari test and help resolve any bugs... Interested?

Chris

Chris add me to your list of volunteers. I have worked on a project were we implemented uIP on an HC12 using the enc... chip so I have some experience with networking in sockets. (though I will admit to being a newbie at C# I have extensive experience in C++). I just spent the last 2 hours getting bind and listen implemented and ran into a glitch on accept so I do want to help.

I think this is the proper close code

        internal void Close(int socketIndex)
        {
            UInt16 socketBaseAddress = (UInt16)(0x400 + (socketIndex * 0x100));

            // issue command to close the socket
            // socket n command register (Sn_CR)
            WriteRegister((UInt16)(socketBaseAddress + 0x0001), 0x10);
            while (ReadRegister((UInt16)(socketBaseAddress + 0x0001)) != 0) ; // wait to process the command
            lock (m_SocketsLock)
            {
                m_Sockets[socketIndex] = null;
            }
        }