|
|
|
nst6563
|
 |
April 28, 2014, 02:04:37 AM |
|
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!).  |
|
|
|
|
|
sandor111
|
|
April 28, 2014, 02:21:35 AM |
|
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. |
|
|
|
|
jamieb81
|
|
April 28, 2014, 02:32:48 AM |
|
this are the commands out of the --help for anyone looking for them Usage: minerd [OPTIONS] Options: -G, --gc3355=DEV0,DEV1,...,DEVn enable GC3355 chip mining mode (default: no) -F, --freq=FREQUENCY set GC3355 core frequency in NONE dual mode (default: 600) -f, --gc3355-freq=DEV0:F0,DEV1:F1,...,DEVn:Fn individual frequency setting --gc3355-freq=DEV0:F0:CHIP0,...,DEVn:Fn:CHIPn individual per chip frequency setting -A, --gc3355-autotune auto overclocking each GC3355 chip (default: no) -c, --gc3355-chips=N # of GC3355 chips (default: 5) -a, --api-port=PORT set the JSON API port (default: 4028) -t, --text disable curses tui, output text -L, --log file logging -o, --url=URL URL of mining server (default: http://127.0.0.1:9332/) -O, --userpass=U:P username:password pair for mining server -u, --user=USERNAME |
|
|
|
|
|
wolfey2014
|
|
April 28, 2014, 02:36:26 AM |
|
Sandor, Can I use the same command line syntax I was using in the previous version? Using it changes the output screen so I can't see anything scrolling below the pod numbers, speed, accepts etc. I also don't understand the syntax in help for setting autotune ON, it says default is NO....tried =Y , =YES but doesn't work... I changed the exe name to minderdoc Current command line... minerdoc --freq=1150 --gc3355=com4,com5,com8,com7,com2,com6 --gc3355-autotune --url=stratum+tcp://pool.hashit.right:zzzz --userpass=xxx.xxx:xxx thanks! |
I Modify Miners Professionally! PM me for details!
|
|
|
|
sandor111
|
|
April 28, 2014, 02:41:22 AM |
|
Sandor, Can I use the same command line syntax I was using in the previous version? Using it changes the output screen so I can't see anything scrolling below the pod numbers, speed, accepts etc. I also don't understand the syntax in help for setting autotune ON, it says default is NO....tried =Y , =YES but doesn't work... I changed the exe name to minderdoc Current command line... minerdoc --freq=1150 --gc3355=com4,com5,com8,com7,com2,com6 --gc3355-autotune --url=stratum+tcp://pool.hashit.right:zzzz --userpass=xxx.xxx:xxx thanks! Syntax didn't change, it just doesn't output that if you aren't running in debug mode (--debug), but it works. If you want to scroll you have to disable the curses TUI. |
|
|
|
|
jamieb81
|
|
April 28, 2014, 02:45:18 AM |
|
Sandor, Can I use the same command line syntax I was using in the previous version? Using it changes the output screen so I can't see anything scrolling below the pod numbers, speed, accepts etc. I also don't understand the syntax in help for setting autotune ON, it says default is NO....tried =Y , =YES but doesn't work... I changed the exe name to minderdoc Current command line... minerdoc --freq=1150 --gc3355=com4,com5,com8,com7,com2,com6 --gc3355-autotune --url=stratum+tcp://pool.hashit.right:zzzz --userpass=xxx.xxx:xxx thanks! I'm using this syntax minerd-gc3355.exe --gc3355=\\.\COM7,\\.\COM8,\\.\COM9,\\.\COM10,\\.\COM11 --gc3355-autotune --freq=1150 --url=stratum+tcp:/xx:xx --userpass=xx.xx:xx |
|
|
|
|
|
nst6563
|
|
April 28, 2014, 02:48:48 AM |
|
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.log: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. System specs: Asus P8z77v-pro Core i-7 IvyBridge @ 4.55Ghz 24GB DDR3 5-disc RAID with SSD acceleration |
|
|
|
|
|
sandor111
|
|
April 28, 2014, 02:56:45 AM |
|
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.  |
|
|
|
|
nst6563
|
|
April 28, 2014, 03:00:05 AM |
|
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... |
|
|
|
|
|
jamieb81
|
|
April 28, 2014, 03:01:46 AM |
|
so if we just use freq=\\.\COM8:1200,\\.\COM9:1150,\\.\COM10:1750,\\ it sets the speeds per pod right? |
|
|
|
|
|
wolfey2014
|
|
April 28, 2014, 03:29:07 AM |
|
Sandor, Can I use the same command line syntax I was using in the previous version? Using it changes the output screen so I can't see anything scrolling below the pod numbers, speed, accepts etc. I also don't understand the syntax in help for setting autotune ON, it says default is NO....tried =Y , =YES but doesn't work... I changed the exe name to minderdoc Current command line... minerdoc --freq=1150 --gc3355=com4,com5,com8,com7,com2,com6 --gc3355-autotune --url=stratum+tcp://pool.hashit.right:zzzz --userpass=xxx.xxx:xxx thanks! Syntax didn't change, it just doesn't output that if you aren't running in debug mode (--debug), but it works. If you want to scroll you have to disable the curses TUI. k, thx. I see scrolling now but no summary at the top anymore.. Can I get both to work at the same time? I thought that was the idea. Also, I see only 2 colors. No reds and greens like in the previous versions....why? I presume pod autotune is ON by default? thx! |
I Modify Miners Professionally! PM me for details!
|
|
|
|
happydaze
|
|
April 28, 2014, 04:17:21 AM
Last edit: April 28, 2014, 04:34:17 AM by happydaze |
|
I tried rmod on a second gridseed today after having it working well on another gridseed for several days. This one already had vmod1 and I was adding 15k. Actual measured numbers were 35.83k + 14.92k = 50.75 tested on board. That is on the high side I know. I got the clicking noise and tried to redo a few times but couldn't solve it. I'm not good at soldering but thought I did an ok job. Voltage was low on first try 1.3 something. Second try had the voltage at 1.63v. I removed vmod1 but the clicking was still there. You can actually feel the clicking. The first pod I did had a higher value large silver capacitor 16v 330. This pod has 16v 220. I screwed something up though on one of the later tries. I may have bridged to that 20nf capacitor. It got hot quickly ..... some solder has actually come out from under one of the gc3355 chips on two sides! These little things are pretty tough. One chip of the five is still working so hopefully I can fix it up.   Summary: rmod removed, bridge replaced, no clicking sound It powers up and miner software sees it. cpuminer reports 5 chips and sets the frequency. Only one chip does any mining and those shares are accepted by pool. (only chip #4 works) Red light blinks very very slow. It can be off for a long time or on for a long time. This might be caused because only one chip is actually mining. Solder is visible on two sides of the center Gridchip (one of the mining chips). See photo. It covers four or five pins on one side and maybe three on another side. I did not drop solder there and I know it wasn't there earlier because I took a photo of the new resistor in place before trying it. I think it has come out from under the chip if that is possible. How do I remove that? I need some advice or suggestions on what to check / what to do so I can try to recover it or at least get a few more chips working. Any help will be greatly appreciated. |
|
|
|
|
|
wolfey2014
|
|
April 28, 2014, 04:39:52 AM |
|
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!). 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! |
I Modify Miners Professionally! PM me for details!
|
|
|
|
wolfey2014
|
|
April 28, 2014, 05:00:40 AM |
|
I tried rmod on a second gridseed today after having it working well on another gridseed for several days. This one already had vmod1 and I was adding 15k. Actual measured numbers were 35.83k + 14.92k = 50.75 tested on board. That is on the high side I know. I got the clicking noise and tried to redo a few times but couldn't solve it. I'm not good at soldering but thought I did an ok job. Voltage was low on first try 1.3 something. Second try had the voltage at 1.63v. I removed vmod1 but the clicking was still there. You can actually feel the clicking. The first pod I did had a higher value large silver capacitor 16v 330. This pod has 16v 220. I screwed something up though on one of the later tries. I may have bridged to that 20nf capacitor. It got hot quickly ..... some solder has actually come out from under one of the gc3355 chips on two sides! These little things are pretty tough. One chip of the five is still working so hopefully I can fix it up. Summary: rmod removed, bridge replaced, no clicking sound It powers up and miner software sees it. cpuminer reports 5 chips and sets the frequency. Only one chip does any mining and those shares are accepted by pool. (only chip #4 works) Red light blinks very very slow. It can be off for a long time or on for a long time. This might be caused because only one chip is actually mining. Solder is visible on two sides of the center Gridchip (one of the mining chips). See photo. It covers four or five pins on one side and maybe three on another side. I did not drop solder there and I know it wasn't there earlier because I took a photo of the new resistor in place before trying it. I think it has come out from under the chip if that is possible. How do I remove that? I need some advice or suggestions on what to check / what to do so I can try to recover it or at least get a few more chips working. Any help will be greatly appreciated. Wow! That sucks! No one has EVER had this trouble like that with the R52 mod! No One! Not even green-horns! Shit!This really bugs me! I feel for your loss! 4 good chips ruined by yet another Zig DOH!!! pod killer mod! Are you absolutely sure un-bridging and adding a resistive load to R42 is correct, Zig? Never mind. I strongly suspect - NOT! This clicking problem only started happening after Zig's mod was introduced! I think that Zig's mod should be killed for now, at least until the actual cause of the clicking which most likely means something permanently serious has happened and your pod is now a paper weight, is discovered. Looks like I have my work cut out for me. Thanks Zig! Remember, R52 (aka R139-at least he got that right) mod is proven by thousands of mods to work without harming your pod, even if you make a mistake, the worst that happens is your pod stops working until the solder connections are re-done correctly or the mod is reversed. No permanent destruction! Certainly no solder melting hot chips destruction occurs! I think this makes 4 clicking pods now....That's just too many fried pods! DANGER!Stick with R52 mod. And again, the chances of our pods ever profitably mining SHA again are slim to none and IF the mod ever has to be reversed, it can be done easily by any qualified tech. Even greenhorns can do it in a reasonable amount of time, obviously! |
I Modify Miners Professionally! PM me for details!
|
|
|
mixdio
Newbie
 Offline
Activity: 20
Merit: 0
|
|
April 28, 2014, 05:21:47 AM |
|
Wow! That sucks! No one has EVER had this trouble like that with the R52 mod! No One! Not even green-horns!
Shit!This really bugs me! I feel for your loss! 4 good chips ruined by yet another Zig DOH!!! pod killer mod! Are you absolutely sure un-bridging and adding a resistive load to R42 is correct, Zig? Never mind. I strongly suspect - NOT! This clicking problem only started happening after Zig's mod was introduced!
I think that Zig's mod should be killed for now, at least until the actual cause of the clicking which most likely means something permanently serious has happened and your pod is now a paper weight, is discovered. Looks like I have my work cut out for me. Thanks Zig!
Remember, R52 (aka R139-at least he got that right) mod is proven by thousands of mods to work without harming your pod, even if you make a mistake, the worst that happens is your pod stops working until the solder connections are re-done correctly or the mod is reversed. No permanent destruction! Certainly no solder melting hot chips destruction occurs! I think this makes 4 clicking pods now....That's just too many fried pods! DANGER!
Stick with R52 mod. And again, the chances of our pods ever profitably mining SHA again are slim to none and IF the mod ever has to be reversed, it can be done easily by any qualified tech. Even greenhorns can do it in a reasonable amount of time, obviously!
My devices have been running stable for over a month with R46 = 14k7. Zig's mod looks to be the same mod I posted back on page 22. The schematic clearly shows R46 in series with the other SET resistors, and the mod should not cause any more problems than replacing R63/R64/R66/R139. |
|
|
|
|
Ranma13
Newbie
Offline
Activity: 17
Merit: 0
|
|
April 28, 2014, 06:06:11 AM
Last edit: April 28, 2014, 06:20:37 AM by Ranma13 |
|
Wow! That sucks! No one has EVER had this trouble like that with the R52 mod! No One! Not even green-horns!
Shit!This really bugs me! I feel for your loss! 4 good chips ruined by yet another Zig DOH!!! pod killer mod! Are you absolutely sure un-bridging and adding a resistive load to R42 is correct, Zig? Never mind. I strongly suspect - NOT! This clicking problem only started happening after Zig's mod was introduced!
I think that Zig's mod should be killed for now, at least until the actual cause of the clicking which most likely means something permanently serious has happened and your pod is now a paper weight, is discovered. Looks like I have my work cut out for me. Thanks Zig!
Remember, R52 (aka R139-at least he got that right) mod is proven by thousands of mods to work without harming your pod, even if you make a mistake, the worst that happens is your pod stops working until the solder connections are re-done correctly or the mod is reversed. No permanent destruction! Certainly no solder melting hot chips destruction occurs! I think this makes 4 clicking pods now....That's just too many fried pods! DANGER!
Stick with R52 mod. And again, the chances of our pods ever profitably mining SHA again are slim to none and IF the mod ever has to be reversed, it can be done easily by any qualified tech. Even greenhorns can do it in a reasonable amount of time, obviously!
You really need to cut it out with the personal attacks. It's obvious to anyone who's been following this thread that you have some sort of personal vendetta against Zig for introducing an alternative mod. It doesn't matter if you've 'invented' the original mod, nobody likes an asshole and you're doling it out in droves. And I've had the clicking issue as well, and I've only done the R52 mod. The only time I heard it though was when I plugged in the power to the USB hub, but not the 12V power. It went away after I turned on the 12V power. I thought it was kind of weird, but didn't think much of it at the time, and it never happened again except for that one time. All my Gridseeds are hashing away fine too, so I'm not sure what I did to cause it to click. |
|
|
|
|
amix
Member
Offline
Activity: 84
Merit: 10
|
|
April 28, 2014, 06:36:05 AM |
|
I tried rmod on a second gridseed today after having it working well on another gridseed for several days. This one already had vmod1 and I was adding 15k. Actual measured numbers were 35.83k + 14.92k = 50.75 tested on board. That is on the high side I know. I got the clicking noise and tried to redo a few times but couldn't solve it. I'm not good at soldering but thought I did an ok job. Voltage was low on first try 1.3 something. Second try had the voltage at 1.63v. I removed vmod1 but the clicking was still there. You can actually feel the clicking. The first pod I did had a higher value large silver capacitor 16v 330. This pod has 16v 220. I screwed something up though on one of the later tries. I may have bridged to that 20nf capacitor. It got hot quickly ..... some solder has actually come out from under one of the gc3355 chips on two sides! These little things are pretty tough. One chip of the five is still working so hopefully I can fix it up. Summary: rmod removed, bridge replaced, no clicking sound It powers up and miner software sees it. cpuminer reports 5 chips and sets the frequency. Only one chip does any mining and those shares are accepted by pool. (only chip #4 works) Red light blinks very very slow. It can be off for a long time or on for a long time. This might be caused because only one chip is actually mining. Solder is visible on two sides of the center Gridchip (one of the mining chips). See photo. It covers four or five pins on one side and maybe three on another side. I did not drop solder there and I know it wasn't there earlier because I took a photo of the new resistor in place before trying it. I think it has come out from under the chip if that is possible. How do I remove that? I need some advice or suggestions on what to check / what to do so I can try to recover it or at least get a few more chips working. Any help will be greatly appreciated. firstly clicking is prob the crystal i got it when i did the r52 mod with a 56k resistor. Applying slight pressure o. The crystal lessened it i reworked. It was less. I then uninstalled my grid dricers - i was getting an uart open error - and checkdd the box to delete the drivers. Tge dud a fresh install of the drivers. It sorted it. I aslo noticed havibg several instances of grid miner software cancause issues!! Byt it ciuldve been my drivers agsin. As for the dolder o. Your chips thats from underside of yhe gtids. It connects the thermal plate under the grids to the theal vias. This is something i mentioned way back. Appears they used eithrr normal solder and tinned the pads or too much solder paste. On mine it was leaking o. The underside on several chips i had balls o tge thermal vias!! Try reworking it but first check the underside of your pcd make sure the thermal viad are clear. You might want to remove any dolder fro. The underside first. Hot air rework would do nicely alibg with flhx and desolder braid. To remove the doldrr balls o top flux and desolder braid. Either hit air it and remove the balls or a very fine solder tip. Rither way you need to be carefull. Chances are you might end up unsolderi g a fws pins. Resolder them with a fine tip. Remember to applyf Flux to the pins beforehand and ti you tip. Google smd remove. Theres a few you tube videos out there thatll be able to show you. It sint eady though so pratice on somethi g else first. Dud wolfey invent the mod?? Er no wad someo e else he jyst gyessed what they wsd up to. Slthough i had the idwa of the r52 mod first. Others jyst tested it and put it into practice furst. When overclickibg make sure you have fan cooling and even improved thetmsl pafs/paste especailly on the u derside!!!!! |
|
|
|
|
|
ZiG
|
|
April 28, 2014, 07:07:21 AM |
|
Wow! That sucks! No one has EVER had this trouble like that with the R52 mod! No One! Not even green-horns!
Shit!This really bugs me! I feel for your loss! 4 good chips ruined by yet another Zig DOH!!! pod killer mod! Are you absolutely sure un-bridging and adding a resistive load to R42 is correct, Zig? Never mind. I strongly suspect - NOT! This clicking problem only started happening after Zig's mod was introduced!
I think that Zig's mod should be killed for now, at least until the actual cause of the clicking which most likely means something permanently serious has happened and your pod is now a paper weight, is discovered. Looks like I have my work cut out for me. Thanks Zig!
Remember, R52 (aka R139-at least he got that right) mod is proven by thousands of mods to work without harming your pod, even if you make a mistake, the worst that happens is your pod stops working until the solder connections are re-done correctly or the mod is reversed. No permanent destruction! Certainly no solder melting hot chips destruction occurs! I think this makes 4 clicking pods now....That's just too many fried pods! DANGER!
Stick with R52 mod. And again, the chances of our pods ever profitably mining SHA again are slim to none and IF the mod ever has to be reversed, it can be done easily by any qualified tech. Even greenhorns can do it in a reasonable amount of time, obviously!
My devices have been running stable for over a month with R46 = 14k7. Zig's mod looks to be the same mod I posted back on page 22. The schematic clearly shows R46 in series with the other SET resistors, and the mod should not cause any more problems than replacing R63/R64/R66/R139. Finally somebody here, competent to verify independently what I was posting in that thread...with clear understanding of (Gridseed ) electronics, schematics etc... Thanks Mixdio...! I recall now seeing your post back in March...I took a different path since the beginning...March 13 ...using trim pot to R46 to explore smoothly the DVDD voltage increase and it's effect on the overclocking performance and hashing ...Now I see also that you have been playing with VPLL...me too... and can tell that VPPL has a very positive effect on the stability and performance potential of the device...( reference google CPU PLL ...) Back to the problem...everything is pointing to C35...the capacitor next to R46 pads...It is connected to the pin "SS" of the uP1509 - "buck convertor" / Voltage chip...I could NOT find any data or specs for this chip...but many other manufacturers have similar IC...like TI, Motorola, Panasonic etc...All of them are marking "SS" pin as "Soft Start" ...which means that it is responsible for a nice, Smooth, with NO transient transitions on the Power MOSFETs ...gradual rise of the voltage supplied to the rest of the circuitry... C35 is connected to "SS" pin and is responsible for this function of the voltage regulator to start / function properly...IF YOU SHORT or DISCONNECT C35... in any way...the voltage regulator CAN NOT START "SOFT"...or smooth...or properly...and one could expect all kind of unwanted effects on the voltage output of the buck convertor...like clicking sound...maybe VR is trying to start...and couldn't...in cycle...I guess... In both of these cases the guys reported that have been messy around C35...short or missing...or something in that matter...Sorry to hear that... Anyway...I never had this problem so far...never have been messing with C35...and don't understand how C35 could be even touch in the process of cutting R46 bridge...there is enough space on the opposite side of C35 to use "Exacto knife"...cut gently the R46 bridge...and YOU ARE DONE...You don't need to solder anything to the pads of R46...or mess anymore in proximity with C35... I already pointed that there is many other spots - a FULL ROW of pads to solder...with a lot of space around...PLUS a BIG GROUND PAD under them... Again...to be able to modify / change /experiment with your electronic device(s)...a person have to...: 1. UNDERSTAND what needs to be done...and what he/she is doing... 2. Have KNOWLEDGE about the device...it's operation,... the process to be performed...and the desired/possible results... 3. TOOLS suitable to perform the job in satisfactory manner... 4. SKILLS to do it... 5. etc... IF you are not sure that you have ALL of these above...simply DO NOT DO IT...DON"T EVEN TRY...because the results will NOT BE what you are trying ...and expecting to be...but the decision is completely up to you.. I am only trying to help...for free...on my time...but you are the one to actually do it... Ask...research...learn first...and try later...it is NOT a rocket science...a relatively simple procedure...and one day there is a good chance to succeed... Thanks for your time to read this...didn't anticipate to be that long... ZiG |
|
|
|
|
|
happydaze
|
|
April 28, 2014, 11:24:11 AM |
|
I could screw up any mod  I bet. Sorry ZiG - I'm not blaming you at all. I did the first pod and it has run for several days. Re: C35 - the clicking came before accidentally bridging that. I took photos and planned to post them. It looked good from several angles. I suspect the clicking has to do with me making a poor solder connection, maybe even up at con3. The bridge to C35 came at a later attempt. I was so surprised that I did it and even more surprised that I didn't notice it before testing the pod. Looking at the brd file: R46 Pin 1 goes something referenced N31930727 on the board R46 Pin 2 goes to DGND C35 Pin 1 goes to N31930727 C35 Pin 2 goes to N31930664 It looked like the short went from pin 1 to pin 1. The components are tiny so maybe I shorted C35 itself. I also started the pod at 1200MHz - I feel kind of dumb admitting that. I had to post my failure. I want to focus on fixing it if I can. Turn a negative into a positive. ZiG - Can we put a resistor between Con3 pin3 and C38 pin1 or C40 pin1 or C41 pin1 or C43 pin1? Thank Amix for the helpful advice. I'll focus on cleaning the pins for now. The underside is clean. Any, all suggestions, tips, advice for what to do and what to check are welcome. |
|
|
|
|
|
