 Show Posts
|
|
Pages: [1] 2 »
|
Hi Patrike ! Another suggestion for for you to include in the next update if you find it usefull. Currently I can update coin price with exchange API in BTC. But for some coins I could only exchange to DOGE/LTC/ETH/ETC/USDT/USDC. Could it be possible to add something like a drop down menu in coin properties " Value in ..." and choose between populars coins like these. I don't know if I'm clear enough, so just tell me if not and I'll try to explain it another way, with graphics  I fully understand your request. It's noted but I will have to investigate if this can be supported in a good way. Thanks! Hi Patrike ! Any news about my request ? At least just a dynamic update of price in USD would already be great ! Thx ! |
|
|
|
Hi Patrike ! Another suggestion for for you to include in the next update if you find it usefull. Currently I can update coin price with exchange API in BTC. But for some coins I could only exchange to DOGE/LTC/ETH/ETC/USDT/USDC. Could it be possible to add something like a drop down menu in coin properties " Value in ..." and choose between populars coins like these. I don't know if I'm clear enough, so just tell me if not and I'll try to explain it another way, with graphics |
|
|
|
Hi Patrike ! Just some ideas that you could find interesting (or not ) In Coins tab I think it would be great to have like a search field to put the name, the ticker or the algo and it filters coins. Second one, still in the coin section, right click on a coin -> "pool using coin" -> "new pool" would save some time. This way I wouldn't have to select the coin in the "new pool" form. Third one. Sometimes I change download address for softwares to get the last version and when AM is updating with a newer version of this software that I missed I can't see quickly wich one uses a custom URL or not, so I have to check it manually (don't know if it's clear enough to understand) Maybe a blue font like when you modify coins properties could let you see if you have modified URL ? Or a box to check to let AM update to a new version even if you have modified URL, and leave it uncheck if you want to stay on custom URL forever. Fourth one, I added Zergpool online services through API to add Argon2d-250 & 4096. But it imports all algos. Is it possible for AM to check with predefined online services or user defined online services to avoid duplicates services (same stratum address) ? I've seen a function on Icemining to import directly pools, and you can select them one by one. That's a usefull feature, hope to see more pools using it in the future ! Great work however ! |
|
|
|
Lolminer 0.8.1 https://github.com/Lolliedieb/lolMiner-releases/releases/tag/0.8.1But I can't get it to work on Cuckatoo 31 with AM. C:\Users\*******\AppData\Local\AwesomeMiner\lolminer_v081_win64_1\0.8.1\lolMiner.exe -a cuckatoo31 --pool grin-eu.sparkpool.com --port 6667 --user ********* --pass ***** --coin GRIN --apiport 4028
====================================================================================================
> +---------------------------------------------------------+
> | _ _ __ __ _ ___ ___ |
> | | | ___ | | \/ (_)_ __ ___ _ __ / _ \ ( _ ) |
> | | |/ _ \| | |\/| | | '_ \ / _ \ '__| | | | |/ _ \ |
> | | | (_) | | | | | | | | | __/ | | |_| | (_) | |
> | |_|\___/|_|_| |_|_|_| |_|\___|_| \___(_)___(1) |
> | |
> | |
> | This software is for mining Equihash |
> | 150/5: Beam 96/5: MNX 210/9: Aion |
> | 192/7: ZER, GENX, SAFE, VDL |
> | 144/5: BTG, ZEL and many more |
> | And Cuckatoo-31: Grin |
> | |
> | |
> | Made by Lolliedieb, April 2019 |
> +---------------------------------------------------------+
> Warning: No user profile defined in command line (--profile <profileName> missing)
> Using only DEFAULT section and command line input
> Reading pool data from command line
> Error: No coin profile find for coin GRIN |
|
|
|
|
@Patrike
Bminer 14.2.0 released with support of Cuckatoo31 on 1080 Ti
Am show speed in MHs instead of Hs by the way.
|
|
|
|
Hi Patrike ! When I'm minning Beam with Gminer 1.23 AM sends this command : miner.exe -a 150_5 -s beam.eu.nicehash.com -n 3370 -u 3LgnBTzLFZiKyDpAc9n7V42zphkz3cjx21 -p x --pers auto -w 0 --api 4028 And the --pers auto doesn't work with sparkpool, if I remove this it works well with a bat file, but I can't manage to remove --pers auto in AM. Thx Awesome Miner is currently adding "auto" if you didn't specify any personalization string in the Properties of the Pool you have defined in Awesome Miner. The example above was for Nicehash. Can you share the exact command line you use for Sparkpool? For sparkpool I do now that you need to add "--ssl 1" for Gminer to connect correctly. How do you see that "--pers auto" creates a problem - do you get any error message in Gminer while connecting to Sparkpool? When I add "--pers auto" it still connects fine. Sorry I messed up my configuration files and my mind ^^ With --ssl 1 it works well. It wasn't related with personalization string. Thx for support ! |
|
|
|
Hi Patrike ! When I'm minning Beam with Gminer 1.23 AM sends this command : miner.exe -a 150_5 -s beam.eu.nicehash.com -n 3370 -u 3LgnBTzLFZiKyDpAc9n7V42zphkz3cjx21 -p x --pers auto -w 0 --api 4028 And the --pers auto doesn't work with sparkpool, if I remove this it works well with a bat file, but I can't manage to remove --pers auto in AM. Thx |
|
|
|
|
Hi Patrike !
Just another little issue to submit to you.
When I'm minning Grin with G miner tha hashrate reported on AM isn't the same in Gminer console (35 for AM and 36.8 in Gminer).
Except this everything is fine with this update !
Thanks.
|
|
|
|
Hi Patrike ! I have an issue with Bminer 12.2 and sparkpool with Grint It works correctly with my bat file : bminer.exe -uri cuckaroo29://myaddress@gmail.com%%2Frig_123@grin.sparkpool.com:6666 But in AM I can't managed to get it working correctly. This is the command sent. bminer.exe -uri cuckaroo29://myaddress@gmail.com%%2Frig_123:x@grin.sparkpool.com:6666 -watchdog=false -api=0.0.0.0:4028 And this is the result > invalid value "cuckaroo29://myaddress@gmail.com%%2Frig_123:x@grin.sparkpool.com:6666" for flag -uri: parse cuckaroo29://myaddress@gmail.com%%2Frig_123:x@grin.sparkpool.com:6666: invalid URL escape "%%2" Could you take a look at this ? Thx ! Thanks for the very detailed report. I think Awesome Miner is getting confused about '@' in both the mail address and before the server name. Edit: What are this part "%%2" indicating? Having double % is not allowed in the URL and the reason it works from the batch-file is that %% is being translated into a single %. Can you please check this part? The %%2 comes from sparkpool faq section. https://support.sparkpool.com/hc/en-us/articles/360015730673-Configuration-for-BminerI changed with only one % and it works fine ! Thx |
|
|
|
Hi Patrike ! I have an issue with Bminer 12.2 and sparkpool with Grint It works correctly with my bat file : bminer.exe -uri cuckaroo29://myaddress@gmail.com%%2Frig_123@grin.sparkpool.com:6666 But in AM I can't managed to get it working correctly. This is the command sent. bminer.exe -uri cuckaroo29://myaddress@gmail.com%%2Frig_123:x@grin.sparkpool.com:6666 -watchdog=false -api=0.0.0.0:4028 And this is the result > invalid value "cuckaroo29://myaddress@gmail.com%%2Frig_123:x@grin.sparkpool.com:6666" for flag -uri: parse cuckaroo29://myaddress@gmail.com%%2Frig_123:x@grin.sparkpool.com:6666: invalid URL escape "%%2" Could you take a look at this ? Thx ! |
|
|
|
Worked like a charm, thanks, I didn't know this tool ! |
|
|
|
No problems for remote agents on my miners. But on my computer the main application installator give me this post.  The same if I try to uninstall AM. |
|
|
|
Hi,
I'm trying to update from 6.0.9 to 6.0.10 but it fails everytime.
Here is the log
Hi. Can you please try to reboot the system once? It's not too uncommon that pending Windows Updates are preventing MSI-based installers from running correctly. Thx for support, I had a pending update, I rebooted twice but still the same issue, even with the 6.0.11 version.  |
|
|
|
Hi, I'm trying to update from 0.6.9 to 0.6.10 but it fails everytime. Here is the log 08/01/2019 20:02:32.193 [001] [S]Checking for updates: Release URL: https://www.awesomeminer.com/download/setup/ReleaseInfo.xml, Dev URL: https://www.awesomeminer.com/download/setupdev/ReleaseInfo.xml
08/01/2019 20:02:32.832 [001] [S]Current Version: 6.0.9
08/01/2019 20:02:32.832 [001] [S]New Version: 6.0.5.0
08/01/2019 20:02:32.832 [001] [S]Requires Version: 0.1.4.0
08/01/2019 20:02:33.307 [001] [S]Current Version: 6.0.9
08/01/2019 20:02:33.307 [001] [S]New Version: 6.0.10.0
08/01/2019 20:02:33.307 [001] [S]Requires Version: 0.1.4.0
08/01/2019 20:02:33.307 [001] [S]Development version update available: 6.0.10.0
08/01/2019 20:02:33.307 [001] [S]Check for updates, dev: True
08/01/2019 20:02:34.855 [001] [S]Downloading file http://www.awesomeminer.com/download/setupdev/AwesomeMiner.msi to C:\Users\Damien\AppData\Local\AwesomeMiner\AwesomeMiner.msi
08/01/2019 20:02:34.857 [001] [S]Downloading file: http://www.awesomeminer.com/download/setupdev/AwesomeMiner.msi?u=70952531
08/01/2019 20:02:40.651 [001] [S]Copy file to: C:\Users\Damien\AppData\Local\AwesomeMiner\PE.Launcher.exe
08/01/2019 20:02:40.652 [001] [S]Copy file to: C:\Users\Damien\AppData\Local\AwesomeMiner\IntelliBreeze.Maintenance.Service.Contracts.dll
08/01/2019 20:02:40.653 [001] [S]Copy file to: C:\Users\Damien\AppData\Local\AwesomeMiner\PE.Infrastructure.ServiceModel.dll
08/01/2019 20:02:40.654 [001] [S]Copy file to: C:\Users\Damien\AppData\Local\AwesomeMiner\PE.Infrastructure.dll
08/01/2019 20:02:40.655 [001] [S]Copy file to: C:\Users\Damien\AppData\Local\AwesomeMiner\PE.Infrastructure.Windows.dll
08/01/2019 20:02:40.656 [001] [S]Upgrade launcher parameters: 1696, C:\Program Files (x86)\Awesome Miner\AwesomeMiner.exe, C:\Users\Damien\AppData\Local\AwesomeMiner\AwesomeMiner.msi, restartService:
08/01/2019 20:02:40.712 [001] [S]CoreContext received event for Shutdown
08/01/2019 20:02:40.712 [001] [S]Shutdown: Save statistics
08/01/2019 20:02:40.749 [001] [S]ChannelFactoryProvider: Channel closed
08/01/2019 20:02:40.749 [001] [S]ChannelFactoryProvider: Channel closed
08/01/2019 20:02:40.749 [001] [S]ChannelFactoryProvider: Channel closed
08/01/2019 20:02:40.749 [001] [S]Shutting down timer
08/01/2019 20:02:40.750 [001] [S]Request to close Main Window
08/01/2019 20:02:40.806 [001] [S]Shutdown: Save configuration
08/01/2019 20:02:40.806 [001] [S]Wait for Save Thread to terminate
08/01/2019 20:02:40.879 [003] [S]Saving configuration to: C:\Users\Damien\AppData\Roaming\AwesomeMiner\ConfigData.xml.tmp
08/01/2019 20:02:54.749 [001] [S]Log Initiated
08/01/2019 20:02:54.097 [001] [S]Mode: Non Portable mode
08/01/2019 20:02:54.105 [001] [S]Loading configuration from: C:\Users\Damien\AppData\Roaming\AwesomeMiner\ConfigData.xml
08/01/2019 20:02:54.726 [001] [S]Configuration file created: 09/08/2018 03:49:53
08/01/2019 20:02:54.746 [001] [S]Starting Awesome Miner 6.0.9
08/01/2019 20:02:54.746 [001] [S]Starting time UTC: 08/01/2019 19:02:54 |
|
|
|
Thanks for letting me know. I will take a look at this one as the latest version may have introduced some API changes. The plan is to support the new NBMiner version in the next release. I was just trying out version 12.2 and it shows the hashrate correctly. If version 12.2 isn't working for you, could you please send me the API report for it (via the toolbar Tools -> API Report). Thanks! Works fine again with version 12.2. Problem fixed ! |
|
|
|
Hi patrike,
I'm experiencing an issue mining with excavator through AM.
I'm using excavator 1.4.4a, with the "default_command_file.json" included it works well.
With AM it worked fine but not anymore, no regard how much GPU I select in benchmark or wich algorithm or wich pool I choose, I always got this
It looks like Awesome Miner think you are using Excavator 1.5, as it will try to connect to "nhmp.eu.nicehash.com:3200". It might be the detection in Awesome Miner isn't perfect for this scenario. Do you want to use 1.4 or is 1.5 an option? I prefer keeping 1.4 version so I can use any server and not only nicehash's one. Would it be possible in the next update to split Excavator 1.4 and 1.5 or to add an option to tell AM wich version of excavator is working on the miner ? Thx |
|
|
|
Hi patrike,
I'm experiencing an issue mining with excavator through AM.
I'm using excavator 1.4.4a, with the "default_command_file.json" included it works well.
With AM it worked fine but not anymore, no regard how much GPU I select in benchmark or wich algorithm or wich pool I choose, I always got this
It looks like Awesome Miner think you are using Excavator 1.5, as it will try to connect to "nhmp.eu.nicehash.com:3200". It might be the detection in Awesome Miner isn't perfect for this scenario. Do you want to use 1.4 or is 1.5 an option? I prefer keeping 1.4 version so I can use any server and not only nicehash's one. |
|
|
|
Hi patrike, I'm experiencing an issue mining with excavator through AM. I'm using excavator 1.4.4a, with the "default_command_file.json" included it works well. With AM it worked fine but not anymore, no regard how much GPU I select in benchmark or wich algorithm or wich pool I choose, I always got this =========================== www.nicehash.com =========================
Excavator v1.4.4a_nvidia GPU Miner for NiceHash.
Copyright (C) 2018 NiceHash. All rights reserved.
Developed by
djeZo, dropky, voidstar, and agiz
with help and contributions from
zawawa, pallas, Vorksholk, bitbandi, ocminer, and Genoil.
=========================== www.nicehash.com =========================
Build time: 2018-02-16 13:11:25
Build number: 4645
Provided startup commandline:
"C:\Users\MINEUR\AppData\Local\AwesomeMinerService\UploadedSoftware\excavator\excavator.exe" -c awesome.json -p 4028
[05:05:15][0x00000fc0][info] Log started
[05:05:15][0x00000fc0][info] core | Found CUDA device: GeForce GTX 1080 Ti
[05:05:16][0x00000fc0][info] core | Found CUDA device: GeForce GTX 1080 Ti
[05:05:16][0x00000fc0][info] core | Found CUDA device: GeForce GTX 1080 Ti
[05:05:16][0x00000fc0][info] core | Found CUDA device: GeForce GTX 1080 Ti
[05:05:16][0x00000fc0][info] core | Found CUDA device: GeForce GTX 1080 Ti
[05:05:16][0x00000fc0][info] core | Found CUDA device: GeForce GTX 1080 Ti
[05:05:16][0x00000fc0][info] api | Listening on 127.0.0.1:4028
[05:05:16][0x00000fc0][info] core | Initialized!
[05:05:19][0x000007d4][warning] core | Command exec: invalid stoi argument
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
[05:05:19][0x000007d4][warning] core | Command exec: device or resource busy: device or resource busy
The awesome.json file generated in excavator folder look like this [
{"time":0,"commands":[
{"id":1,"method":"subscribe","params":["nhmp.eu.nicehash.com:3200","my.btc.address"]}
]},
{"time":1,"commands":[
{"id":1,"method":"algorithm.add","params":["equihash"]}
]},
{"time":3,"commands":[
{"id":1,"method":"worker.add","params":["equihash","0"]},
{"id":1,"method":"worker.add","params":["equihash","1"]},
{"id":1,"method":"worker.add","params":["equihash","2"]},
{"id":1,"method":"worker.add","params":["equihash","3"]},
{"id":1,"method":"worker.add","params":["equihash","4"]},
{"id":1,"method":"worker.add","params":["equihash","5"]},
{"id":1,"method":"worker.add","params":["equihash","6"]},
{"id":1,"method":"worker.add","params":["equihash","7"]},
{"id":1,"method":"worker.add","params":["equihash","8"]},
{"id":1,"method":"worker.add","params":["equihash","9"]},
{"id":1,"method":"worker.add","params":["equihash","10"]},
{"id":1,"method":"worker.add","params":["equihash","11"]},
{"id":1,"method":"worker.add","params":["equihash","12"]}
]},
{"time":10,"loop":10,"commands":[
{"id":1,"method":"worker.print.speed","params":["0"]},
{"id":1,"method":"worker.print.speed","params":["1"]},
{"id":1,"method":"worker.print.speed","params":["2"]},
{"id":1,"method":"worker.print.speed","params":["3"]},
{"id":1,"method":"worker.print.speed","params":["4"]},
{"id":1,"method":"worker.print.speed","params":["5"]},
{"id":1,"method":"worker.print.speed","params":["6"]},
{"id":1,"method":"worker.print.speed","params":["7"]},
{"id":1,"method":"worker.print.speed","params":["8"]},
{"id":1,"method":"worker.print.speed","params":["9"]},
{"id":1,"method":"worker.print.speed","params":["10"]},
{"id":1,"method":"worker.print.speed","params":["11"]},
{"id":1,"method":"worker.print.speed","params":["12"]},
{"id":1,"method":"algorithm.print.speeds","params":["0"]}
]}
] I don't understand why there's this "invalid stoi argument" Thanks ! |
|
|
|
|
