The footprint is actually listed as R1206. I believe those are part of the 12v circuitry on the board, so it could be from a surge of some sort I suppose. I've seen another report of those beads blowing for someone else but I don't recall what the total damage (beads + collateral) was. EDIT: For reference, the information about the board layout and parts list is on github here: https://github.com/gridseed/gc3355-doc or here: https://github.com/gridseed/usb-minerThanks for the help! No problem. Those parts should be pretty cheap, hopefully that's all that was damaged. Only way to find out is to replace them with identical spec replacements. Someone mentioned the possibility of temporarily bypassing those parts to verify functionality of the gridseed - however if it were mine, I'd replace the parts before testing it. :EDIT: What thermal paste did you use? Non-conductive I hope. You might want to clean that up while you've got it apart. In my opinion, there's no real point in using thermal paste unless you are positive the heatsink makes full contact with all 5 gc3355 chips. On all the gridseeds I have there are 2 components which are taller than the gc3355's and prevent full contact. I milled out part of the heatsink over those two components so the heatsink made full contact. I posted a pic in this thread somewhere of it. However, if you do that, then the heatsink will likely make contact with all the capacitors surrounding the gc3355's. So I covered those with electrical tape to prevent a short. |
|
|
|
*image snipped*
Does anybody know what this two parts(yellow marked)? my 5volt mode with 49.9k resistor swapped pot is blown(13 out of 20 GS) after 3 days 24/7 run for unknown reason. windows still recognize the com port and 5 chip still visible in cpuminer. if anybody knows the value of this two i might try to change this to see if it works.
Ferrite Beads. 300ohm@100MHz,3A Thanks for quick replay, any idea why would it might blow? Also is it 0603 ? The footprint is actually listed as R1206. I believe those are part of the 12v circuitry on the board, so it could be from a surge of some sort I suppose. I've seen another report of those beads blowing for someone else but I don't recall what the total damage (beads + collateral) was. EDIT: For reference, the information about the board layout and parts list is on github here: https://github.com/gridseed/gc3355-doc or here: https://github.com/gridseed/usb-miner |
|
|
|
*image snipped*
Does anybody know what this two parts(yellow marked)? my 5volt mode with 49.9k resistor swapped pot is blown(13 out of 20 GS) after 3 days 24/7 run for unknown reason. windows still recognize the com port and 5 chip still visible in cpuminer. if anybody knows the value of this two i might try to change this to see if it works.
Ferrite Beads. 300ohm@100MHz,3A |
|
|
|
To everyone that has done this mod, have any of you needed to upgrade cooling on the unit?
I was using thermal compound on mine, and one of mine shorted out and fried the gridseed. Apparently when you remove the pad, the screws compress down and potentially touch the unit.
Are you guys just leaving stock pads on there? I would like to get aftermarket pads, but to upgrade cooling on 50 of my seeds will be like $200 in thermal pads lol.
The thermal interface grease makes me paranoid now because of the 1 unit that fried.
If you remove the thermal pad on the back of the unit, you have to insulate the exposed contacts otherwise a short WILL occur. If you chose to use paste on the top of the chips instead of the thermal pad, then chances are you'll need to mill out part of the heatsink so that it makes full contact to all five gc3355 chips. There are 2 components (a 6-pin chip and the crystal) which are taller than the gc3355 chips. If you crank down the heatsink, you'll put a lot of pressure on those two components and likely break them or at least break the solder connection to the board. Thermal pads may not have level of heat transfer that the thermal paste does, but they're a much easier option. |
|
|
|
It's a work in progress, people shouldn't expect perfection with every release.
Unless you are called Wolfey2014.   |
|
|
|
Just updated to the new binaries. Working great for me.
Same here...awesome work Sandor. Not sure why it's "freezing" or "locking up" for some people, I've never had the problem, but I don't have a lot of gridseeds either. Maybe it's a memory allocation issue with enabling autotune for all those gridseeds? I'm not sure if you're using hashtables, arrays, or dictionaries to record and keep track of autotune info but maybe people with a lot of gridseeds are hitting a limitation within the method? If someone wants to send me 100 or more gridseeds to "test" I have 32GB ram in my system to test the theory  It's none of that. The curses TUI isn't thread safe, so I have to use pthread_mutex to keep stuff synchronized between threads. My shitty coding lead to some deadlocks I think, where one thread was waiting forever for a lock to release. I have no idea about the top stat on Windows though, the same code works perfectly fine on any Unix system I tested (Rpi, Ubuntu, OpenWrt) which are using ncurses lib, so I guess it's a bug in the pdcurses lib which Windows uses (specifically printw/wprintw). That's good to know, at least you know where to look. It's a work in progress, people shouldn't expect perfection with every release. My hat's off to you for your awesome work though. The top bar was just a 'technicality' in my opinion as the rest of it worked just fine. |
|
|
|
Just updated to the new binaries. Working great for me.
Same here...awesome work Sandor. Not sure why it's "freezing" or "locking up" for some people, I've never had the problem, but I don't have a lot of gridseeds either. Maybe it's a memory allocation issue with enabling autotune for all those gridseeds? I'm not sure if you're using hashtables, arrays, or dictionaries to record and keep track of autotune info but maybe people with a lot of gridseeds are hitting a limitation within the method? If someone wants to send me 100 or more gridseeds to "test" I have 32GB ram in my system to test the theory |
|
|
|
Important! You MUST update to the latest binaries (Download on Github)
Have fixed the top stat on Windows (weird bug), and I think lock ups are fixed now too. I have been testing on Rpi and Windows for 6 hours now.
Are the links to the binaries updated? I downloaded the 'new' version and still have the same problem as before with the top stats - and the dropbox link says "13 hours ago". |
|
|
|
No idea why the top stat is bugged in Windows, seems to be some sort of memory corruption or bug in the library, the function that's causing it is "wprintw".
I'll have look in Valgrind.
If it helps any, it looks like the Total accepted is the same as total hw errors. I've been periodically checking and happen to see both numbers change to the same number at the same time. |
|
|
|
Sandor, the stats are not updating in the new version? My screenshot: http://snag.gy/D6aPH.jpgThey still show 0 and 0 speed even after some time when shares have been accepted and mining is in progress.. I can confirm. I'm seeing the same thing here. The individual gridseed hashrates are updating, but the "total" at the top always says 0/0. Sometimes there's a "-" in front, but always 0. Edit: Also looks like the Total number of accepted isn't updating past 1. So far each gridseed says 10+ accepted but the total at the top still says 1. |
|
|
|
Important! You MUST update to the latest binaries (Download on Github)In this update the TUI code is rewritten, it accepts any window size and if the window isn't large enough, you can scroll through the stats using the UP/DOWN keys. Fixed the biggest bug yet related to crashes/stuck/flooding of HW errors, it's really critical to update now! G-Blades are 2 boards, so 2 ttyACMx. No need to tell it, it detects which is which based on the firmware version thats on the MCU chip.  Thanks Sandor! Testing it out now. For those missing the link: https://github.com/siklon/cpuminer-gc3355/ (It's also in Sandor's sig) |
|
|
|
|
For what it's worth I don't have the problem of the missing scrolling data and I'm running Win 8.1. No special command line arguments or settings either.
|
|
|
|
Hey nst6563,
what commands did you use to get both the summary and scrolling print out? I can only get one or the other..DOH!
Tanks!
Wolfey - here's the command I'm using. I didn't enter anything special that I know of to get both the summary at the top as well as the scrolling data. minerd-gc3355.exe --gc3355=\\.\COM8,\\.\COM9,\\.\COM10 --gc3355-freq=\\.\COM8:1200:0,\\.\COM8:1150:1,\\.[b]\COM8:11750:2,[/b]\\.\COM8:600:3,\\.\COM8:1175:4,\\.\COM9:1225:0,\\.\COM9:1200:1,\\.\COM9:1225:2,\\.\COM9:1225:3,\\.\COM9:1225:4,\\.\COM10:1225:0,\\.\COM10:1275:1,\\.\COM10:1250:2,\\.\COM10:1250:3,\\.\COM10:1275:4 --gc3355-autotune --url=stratum+tcp://pool.manicminer.in:3333 --userpass user:pass Thanks. I'll chk it out. You sure about that? ^^^^^^^ I wish! Crap...forgot to remove the typo. I cut and pasted from a previous post lol. |
|
|
|
Hey nst6563,
what commands did you use to get both the summary and scrolling print out? I can only get one or the other..DOH!
Tanks!
Wolfey - here's the command I'm using. I didn't enter anything special that I know of to get both the summary at the top as well as the scrolling data. minerd-gc3355.exe --gc3355=\\.\COM8,\\.\COM9,\\.\COM10 --gc3355-freq=\\.\COM8:1200:0,\\.\COM8:1150:1,\\.\COM8:11750:2,\\.\COM8:600:3,\\.\COM8:1175:4,\\.\COM9:1225:0,\\.\COM9:1200:1,\\.\COM9:1225:2,\\.\COM9:1225:3,\\.\COM9:1225:4,\\.\COM10:1225:0,\\.\COM10:1275:1,\\.\COM10:1250:2,\\.\COM10:1250:3,\\.\COM10:1275:4 --gc3355-autotune --url=stratum+tcp://pool.manicminer.in:3333 --userpass user:pass |
|
|
|
|
@Happydaze - what you might try to check is the voltage on the vIN pins on the gc3355 chips. Test them all, ones that vary may lead to another clue as to where the fault is. Between looking at the board and the schematics you can likely trace back the supply voltage line and test at various points along the way to try and narrow down the possibilities.
|
|
|
|
|
I see the command lines of various mining setups and it just leaves me wondering...is there a way we could dump all the comm and speed assignments to a config file, or if the comm and speed assignments are omitted, have cpuminer search for the gridseeds and just run at the default speed that is indicated by --freq?
|
|
|
|
:EDIT: If I remove the --log parameter it doesn't freeze. When I add it back in, it freezes after just a minute or two.
I can report this same issue, I'm trying it now without --log to see what happens. Thanks for the tip. Hmmm... I can confirm that the new miner lasts longer without --log, but it still ends up freezing on my box after about 2 hours, I had no problems with the last version freezing. my batch file: minerd.exe --freq=1200 --gc3355-autotune --gc3355=\\.\COM3,\\.\COM4,\\.\COM5,\\.\COM6 --gc3355-chips=5 --debug --url=stratum+tcp://xxx:4444 --userpass=xxx:xxx Also, the miner in the output says it will adjust the voltage in steps of 25, ie " 2565 steps until frequency adjusts to 1175MHz" but then it really only bumps it down to 1190 from 1200 on the status display at the top. I can't tell what frequency it really adjusting it to. I'm restarting for another run, lets see if it can stay up longer this time. Once I removed both the --debug and --log from the command line my miner has been running all night without any hiccups. It doesn't seem to like something about those two parameters. Memory allocation maybe? Dunno... |
|
|
|
I would definitely replace those two components and not run the gridseed very long at all without them. I think your gc3355 chips may be ok since the blown parts are part of the 12v circuitry. Don't discount any damage yet though. I had a problem with the 12v mosfet and one of my gc3355 chips took a hit. The rest seem to work ok, but that one chip just isn't stable anymore at almost any speed. |
|
|
|
gtraah - could be power related. Volt x amps = watts. If you have a significant amount of voltage drop then the amps will go way up. You used a 49.9k right? Are you allowing 30 watts per pod on your power supplies? That should provide a good safety margin.
I think the part in the photo is:
Device Type: FERRITE BEAD_R1206_300OHM@100MH
Value: 300ohm@100MHz,3A
Someone else should confirm it for you.
Thanks vERY VERY much Happydaze, are they both the same? can someone please confirm this please I would like to get these asap so I can get this pod back online... I dont really want to throw away $100 + 510KH... Yes 49.9K was used I do not have any other to use. So lets thin about this for a second, HASHRA sells the 6-PIN > 10 barrel tips and states no more than 250watt and only for scrypt. I did some research which saw someone find those can handle 192watt... I now have 7 - Vmodded Seeds on each 6-PIN they are all working, I am just thinking to myself --- Is it or isnt it the cause, I DEFINITLEY know the 75w spec is ridiculous But I now made sure its under the 192watt as of what I found after some research was done... Not sure why hashra says 250w is the limit and if thats the case I would of thought they should be fine. And if what your saying the amps sky rocketted... WOuld that happen if only I was only short by 20-30watt? Do you think its because I plugged them in all at the same time and then flicked the powersupply on, maybe plug them in one by one? When you turn on anything electronic, there is an initial surge current (normally very small) which is higher than the operational current. I have a hard time believing that turning on 20-30 gridseeds at once would generate a surge in current powerful enough to blow components unless those components were somehow 'weak' to begin with. I think if you replace those beads you'll be back in business - hopefully no worse for wear. I had a similar issue with a mosfet blowing (like a dumbass, curiosity got the best of me and I tried dual mining with a voltmod). I replaced the mosfet but the gridseed just doesn't seem to run "like it used to", particularly chip #3. But...thanks to Sandor I can clock chip #3 lower than the rest and still get 450Kh/s out of it. |
|
|
|
Thanks! Testing it out now. One thing I noticed I miss right off the bat is the informative messages regarding each chip's frequency. I also noticed that it incorrectly displays the frequency of one of my gridseeds - it's displaying as 3175Mhz (I WISH!). ... Start it with Log files are saved as "cpuminer-gc3355.log" in the same folder. Let me know what the chip frequency are set at. Here is the command line (Gridseed speeds are set within it) minerd-gc3355.exe --gc3355=\\.\COM8,\\.\COM9,\\.\COM10 --gc3355-freq=\\.\COM8:1200:0,\\.\COM8:1150:1,\\.\COM8: 11750:2,\\.\COM8:600:3,\\.\COM8:1175:4,\\.\COM9:1225:0,\\.\COM9:1200:1,\\.\COM9:1225:2,\\.\COM9:1225:3,\\.\COM9:1225:4,\\.\COM10:1225:0,\\.\COM10:1275:1,\\.\COM10:1250:2,\\.\COM10:1250:3,\\.\COM10:1275:4 --gc3355-autotune --url=stratum+tcp://pool.manicminer.in:3333 --userpass user:pass --debug --log I just launched it with the parameters you specified, let it run for a few minutes but then it just froze. Here's the log: https://www.dropbox.com/s/jj1yneqjcrstr81/cpuminer-gc3355.logBe careful with that.  Holy Shite! talk about a typo...whoa... |
|
|
|
|
Show Posts
