Yes you can fix this by adding a powered USB hub (wifi and bluetooth dongle), but now you need to provide power to the hub, Pi, drive motors in a mobile configuration.
I think a WiFi dongle should be ok powered from the Pi Zero itself w/o a powered hub, all you need is an adapter from MicroUSB to "normal" USB.
This is true but if you also want to use a PS3 game controller to interface to a mobile robotic then you also need an additional USB port for a bluetooth dongle. Another gotcha with a PS3 game controller is that it must be "wired" (USB) to the device in order to pair it. Once paired you can disconnect the "cord" and talk to the Bluetooth dongle. So now you need 3 USB ports.
You don't have the 7.6 BOINC installed which is available in Stretch. You also seem to have a more up to date kernel than mine (I have 4.1.7). Are you sure you aren't running Jessie (the stable release)?
So my Kickstarter reward C.H.I.P. ARM board has finally arrived and I'm burning it in with some E@H BRP tasks (needless to say).
The idea of a US$ 9 computer has lost some appeal since its Kickstarter campaign was started, as there is now the Raspberry PI Zero for $5 . However, the CHIP thingy has better connectivity via the integrated WiFi and Bluetooth module, and a very cool keyboard and display shield, plus a ready-to-use audio interface.
I currently run a 3 board RPI2 "Cluster" which made me really interested in the Zero. At first, all hope seemed lost for getting many of them and getting them networked together to start crunching without significant expense and complication, but I came across a concept recently that make it a no-brainer to try (I also plan on going to a 5-board PI2 cluster).
You can turn the Zero in to a USB Ethernet Gadget! What this does is allow you to have a single "master" Zero connected to a USB hub with whatever peripherals you care about (keyboard/mouse/wifi/ethernet, etc) and as many OTHER Pi Zero boards as you have ports. The USB Ethernet Gadget basically turns the Zero in to a virtual networking device. This means that all communication and network access for the "Slave" Pi Zeros happens through the master over USB. The best part is that when a Zero is in gadget mode, it gets power through the USB port as well, so you only need the hub.
I'm currently experimenting with BOINC on the Zero with 100% CPU allocation - have hit a few snags including the machine becoming unresponsive overnight with no known cause (the CPU temp in my office is hovering around 43C). I have also had logsysd runaway as a process this evening causing the CPU time to get split between E@H and logsysd.
I'm assuming that there's no reason to try and calculate fftw wisdom for it because it's already built in? I seem to remember something about this.
Yes, wisdom is build in and should be reasonably good. There has been some work on GPU FFT reported here but nothing production-ready yet. It would indeed make some sense for the Zero running headless, I guess.
Meanwhile my C.H.I.P. (after some troubles with a poor power supply) has returned it's first valid result:
RE: RE: Yes you can fix
)
This is true but if you also want to use a PS3 game controller to interface to a mobile robotic then you also need an additional USB port for a bluetooth dongle. Another gotcha with a PS3 game controller is that it must be "wired" (USB) to the device in order to pair it. Once paired you can disconnect the "cord" and talk to the Bluetooth dongle. So now you need 3 USB ports.
If you're running Debian
)
If you're running Debian Stretch on your Rpi's you will notice that this week saw a libc6 update. It breaks the 1.06 BRP4 app.
You'd be running 1.06 on the older Rpi's (A, B and B+). The 1.47 app seems to work fine on the Pi2 with the latest libc6.
BOINC blog
RE: The 1.47 app seems to
)
My Pi produced many Errors with the NEON Beta App! :-(
Since a couple of Days.
https://einsteinathome.org/host/12037419/tasks
Greetings from the North
RE: RE: The 1.47 app
)
You don't have the 7.6 BOINC installed which is available in Stretch. You also seem to have a more up to date kernel than mine (I have 4.1.7). Are you sure you aren't running Jessie (the stable release)?
BOINC blog
...yes I'm running on
)
...yes I'm running on Jessie, did I something not seen in the Last couple of Weeks?
Greetings from the North
RE: ...yes I'm running on
)
Stretch is the testing release so it regularly gets updates. They seem to be updating GCC/C++ at the moment.
BOINC blog
So my Kickstarter reward
)
So my Kickstarter reward C.H.I.P. ARM board has finally arrived and I'm burning it in with some E@H BRP tasks (needless to say).
The idea of a US$ 9 computer has lost some appeal since its Kickstarter campaign was started, as there is now the Raspberry PI Zero for $5 . However, the CHIP thingy has better connectivity via the integrated WiFi and Bluetooth module, and a very cool keyboard and display shield, plus a ready-to-use audio interface.
https://einsteinathome.org/host/12165343
Cheers
HB
I currently run a 3 board
)
I currently run a 3 board RPI2 "Cluster" which made me really interested in the Zero. At first, all hope seemed lost for getting many of them and getting them networked together to start crunching without significant expense and complication, but I came across a concept recently that make it a no-brainer to try (I also plan on going to a 5-board PI2 cluster).
https://learn.adafruit.com/turning-your-raspberry-pi-zero-into-a-usb-gadget/overview
You can turn the Zero in to a USB Ethernet Gadget! What this does is allow you to have a single "master" Zero connected to a USB hub with whatever peripherals you care about (keyboard/mouse/wifi/ethernet, etc) and as many OTHER Pi Zero boards as you have ports. The USB Ethernet Gadget basically turns the Zero in to a virtual networking device. This means that all communication and network access for the "Slave" Pi Zeros happens through the master over USB. The best part is that when a Zero is in gadget mode, it gets power through the USB port as well, so you only need the hub.
I'm currently experimenting with BOINC on the Zero with 100% CPU allocation - have hit a few snags including the machine becoming unresponsive overnight with no known cause (the CPU temp in my office is hovering around 43C). I have also had logsysd runaway as a process this evening causing the CPU time to get split between E@H and logsysd.
I'm assuming that there's no reason to try and calculate fftw wisdom for it because it's already built in? I seem to remember something about this.
What about utilizing the GPU to speed as referrenced here:
https://www.raspberrypi.org/blog/accelerating-fourier-transforms-using-the-gpu/ Did this already get implemented in the E@H code?
My YouTube Channel: https://www.youtube.com/user/KF7IJZ
Follow me on Twitter: https://twitter.com/KF7IJZ
RE: I'm assuming that
)
Yes, wisdom is build in and should be reasonably good. There has been some work on GPU FFT reported here but nothing production-ready yet. It would indeed make some sense for the Zero running headless, I guess.
Meanwhile my C.H.I.P. (after some troubles with a poor power supply) has returned it's first valid result:
https://einsteinathome.org/task/538989308
Same ballpark, performance-wise, as the PI Zero would be, maybe a tiny bit faster.
HB
RE: Meanwhile my C.H.I.P.
)
Here is a task that my Zero has returned. Running Jessie Lite.
https://einsteinathome.org/task/539870898
My YouTube Channel: https://www.youtube.com/user/KF7IJZ
Follow me on Twitter: https://twitter.com/KF7IJZ