Thanks for letting me know! Do you use the API Output window and/or MobileMiner with that btw?
There will soon be buttons added to miner settings panel for specific devices which will take care of the order they need to be added in - Unfortunately with all the recent device additions bfgminer gets a bit confused sometimes looking for miners!
Topic: The official MacMiner thread [BTC/LTC-CPU/GPU/FPGA/ASIC] - page 16. (Read 166698 times)
Can a few people please verify that they're using 1.5.5 successfully please? One user has reported freezing right after starting bfgminer or asic window but I've tested and tested and I know at least one other internet presence is using it fine but I just want to make sure this isn't a widespread issue!
I am currently running in the asic window .. 2 jala 20 USB BE and 1 Red Bitfury
All running very smoothly now.
Only thing is to get everything going I need to be explicit and use
-S bigpic:all -S bfl:all -S Icarus:all
Just a side note, when putting bigpic:all last in the line of arguments, bfgminer didn't detect the bitfury device… not sure about this problem since it works perfect in the order above.
Anyways.. Thanks Bitbacco .. latest version seems very stable to me.
Can a few people please verify that they're using 1.5.5 successfully please? One user has reported freezing right after starting bfgminer or asic window but I've tested and tested and I know at least one other internet presence is using it fine but I just want to make sure this isn't a widespread issue!
MacMiner 1.5.5 totally reworks the API data fetch(es) and allows more than one networked miner to be monitored in the API Output window
I've been very lucky to have the help of a really great programmer named Scott Holben who has made this improvement far quicker in arrival and superior in implementation than it otherwise would have been, totally reworking the api-example.c that's distributed with bfgminer to a more powerful beast altogether which will benefit us all for a long time to come!
Scott is now credited in the About MacMiner section of the app and you can donate BTC for his contribution to the development of MacMiner:
1E4JSbwSvMA2zhrTF1SGpqZBXNyYEei4oY
It's a great pleasure to see MacMiner take a big step towards being a real community driven project!
I've been very lucky to have the help of a really great programmer named Scott Holben who has made this improvement far quicker in arrival and superior in implementation than it otherwise would have been, totally reworking the api-example.c that's distributed with bfgminer to a more powerful beast altogether which will benefit us all for a long time to come!
Scott is now credited in the About MacMiner section of the app and you can donate BTC for his contribution to the development of MacMiner:
1E4JSbwSvMA2zhrTF1SGpqZBXNyYEei4oY
It's a great pleasure to see MacMiner take a big step towards being a real community driven project!
When I was testing I found before the device started receiving data pulling down the MobileMiner display cause it to attempt refresh and if that failed show those settings - we could be on to something here, maybe that means something to nwoolls? Perhaps there's a specific info field that should be updating from MacMiner but isn't - Are you monitoring JUST the network miner? I haven't tested just that yet so I can give that a shot
If you haven't already, I would recommend building in some sort of debug logging that captures the HTTP POST request being sent across and the response. Or use something like Wireshark to capture that.
Unfortunately there's not much I can do other than look server-side and see if data is coming in. From the stats I'm seeing it looks like something in MacMiner is preventing its proper use.
OK, the API data retrieval is about to undergo a big reconstruction so if this isn't fixed by that I'll definitely build in debug logging for this, thanks guys!
When I was testing I found before the device started receiving data pulling down the MobileMiner display cause it to attempt refresh and if that failed show those settings - we could be on to something here, maybe that means something to nwoolls? Perhaps there's a specific info field that should be updating from MacMiner but isn't - Are you monitoring JUST the network miner? I haven't tested just that yet so I can give that a shot
If you haven't already, I would recommend building in some sort of debug logging that captures the HTTP POST request being sent across and the response. Or use something like Wireshark to capture that.
Unfortunately there's not much I can do other than look server-side and see if data is coming in. From the stats I'm seeing it looks like something in MacMiner is preventing its proper use.
I'm sorry my reply is so late, I've been a bit busy in the last days. 
Yes, the API Output window is updating correctly.
I've already did it before posting with no success.
On a side note, on iOS I haven't found a way to check or enter the e-mail address and API key again after they have been set for the first time. I had to delete and reinstall the MobileMiner app to do it. nwoolls, am I missing something?
Yes, I will test it on Mountain Lion and report back.
UPDATE:
I had no success on Mountain Lion (OS X 10.8.5), either.
Yes, it's ASC0.
Hey XFox - so is the API Output window updating OK?
Yes, the API Output window is updating correctly.
Can you just triple check your settings are correct in MobileMiner preferences if so please? Enter them again even if they're right…
I've already did it before posting with no success.
On a side note, on iOS I haven't found a way to check or enter the e-mail address and API key again after they have been set for the first time. I had to delete and reinstall the MobileMiner app to do it. nwoolls, am I missing something?
Do you have a machine running a newer OS you could give it a shot with?
Yes, I will test it on Mountain Lion and report back.
UPDATE:
I had no success on Mountain Lion (OS X 10.8.5), either.
One more thing Xfox, what's the Device name of the Knc, ASC0?
Yes, it's ASC0.
When I was testing I found before the device started receiving data pulling down the MobileMiner display cause it to attempt refresh and if that failed show those settings - we could be on to something here, maybe that means something to nwoolls? Perhaps there's a specific info field that should be updating from MacMiner but isn't - Are you monitoring JUST the network miner? I haven't tested just that yet so I can give that a shot
I'm sorry my reply is so late, I've been a bit busy in the last days.
Yes, the API Output window is updating correctly.
I've already did it before posting with no success.
On a side note, on iOS I haven't found a way to check or enter the e-mail address and API key again after they have been set for the first time. I had to delete and reinstall the MobileMiner app to do it. nwoolls, am I missing something?
Yes, I will test it on Mountain Lion and report back.
UPDATE:
I had no success on Mountain Lion (OS X 10.8.5), either.
Yes, it's ASC0.
Hey XFox - so is the API Output window updating OK?
Yes, the API Output window is updating correctly.
Can you just triple check your settings are correct in MobileMiner preferences if so please? Enter them again even if they're right…
I've already did it before posting with no success.
On a side note, on iOS I haven't found a way to check or enter the e-mail address and API key again after they have been set for the first time. I had to delete and reinstall the MobileMiner app to do it. nwoolls, am I missing something?
Do you have a machine running a newer OS you could give it a shot with?
Yes, I will test it on Mountain Lion and report back.
UPDATE:
I had no success on Mountain Lion (OS X 10.8.5), either.
One more thing Xfox, what's the Device name of the Knc, ASC0?
Yes, it's ASC0.
the 1.5.4 version download has been updated with a bug fix - the original release had a fix for the API Output window when monitoring a network miner where the networked miner data would be fetched when it was being deleted and this caused it's data to stop updating - this new version also includes a fix preventing it from fetching that data before it's finished being written. Sorry about that!
Thanks!
One more thing Xfox, what's the Device name of the Knc, ASC0?
One more thing Xfox, what's the Device name of the Knc, ASC0?
Thanks nwoolls, I don't suppose you have stats for the number of users feeding data from MacMiner?
I'm showing a total of 3 users and 4 machines for MacMiner.
Hey XFox - so is the API Output window updating OK? Can you just triple check your settings are correct in MobileMiner preferences if so please? Enter them again even if they're right… I had trouble testing on a 10.7 VM due to networking issues but I'll sort something out to check on that. Do you have a machine running a newer OS you could give it a shot with?
Thanks nwoolls, I don't suppose you have stats for the number of users feeding data from MacMiner?
Is anyone else using the MobileMiner app with MacMiner?
Thanks nwoolls, I don't suppose you have stats for the number of users feeding data from MacMiner?
Is anyone else using the MobileMiner app with MacMiner?
I should have documented this more and it'll work a lot smoother in the next version once API Output is separated from FPGA/ASIC miner and fed by everything - MobileMiner picks up any GPU or PGA devices that are showing up in API Output window
I still cannot make MobileMiner to work with the API Output window of MacMiner 1.5.4 attached to a KnCMiner networked miner.
Let me know if you need help troubleshooting on the backend Anonymailer.
I should have documented this more and it'll work a lot smoother in the next version once API Output is separated from FPGA/ASIC miner and fed by everything - MobileMiner picks up any GPU or PGA devices that are showing up in API Output window
Hi,
I still cannot make MobileMiner to work with the API Output window of MacMiner 1.5.4 attached to a KnCMiner networked miner.
I tested it on Lion with the firewall off.
MobileMiner is version 1.5.0 on an iPod touch (4th generation) with iOS 6.1.5.
Just to note I carried on that conversation in PMs! For everyone else's benefit - In MacMiner 1.5.4+ you can connect asicminer cubes and blades using --http-port 1234 in FPGA/ASIC window miner settings manual flags where 1234 is the port your asicminer is pointed at - this is an alternative to using Slush's proxy
1.5.4 is just out:
Important bug fix for API Output/MobileMiner users
Upgrade bfgminer and cgminer both to version 3.9
Little Fury driver enabled in bfgminer - this causes a conflict when using -S all with BFL hardware in which case you must use -S bfl:all
1.5.4 is just out:
Important bug fix for API Output/MobileMiner users
Upgrade bfgminer and cgminer both to version 3.9
Little Fury driver enabled in bfgminer - this causes a conflict when using -S all with BFL hardware in which case you must use -S bfl:all
Consider me your guinea pig if you want to test this before release.
And, how do you add the proxy as a device?
And, how do you add the proxy as a device?
Ah I must apologise I've compiled bfgminer without support for --http-port - I'll update MacMiner very soon!
On the plus side, I found out that 'proxy' shows up as a device in MacMiner and you can get the stats for it.
On the plus side, I found out that 'proxy' shows up as a device in MacMiner and you can get the stats for it.
I plopped that line into the manual flags (do I need others? I'm no longer running BEs), and got this back:
[2013-12-24 02:09:37] /Applications/MacMiner.app/Contents/Resources/bfgminer/bin/bfgminer: --http-port: unrecognized option
[2013-12-24 02:09:37] /Applications/MacMiner.app/Contents/Resources/bfgminer/bin/bfgminer: --http-port: unrecognized option
Do I need to kill the proxy first?
[2013-12-24 02:09:37] /Applications/MacMiner.app/Contents/Resources/bfgminer/bin/bfgminer: --http-port: unrecognized option
[2013-12-24 02:09:37] /Applications/MacMiner.app/Contents/Resources/bfgminer/bin/bfgminer: --http-port: unrecognized option
Do I need to kill the proxy first?
All I know is that it's probably something proprietary to asicminer and it's been the same on the older asicminer blade units. I couldn't come across any popular method of monitoring the blades/cubes short of watching the pool! Hopefully bfgminer will show stats rather than just acting as the proxy…
It should be as simple as my previous post though, so just a quick something to test
It should be as simple as my previous post though, so just a quick something to test
Yikes. I'm just ignorant enough to start dicking around with that. I'd love to run it through MacMiner instead of the stratum proxy.
I do know that the Cube is using an internal getwork miner of some sort. Does that change anything?
I do know that the Cube is using an internal getwork miner of some sort. Does that change anything?
Jump to: