So I did, I changed in Make.c (in the firmware/heavy source folder) the following: // we're shooting for 192.168.0.200 int a3 = 5; int a4 = 200;
I've compiled that (the bin is in the output directory)
Then I connectd the make controller trough usb, the red LED is on (before resetting, and de-connecting), I start McHelper, I upload the new builded bin. Then, again, re-connecting the usb cable, the green LED flashes now.
I connect the ethernet cable (at that point, my wireless internet connection doesn't work anymore)
But nothing works now: (no led test, no web server test) -not when I set 192.168.5.200 or 192.168.0.200 as IP adress -not when I take these steps: '/network/address 192.168.5.200' '/network/gateway 192.168.5.1' '/network/valid 1' '/system/reset 1
Sometimes nothing happens, sometimes the command returns witch an ' > ' before it
So I changed the ip in de firmware to 192.168.5.200 I set the sleep time between the blinking to 99 (so when it blinks fast, I'm shure its the right firmware)
I setup my ethernetconnection with IP 192.168.5.210
Firmware uploading trough usb works fine, then reconnecting, connecting ethernet then, in McHelper, the IP is 192.168.5.200 (i've also tried 192.168.0.200) then the '/network/address 192.168.5.200'... steps But I don't get any feeback like 'osc > /network/address 192.168.5.200' can't ping 192.168.5.200, can't view webserver, cant turn the LED on .
I'm feeling that I'm forgetting something very stupid...
Hey SimonV - it looks like, from your message above, that you're trying to give your computer and the board the same IP address - 192.168.5.200. On your computer, you need to set some other IP address on the 192.168.5.xxx subnet...192.168.5.210, or whatever you like.
I might have misunderstood your "I set the Ethernet port to 192.168.5.200", but that's my best guess!
Yea, thats what I did the first time... thats indeed something wrong. But now I'm using ...5.210 for my ethernet and 5.200 for the controller, and it's still the same.(Well, in fact, my wireless connection keeps working now)
If you wireless router is 192.168.0.1 and its subnet mask is likely 255.255.255.0. This means that everthing attached to router should have an address like 192.168.0.xxx.
The controller should have an address like: network address: 192.168.0.200 netmask: 255.255.255.0 default gateway: 192.168.0.1
With the netmask set to 255.255.255.0 the controller says anything that matches the 192.168.0.xxx is on the local network. Any address that does not match 192.168.0.xxx is sent out the default gateway for routing by your IP router since it is not on the local network.
The netmask in hex is 0xFF - 0xFF - 0xFF - 0x00 which if you "AND" with 192.168.0.xxx keeps only 192.168.0.0.
Also - if you only changed the IP address in the firmware, that won't be enough for the board to communicate properly. You'll also need to change the subnet mask in the firmware to 192.168.5.1, just like you did on the PC side.
If you're able to connect to the board on your wireless interface on the 192.168.0.1 subnet, it's probably easier to issue those commands over OSC - but if you can't even get that to work, then the firmware is another strategy.
Heh? That's the case when I don't want to preserve my wireless connection right?
I connect the make controller to my mac, who is wireless connected to the internet (router) My wireless connection and my ethernet should be in a different subnet right? Wel isn't that the case when using ...5.210 and ...5.200 ?
Sorry for any confusion! To maintain your wireless connection, and communicate separately with the board on your wired interface, basically the steps should be as follows:
1. On the PC side, on your wired interface, change the subnet mask to 192.168.5.1, and give your computer an address in that subnet...something like 192.168.5.210.
2. On the Controller, change the subnet mask to 192.168.5.1, and set the address to another address in that subnet...something like 192.168.5.200.
Assuming you're able to make those changes successfully, you should be all set.
Hmm - I completely misspoke there. The subnet mask should be 255.255.255.0 in both cases, but rather the GATEWAY should be 192.168.0.1 for both. Sorry bout that!
Also try setting the gateway address to 192.168.5.127 and 192.168.5.128. I seem to remember that one of 127 or 128 extensions was common for the upper half of the address. Hmm I forget the technical term for the last block of of the IP#. Also, I believe you are correct with the 192.168.5 issue. I forget the details of how the addressing works (ie when it is sent and/or blocked), but I've always seen it having the same first three blocks the same. Anyway, that is something to give a quick try.
It's possible now to send OSC messages trough usb, and so I did. I can set te green leds to on/off, no problem with that.
But when I try these commands: '/network/address 192.168.5.200' '/network/gateway 192.168.5.1' '/network/valid 1' '/system/reset 1'
... the staus led stops blinking. Also when i just ask the network adrress, it stops blinking
When I connect the board with the ethernet cable, using the 192.168.0.210 address, I also can controll the leds, but nothing happens when I try to change the IP address by the osc comments mentioned above
I tried the above sequence just now and all works.
Please confirm that you're using the 1.0.3 firmware.
One thing that might be worth mentioning is that you will need to close MC Helper, power cycle the board, then re-open MC Helper before the USB system works again. USB under Windows is a little touchy and it does merit a little more care than we're currently giving it in MC Helper.
Im using the 1.03.01 right now, and the latest mchelper
I did the osc commands (via usb) to change the IP adress (led stops blinking after the first command) I've stopped mcHelper, I've unplugged the usb and plugged back in, I've started mcHelper Then I've tested if the network address is changed with the command: '/network/address' (via usb), I get the old ip back (...0.200) and again, the led stops blinking
Also, is the IP adress not automatic set to ...0.200 when power-cycling?