Topic: The official MacMiner thread [BTC/LTC-CPU/GPU/FPGA/ASIC] - page 17. (Read 166698 times)

I've had a quick scan around and as far as I can tell it's not running cgminer or bfgminer which is the type of API output it's looking for, BUT if you add

--http-port 8330

to manual flags in the fpga/asic window settings panel where the number is the port you've set up as the pool port on the Cube, then you can use MacMiner instead of slush's stratum proxy and I would assume that then the stats will show up in MacMiner - I'd be very interested to hear how it goes!

Hey BitBacco, does the networked miner feature support ASICminer's Cube? I can't tell if I'm doing something wrong (likely), or if it's an issue with that device.

The Fabulous Panda Pool is moving to a new server today, the change will take a little while to take effect and in the meantime you may see unexpected stats on the pool site - if you'd like to switch to the new server manually without waiting for the change to take effect you can set up with your primary pool as

http://78.46.18.222:9332 for BTC or :9327 for LTC

But there is no need to act on the news, the move will take care of itself and the work from the old server counts towards the work on the new server. The old server will continue to operate for a few days after the move. Thanks everyone who's using it! The pool website will be improved drastically over the coming days/weeks following on from the MacMiner website improvements.

will do, thanks nwoolls!

Sure thing. I've noted it and will have to think about the best way to handle this.


Can you PM me with a curl equivalent of what you are POSTing so that I can post it myself and step through the server-side code? Probably the fastest way to figure out what's going on.

No problem, I'm glad you've done all the hard work for me! At this point you can advertise it, I still haven't implemented the controls but it won't be long now. I've been using it for a day or so now and it seems stable.

I just had a couple of issues actually, one is more of a knc problem leading to a feature request - the 5s average hash is always over 33% higher than the total average so the representation in MobileMiner shows a speed much higher than reality - would it be possible to set which average to display, or to display one by the other?

Also, in the odd circumstances of development I fed my account fake machines and devices testing the mechanism and deleted a bunch but now I can't get the devices I deleted back in the devices list - even when removing a machine and letting it show up again - anything that can be done about that?

I truly appreciate you supporting the MobileMiner API. Would you consider this at a point stability and feature wise where I can advertise support? I'd like to link to MacMiner from the MobileMiner homepage as well as tweet about the update.

Version 1.5.2 is up now but not replacing the download links for 1.5.1 until I've tested it a little bit more.

This update:

-Allows CGMiner window to feed the API Output window

-Allows the API Output window to function for your network miner regardless of whether you're mining on the machine running MacMiner

-Allows networked miners in API Output window to feed MobileMiner

-Removes spell-check lines from log views

http://downloads.fabulouspanda.co.uk/MacMiner.app-1.5.2.zip

the version 1.5.1 that's up has been updated to a b build to address a bug with setting up without entering a BTC address for backup pools

Not a KNC but it'll show in the next version, sorry about that!

Oh, OK, didn't know that!
So a networked miner showing up in the API Output window doesn't count?

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

Doesn't seem to work here… I signed up with MobileMiner and entered the application key in the iOS MobileMiner app and the MacMiner app but MacMiner doesn't show up in the iOS app.
Am I missing something?

Ya I'm not sure, I know its listed as device BF1 but with all the icarus errors, I cannot seem to find where it initially probes for the device.. just seems to start accepting from BF1 intermingled with all the icarus and bitforce errors.

I'll just wait it out, doesn't seem as though things are being affected!.. Thanks for all the help.

It's not one of those. It should show up in the logs when you start the miner though? In any case you can ignore it if you like and I'll get bfgminer fixed up to work for you in the next release in a day or two!

hmm.. ..all that is listed is below. I assumed the bluetooth things are what say they are…
and the usbserial are my jalapenos, and the others are the BEs…

Anyways the Bitfury is running at avg of ~2.5gh/s so it seems to be working.

crw-rw-rw-  1 root    wheel      18,  47 18 Dec 10:50 /dev/cu.Bluetooth-Modem
crw-rw-rw-  1 root    wheel      18,  49 18 Dec 11:02 /dev/cu.Bluetooth-PDA-Sync
crw-rw-rw-  1 root    wheel      18,  41 18 Dec 11:02 /dev/cu.Bluetooth-Serial-1
crw-rw-rw-  1 root    wheel      18,  43 18 Dec 11:02 /dev/cu.Bluetooth-Serial-2
crw-rw-rw-  1 root    wheel      18,  55 18 Dec 13:36 /dev/cu.SLAB_USBtoUART
crw-rw-rw-  1 root    wheel      18,  57 18 Dec 13:36 /dev/cu.SLAB_USBtoUART28
crw-rw-rw-  1 root    wheel      18,  59 18 Dec 13:36 /dev/cu.SLAB_USBtoUART29
crw-rw-rw-  1 root    wheel      18,  61 18 Dec 13:36 /dev/cu.SLAB_USBtoUART30
crw-rw-rw-  1 root    wheel      18,  63 18 Dec 13:36 /dev/cu.SLAB_USBtoUART31
crw-rw-rw-  1 root    wheel      18,  65 18 Dec 13:36 /dev/cu.SLAB_USBtoUART32
crw-rw-rw-  1 root    wheel      18,  73 18 Dec 13:36 /dev/cu.SLAB_USBtoUART36
crw-rw-rw-  1 root    wheel      18,  75 18 Dec 13:36 /dev/cu.SLAB_USBtoUART37
crw-rw-rw-  1 root    wheel      18,  77 18 Dec 13:36 /dev/cu.SLAB_USBtoUART38
crw-rw-rw-  1 root    wheel      18,  79 18 Dec 13:36 /dev/cu.SLAB_USBtoUART39
crw-rw-rw-  1 root    wheel      18,  81 18 Dec 13:36 /dev/cu.SLAB_USBtoUART40
crw-rw-rw-  1 root    wheel      18,  83 18 Dec 13:36 /dev/cu.SLAB_USBtoUART41
crw-rw-rw-  1 root    wheel      18,  85 18 Dec 13:36 /dev/cu.SLAB_USBtoUART42
crw-rw-rw-  1 root    wheel      18,  87 18 Dec 13:36 /dev/cu.SLAB_USBtoUART43
crw-rw-rw-  1 root    wheel      18,  89 18 Dec 13:36 /dev/cu.SLAB_USBtoUART44
crw-rw-rw-  1 root    wheel      18,  91 18 Dec 13:36 /dev/cu.SLAB_USBtoUART45
crw-rw-rw-  1 root    wheel      18,  93 18 Dec 13:36 /dev/cu.SLAB_USBtoUART46
crw-rw-rw-  1 root    wheel      18,  95 18 Dec 13:36 /dev/cu.SLAB_USBtoUART47
crw-rw-rw-  1 root    wheel      18,  97 18 Dec 13:36 /dev/cu.SLAB_USBtoUART48
crw-rw-rw-  1 root    wheel      18,  99 18 Dec 13:36 /dev/cu.SLAB_USBtoUART49
crw-rw-rw-  1 root    wheel      18,  67 18 Dec 13:36 /dev/cu.usbserial-FTWINKIX
crw-rw-rw-  1 root    wheel      18,  69 18 Dec 13:36 /dev/cu.usbserial-FTWMMYGN

No problem, if it's working I understand not wanting to touch it! It should show up something like /dev/cu.usbmodem3a21 do you have something like that in /dev/ ?

Hi Bitbacco, sorry about the delay, I left the office once my stick was finally running in a cgminer window.

What is it that you needed me to do?

I am still having problems with specifying the bitfury device to cgminer, I cannot identify it from the list.

Anyways let me know if there was still some information you would like to see from my end.
Thanks

1.5.1 just released adds support for MobileMiner

I use -S all with BE and BFL together OK - from nwoolls post it looks as though specifying them by group works so if nothing else I can update MacMiner to work around that - I was going to just add a 'use all devices' button but I suppose a button for each group wouldn't hurt.

I did try specifying a device individually though, just a BFL box and no luck with the little fury driver enabled - I suppose it needs to know the type of device it's connecting to.