Topic: Bitminter client (Windows/Linux/Mac) - page 11. (Read 654946 times)
thanks, and keep up the good working
so again i learn an new thing.. 
thanks
Isn't it an idea then that you can give a specific usb minor a unique name or isn't that possible?
I want the U1 do 1,6 ghz and the U2 do 2,0 GHz my server is in the my basement so it can be pretty handy i can give them an unique id to indentefy each other. it is just a suggestion, thanks for listing and good luck with improve bitminer, its already great...
thanksIsn't it an idea then that you can give a specific usb minor a unique name or isn't that possible?
I want the U1 do 1,6 ghz and the U2 do 2,0 GHz my server is in the my basement so it can be pretty handy i can give them an unique id to indentefy each other. it is just a suggestion, thanks for listing and good luck with improve bitminer, its already great...
You can do this today. Each has their own setting. Only problem is if they trade places, U1 on COM1 and U2 on COM2 originally. You set different speeds. Later for some reason the U1 is on COM2 and U2 on COM1, and the client will attempt to run them with wrong speeds. I think this will normally not happen if you keep them plugged into the same USB ports.
so again i learn an new thing.. thanks
Isn't it an idea then that you can give a specific usb minor a unique name or isn't that possible?
I want the U1 do 1,6 ghz and the U2 do 2,0 GHz my server is in the my basement so it can be pretty handy i can give them an unique id to indentefy each other. it is just a suggestion, thanks for listing and good luck with improve bitminer, its already great...
regards,
bas vw
thanksIsn't it an idea then that you can give a specific usb minor a unique name or isn't that possible?
I want the U1 do 1,6 ghz and the U2 do 2,0 GHz my server is in the my basement so it can be pretty handy i can give them an unique id to indentefy each other. it is just a suggestion, thanks for listing and good luck with improve bitminer, its already great...
regards,
bas vw
Difference in bitminter U1/u2 antminer
Is it possible that bitminter detects the difference between U1 and U2. its difficult to see the difference now in program.
Lucky you have make the identify button.
Is it possible that bitminter can see the difference between the tow in the new beta?
Regards,
Basvw
Is it possible that bitminter detects the difference between U1 and U2. its difficult to see the difference now in program.
Lucky you have make the identify button.
Is it possible that bitminter can see the difference between the tow in the new beta?
Regards,
Basvw
As far as I know the only difference is the larger heatsink on U2. I don't think there is a way for software to detect a difference.
Difference in bitminter U1/u2 antminer
Is it possible that bitminter detects the difference between U1 and U2. its difficult to see the difference now in program.
Lucky you have make the identify button.
Is it possible that bitminter can see the difference between the tow in the new beta?
Regards,
Basvw
Is it possible that bitminter detects the difference between U1 and U2. its difficult to see the difference now in program.
Lucky you have make the identify button.
Is it possible that bitminter can see the difference between the tow in the new beta?
Regards,
Basvw
hmm weird thing is i dont have the cog or the wrenches on my client, the only thing i have under controls is the engine start button
That's because the "total" display that shows all the totals is the only one showing full information. The device displays are minimized. Press the green arrows to expand them and the wrench and other stuff will appear.
Thanks for the help ill go and have a fiddle with the software lol
ill go and have a fiddle with the software lol hmm weird thing is i dont have the cog or the wrenches on my client, the only thing i have under controls is the engine start button
Try the beta install, do not let the "unstable" run ya off. It is normal procedure to disclaim "everything OK" on new software.
I would reinstall java first, and do the remove older versions tool after. (if on windows)
I do not know if v1.5 even works on U1 and U2 I had issues early on, switched to BFG till doc had time to iron it out
The Newest Ant work is in the beta.
hmm weird thing is i dont have the cog or the wrenches on my client, the only thing i have under controls is the engine start button
1.6 beta report, got a new U2 today so I popped it into the 5v 5a hub I built, and set port speed to 115200 and Turned off allow computer to sleep this device in device properties.
Told BM Client to scan COM6 it was found, and I set the "wrench" icon to 2gh .0981 and it works just fine. Reports about 1.98 to 1.99 gh.
BFG on the older ones gives 2.03 - 2.08 but pool reports 1.99 so it is all evened out.
Works well Doc, Thank You
Oh, I have not tested the "Identify" button, cool feature, I will get to it later.
Told BM Client to scan COM6 it was found, and I set the "wrench" icon to 2gh .0981 and it works just fine. Reports about 1.98 to 1.99 gh.
BFG on the older ones gives 2.03 - 2.08 but pool reports 1.99 so it is all evened out.
Works well Doc, Thank You
Oh, I have not tested the "Identify" button, cool feature, I will get to it later.
im running v1.5.0 of the client and im getting 1.55Ghps out of my antminer u2, any ideas on how i can push this up to 2Ghps?
With 1.6.0 b1 I am able to run just about all of my Antminers at 2GHps with no miscalculations and the same or fewer rejections.
I need to replace all the resistors and put on a new heat sink array with better cooling and see how far I can go.
Anyone have an IR picture of a working Antminer U1/U2?
I need to replace all the resistors and put on a new heat sink array with better cooling and see how far I can go.
Anyone have an IR picture of a working Antminer U1/U2?
If you're talking about not overclocking an AntMiner you have to weight the hash rate against the rejections to find your sweet spot. I guess you should probably factor in power consumption as well for a total picture. Rejections aren't the end of the world when you're trying to get the most out of your gear.
For what it's worth as a noob, I have a lot less rejections using 1.60
So all is well, next to run some U1 ants with it, all seems well so far.
Good stuff. No network issues? Devices running out of work or connection issues?
v1.6 beta running fine for me. seems there are way less rejected pows.
I will report what I find, if anything...
The exchange rates tool - site is questioning ::
Hey! A lot of the information from this page has been moved to http://bitcoincharts.com. It might be worth visiting if you didn't know about that site yet.
I like the simplicity of the first original site tho.
So all is well, next to run some U1 ants with it, all seems well so far.
Good stuff. No network issues? Devices running out of work or connection issues?
v1.6 beta running fine for me. seems there are way less rejected pows.
So all is well, next to run some U1 ants with it, all seems well so far.
Good stuff. No network issues? Devices running out of work or connection issues?
OK testing W7 64bit IE10 Java7.
So far it picked up com14, as not in use on first fireup.
BFG was using it. So I cleaned all the unused ports in DeviceManager with these commands in command prompt.
set DEVMGR_SHOW_NONPRESENT_DEVICES=1
devmgmt
tick show hidden in view
remove greyed out icons for hubs and com devices...
Reran the v6 client and it found all ports being used as it should..
2014.04.06 [01:54] Cannot probe COM4: port in use
2014.04.06 [01:54] Cannot probe COM17: port in use
2014.04.06 [01:54] Cannot probe COM16: port in use
2014.04.06 [01:54] Cannot probe COM15: port in use
2014.04.06 [01:54] No external devices detected.
2014.04.06 [01:54] BFL drivers: http://www.ftdichip.com/Drivers/VCP.htm ASICMiner and Antminer drivers: http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx On Linux load FTDI driver: "sudo modprobe ftdi_sio vendor=0x0403 product=0x6014". You may lack access to serial ports (Ubuntu: "sudo usermod -a -G dialout USERNAME" then log out and back in).
2014.04.06 [01:54] Cannot probe COM14: port in use
2014.04.06 [01:54] Cannot probe COM3: port in use
2014.04.06 [01:54] Cannot probe COM7: port in use
2014.04.06 [01:54] Cannot probe COM12: port in use
2014.04.06 [01:54] Probe of port COM1 failed: timeout
The BFL message is not needed in this instance silabs is installed.
So all is well, next to run some U1 ants with it, all seems well so far.
So far it picked up com14, as not in use on first fireup.
BFG was using it. So I cleaned all the unused ports in DeviceManager with these commands in command prompt.
set DEVMGR_SHOW_NONPRESENT_DEVICES=1
devmgmt
tick show hidden in view
remove greyed out icons for hubs and com devices...
Reran the v6 client and it found all ports being used as it should..
2014.04.06 [01:54] Cannot probe COM4: port in use
2014.04.06 [01:54] Cannot probe COM17: port in use
2014.04.06 [01:54] Cannot probe COM16: port in use
2014.04.06 [01:54] Cannot probe COM15: port in use
2014.04.06 [01:54] No external devices detected.
2014.04.06 [01:54] BFL drivers: http://www.ftdichip.com/Drivers/VCP.htm ASICMiner and Antminer drivers: http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx On Linux load FTDI driver: "sudo modprobe ftdi_sio vendor=0x0403 product=0x6014". You may lack access to serial ports (Ubuntu: "sudo usermod -a -G dialout USERNAME" then log out and back in).
2014.04.06 [01:54] Cannot probe COM14: port in use
2014.04.06 [01:54] Cannot probe COM3: port in use
2014.04.06 [01:54] Cannot probe COM7: port in use
2014.04.06 [01:54] Cannot probe COM12: port in use
2014.04.06 [01:54] Probe of port COM1 failed: timeout
The BFL message is not needed in this instance silabs is installed.
So all is well, next to run some U1 ants with it, all seems well so far.
Does the "latest (auto update)" menu selection give 1.5 or 1.6 ?
It gives 1.5 until 1.6 is out of beta testing.
Bitminter client v1.6.0 beta1 is ready for testing.
New:
Note: if you were using the "port 80" option to bypass a firewall then this release will probably not work for you. v1.5.0 will still be available in the "tools" menu at bitminter.com for some time. If you have firewall issues, let me know what your needs are, or better yet, fix the firewall.
Please check it out:
New:
- Switch to Stratum mining protocol
- Show worker difficulty changes in the log
- Show the block's hash in the log when a block is found
Note: if you were using the "port 80" option to bypass a firewall then this release will probably not work for you. v1.5.0 will still be available in the "tools" menu at bitminter.com for some time. If you have firewall issues, let me know what your needs are, or better yet, fix the firewall.
Please check it out:
Does the "latest (auto update)" menu selection give 1.5 or 1.6 ?
Jump to: