What is the IP address of your router? I remember I couldn't see my blade and it's because the IP of the router has to be set to 192.168.1.1
He already tried back-to-back (see above). Didn't work...
Topic: [Guide] Dogie's Comprehensive ASICMiner Blade Setup - page 62. (Read 580761 times)
He already tried back-to-back (see above). Didn't work...
I do what you suggest, there is no echo replies after plug cable to the blade. 
I wrote to the friedcat few hours ago, still waiting for his reply.
For what reasons are other pins for example 1-2 ?
I wrote to the friedcat few hours ago, still waiting for his reply.
For what reasons are other pins for example 1-2 ?
What is the IP address of your router? I remember I couldn't see my blade and it's because the IP of the router has to be set to 192.168.1.1
For what reasons are other pins for example 1-2 ?
I am away from my Blade at the moment but if I remember well, there was a DEBUG connector on the Ethernet board. If it is two pins (I think it is), it is probably an I2C interface. But this is not something you may easily work with unless you are in a lab with HW dev equipment.
EDIT: It's actually 3 pins, GND, Tx, Rx. It might just a well be a serial interface (console?). If you have any RS-232 port at hand, maybe you could attach a terminal, and get the settings from friedcat (or just try 8N1 at 2400, 9600 or 19200 bps? best guess...). At any rate, if I were you, I would (be pissed off but anyway) wait for an answer from him.
I do what you suggest, there is no echo replies after plug cable to the blade.
I wrote to the friedcat few hours ago, still waiting for his reply.
For what reasons are other pins for example 1-2 ?
I wrote to the friedcat few hours ago, still waiting for his reply.
For what reasons are other pins for example 1-2 ?
I would suggest configuring 2 network nodes (e.g. computers) with static IP configs.
One would be for example 192.168.1.200 (netmask /24), the other one 192.168.1.254, same netmask.
Then you link them back-to-back (supposing modern HW with auto-sense)
Make sure you reset your blade to factory settings by shortcutting the reset pins (doc).
Start a ping probe from .200 to .254. While you are getting the echo replies, unplug the Ethernet cable from the node on .254, then plug it into the Blade. If you don't see any echo reply, your Ethernet module is likely to suffer a hardware failure.
If that's the case, I feel for you dude
Hopefully friedcat will try to compensate you in a way.
One would be for example 192.168.1.200 (netmask /24), the other one 192.168.1.254, same netmask.
Then you link them back-to-back (supposing modern HW with auto-sense)
Make sure you reset your blade to factory settings by shortcutting the reset pins (doc).
Start a ping probe from .200 to .254. While you are getting the echo replies, unplug the Ethernet cable from the node on .254, then plug it into the Blade. If you don't see any echo reply, your Ethernet module is likely to suffer a hardware failure.
If that's the case, I feel for you dude
Hopefully friedcat will try to compensate you in a way.
Yes , I have green led on the network card and the orange led.
are you getting the green flashing led on the network card on power up?
Anyone has a good idea what to do ? Is it possible to reset blade in other way ? I change my power adapter and still not working.
Yes, I try to connect to the 192.168.1.254:8000.
I turned it off for an 8 hours - it hurts.
I tried reset it and it doesn't work.
I tried reset it and it doesn't work.
Remember when you reset it it will go back to .254
I turned it off for an 8 hours - it hurts.
I tried reset it and it doesn't work.
I tried reset it and it doesn't work.
You've turned it off for an hour to let it cool down and tried again? Worth a try.
If it was working yesterday and you've not touched it, could well be hardware problem. Seems like an odd part to break though, the ethernet controller wouldn't be my first guess as to something which would overheat.
You could try the hardware reset, check the instructions, you have to bridge two pins briefly, and then it should reset to the default IP address I think.
If it was working yesterday and you've not touched it, could well be hardware problem. Seems like an odd part to break though, the ethernet controller wouldn't be my first guess as to something which would overheat.
You could try the hardware reset, check the instructions, you have to bridge two pins briefly, and then it should reset to the default IP address I think.
Yes I tried to ping my blade and there is no answer.
I don't have acces to the config, I have an activity on my network, I send via lan packages but don't received any.
I feel heat behind the power controler.
Everything worked fine till yesterday.
I don't have acces to the config, I have an activity on my network, I send via lan packages but don't received any.
I feel heat behind the power controler.
Everything worked fine till yesterday.
Atm my computer doesn't see a blade,
What do you mean exactly? You try to ping your Blade and no answer? Or the web interface on port 8000 is down?
packages are sent to the blade but don't turn back.
So it means you can access the web interface and see the "Received" counter increasing, but not the "Accepted" counter? Or does that just mean you see network activity on the Ethernet (they could be broadcasts, ARP who-has/is-at etc)?
Blade start as green light is turn on and the ethernet controler has green and orange light. Any1 can help me ?
Can you feel heat on the heatsink under the fans when your Blade is on?
I have problem , my blade worked for 2-4 days. Atm my computer doesn't see a blade, packages are sent to the blade but don't turn back. Blade start as green light is turn on and the ethernet controler has green and orange light. Any1 can help me ?
I Pmed John and friedcat.
I Pmed John and friedcat.
I'm scared to change the Low clock to High clock...
Look at your blade every day for about a week, when you get used to having it there, switch the clock to high and run really, really fast out the door about 100 meters out. If you don't hear a loud pop in 24 hours it will be safe to return ...
:/ I set it to high within 30 minutes of checking the cable temps. All its doing is changing to the faster oscillator and drawing ~20W more.
Thanks for the answer. I clicked the button, and no *boom* ;-) Just some more heat, but I still can touch the heatsink without my fingers getting burned, and about 2 more GH/s. I don't have a watt-meter on that plug yet so I can't check but I trust you on the +20W.
Thanks dogie for the tips on the fans direction too. Crossing fingers to see the difficulty staying below 20M within 60 days and we should be good
yep, same here, let's hope that the investment would be worth it...
I'm scared to change the Low clock to High clock...
Look at your blade every day for about a week, when you get used to having it there, switch the clock to high and run really, really fast out the door about 100 meters out. If you don't hear a loud pop in 24 hours it will be safe to return ...
:/ I set it to high within 30 minutes of checking the cable temps. All its doing is changing to the faster oscillator and drawing ~20W more.
Thanks for the answer. I clicked the button, and no *boom* ;-) Just some more heat, but I still can touch the heatsink without my fingers getting burned, and about 2 more GH/s. I don't have a watt-meter on that plug yet so I can't check but I trust you on the +20W.
Thanks dogie for the tips on the fans direction too. Crossing fingers to see the difficulty staying below 20M within 60 days and we should be good
I noticed some weird behaviour today with my blade. I am running stratum proxy on bitparking to feed my blade. Today the pool went down and my gpu miners running cgminer switched to its backup pool, where the blade just stayed on the proxy with 0mhs and resetting every 2 minutes. It does have a backup pool set up and the switch server button makes the blade work fine on the second pool, but this did not happen automatically.
Anyone know how this can be fixed? It seems like whatever algorithm cgminer uses to switch pools is better than what the blade has built in. Is there any way to update the firmware or any of the parameters?
This is what stratum proxy is showing while the blade is trying to get work:
Anyone know how this can be fixed? It seems like whatever algorithm cgminer uses to switch pools is better than what the blade has built in. Is there any way to update the firmware or any of the parameters?
This is what stratum proxy is showing while the blade is trying to get work:
Quote
Unhandled error in Deferred:
Unhandled Error
Traceback (most recent call last):
File "twisted\web\server.pyo", line 156, in process
File "twisted\web\server.pyo", line 191, in render
File "twisted\web\resource.pyo", line 216, in render
File "mining_libs\getwork_listener.pyo", line 163, in render_POST
--- ---
File "twisted\internet\defer.pyo", line 134, in maybeDeferred
File "mining_libs\worker_registry.pyo", line 37, in authorize
File "stratum\socket_transport.pyo", line 93, in rpc
stratum.custom_exceptions.TransportException: Not connected
2013-05-24 20:32:51,382 ERROR proxy # Connection to upstream pool timed out
Unhandled Error
Traceback (most recent call last):
File "twisted\web\server.pyo", line 156, in process
File "twisted\web\server.pyo", line 191, in render
File "twisted\web\resource.pyo", line 216, in render
File "mining_libs\getwork_listener.pyo", line 163, in render_POST
---
File "twisted\internet\defer.pyo", line 134, in maybeDeferred
File "mining_libs\worker_registry.pyo", line 37, in authorize
File "stratum\socket_transport.pyo", line 93, in rpc
stratum.custom_exceptions.TransportException: Not connected
2013-05-24 20:32:51,382 ERROR proxy # Connection to upstream pool timed out
Saw this the other day too, do you have more than one blade? I have a more than one and I had to put them on one worker each on BTCguild and I was able to get it going.
I'm scared to change the Low clock to High clock...
Look at your blade every day for about a week, when you get used to having it there, switch the clock to high and run really, really fast out the door about 100 meters out. If you don't hear a loud pop in 24 hours it will be safe to return ...
:/ I set it to high within 30 minutes of checking the cable temps. All its doing is changing to the faster oscillator and drawing ~20W more.
I'm scared to change the Low clock to High clock...
Look at your blade every day for about a week, when you get used to having it there, switch the clock to high and run really, really fast out the door about 100 meters out. If you don't hear a loud pop in 24 hours it will be safe to return ...
Jump to: