Raspberry Pi Forums

rgh

There is a version of ServoBlaster for testing on this thread:

http://www.raspberrypi.org/forums/viewt ... 5&start=25

Reported working by a couple of people.

Richard

rgh

I've attached a version of ServoBlaster that works for me on a Pi2B, please test and report back. I've fixed it by using the mailbox interface to request memory from the VC, like the GPU FFT stuff Dom pointed to does. This much cleaner than what I was doing before and works on rev 1 and rev 2 for me...

rgh

Hi Michael, If you are running Raspbian and you run rpi-update, you will hopefully end up with this kernel: [email protected] ~ $ cat /proc/version Linux version 3.12.22+ ([email protected]) (gcc version 4.7.2 20120731 (prerelease) (crosstool-NG linaro-1.13.1+bzr2458 - Linaro GCC 2012.08) ) #690 PREE...

rgh

I have a more modern binary kernel module available as well as the Panalyzer ui program itself if you're interested; both of those in the current github project do not run on the current raspbian. Thanks, I'll rebuild and push to github myself when I get time - I'm sure your binaries are fine but I...

rgh

edb wrote:Hi Richard I did figure this out - in your original demo_3d.cpp you call...

Thanks very much for the fixes! One day I'll find time to merge them in to github.

Richard

rgh

New version pushed to github: You can now specify the step increment, in case 10us wasn't want you wanted. You can specify a cycle time other than 20ms, which might be useful if driving LEDs and you don't like the 50Hz flicker. You can specify pulse widths in microseconds or as a percentage, as an a...

rgh

JohnneyBoy wrote:Hello,

I looked like I needed to update the kernel source .config file with a valid one, the driver now compiles.

Just need to test it....

John

Joan is correct, the kernel space driver is depreciated and you really should use the userspace servod.c one instead (ServoBlaster/user/servod.c).

rgh

Zeryk wrote: when sudo insmod servoblaster.ko then Error: could not insert module servoblaster.ko: Invalid module format

Please see the README in the github repository, and use the user space servod implementation, not the kernel space servoblaster.ko implementation.

Richard

rgh

I understand why you would want that; to provide it I'd have to rewrite a file containing the data for every servo position update; maybe that's ok, provided its on a RAM file system - I wouldn't want servod to start blocking just because the SD card was busy, for example. I'll think about it some m...

rgh

BTW quick question: is it going to be possible to read /dev/servoblaster of userspace implementation? No, because the user space implementation is not really a device driver in the usual sense of the word and /dev/servoblaster is a FIFO, not a device node. Your code writes to that FIFO, and servod ...

rgh

Further updates, as requested by clicky :-) As an alternative command syntax you can now specify header pins rather than servo numbers when writing to /dev/servoblaster. For example, if you have a servo connected to P1 pin 16, you could set it to mid position with "echo P1-16=150 > /dev/servoblaster...

rgh

Note the driver needs to know which pins are to be used for servos, so it can program them as outputs on startup. So, if you want to use a P1-4=<width> sort of syntax "'P1-4" would only be valid if either P1-4 was one of the default pins, or if you'd specified it in a --p1-pins= parameter. Anyway, i...

rgh

You can in fact map the servo numbers to the P1 header pins already. In this example I have four servos connected to P1 pins 7, 11, 12, and 15, and I refer to them as servos 7, 11, 12 and 15 when writing to /dev/servoblaster: [email protected] ~ $ sudo ./servod --p1pins=0,0,0,0,0,0,0,7,0,0,0,11,12,0,0,...

rgh

I pushed another servod.c update to github at https://github.com/richardghirst/PiBits/tree/master/ServoBlaster . ServoBlaster will now drive up to 21 servos (or 17 on a Rev 1 board), rather than just 8. It will also now let you specify pulse widths from 0 to 20ms (20ms is the cycle time, so that is ...

rgh

I also provided servodebug.c along with the servoblaster source. You need to read the code to see how to use it, but it should tell you if servoblaster is generating pulses.

rgh

I just pushed an update to https://github.com/richardghirst/PiBits/tree/master/ServoBlaster , which: Adds an option to servod to automatically turn off servo pulses some time after the last update (e.g. "sudo ./servod --idle-timeout=2000" will turn off pulses after 2000ms, or 2 seconds). Fixes servo...

rgh

That's OK. Its not motion that I am using, sorry for the confusion. It is your python script that I just happened to name it motion :-) Such a shame that it doesn't work. I might get onto the maker of servoblaster, might have a different insight perhaps? Thanks again!!! Hi, there are two implementa...

rgh

Hi, how would you recommend accessing your servod driver from C? I use something like this: static void set(int servo, int position) { char buf[32]; int fd; sprintf(buf, "%d=%d\n", servo, position); if ((fd = open("/dev/servoblaster", O_WRONLY)) >= 0) { int n = strlen(buf); if (write(fd, buf, n) !=...

rgh

Sorry Glen, I've got no idea.. all my knowledge came from reading Jeff's code, and I've not explored adding a HMC5883L.

rgh

@mikkov: That looks about right to me; I must get round to adding an option to invert outputs. You are not the first that has wanted it.

rgh

Would it be possible to generate a "multiplexed" signal? I'd like to connect to a RC transmitter that expects the PPM signal which is all 8 servo channels sent over one wire with a pause after the 8th channel. I was hoping it was possible since the Pi has one PWM pin. Yes, I think that would be qui...

rgh

Worked first time, just like it said in the readme. Very nice. Do you have any plans to prompt the official RaspPi kernel to add this to their build? I'm sure doing a rebuild every time there is a new kernel is going to get old very fast. Thanks. The new servod implementation is a simple user space...

rgh

One last thing.... even when I play an audio file from the command line ie sudo aplay 12345.wav the servos buzz/vibrate uncontrollably and go into an invalid state as described above. See this post... you need to try "sudo ./servod --pcm" http://www.raspberrypi.org/phpBB3/viewtopic.php?f=37&t=15011...

rgh

Forris wrote:I've written my first bit of real-world Python and my son is now showing an interest in my new toy.

Excellent! That's what it is all about

rgh

I may have misread the code but it seems to be using a PLL rather than the 19.2MHz osc? That's correct; PLLD is 500MHz (regardless of whether or not you overclock). I guess you could equally use the 19.2MHz osc, but I find the math easier if I start with 500MHz :) and it is easier to select a wider...

Search found 211 matches

Re: Pi 2 - Servoblaster, Pi-Blaster etc.

Re: Pi2 B and Pi-Pan (ServoBlaster)

Re: Panalyzer - a RaspberryPi based Logic Analyzer

Re: Panalyzer - a RaspberryPi based Logic Analyzer

Re: Yet more MPU6050 demo code

Re: Driving multiple servos from the RaspberryPi

Re: Driving multiple servos from the RaspberryPi

Re: Driving multiple servos from the RaspberryPi

Re: Driving multiple servos from the RaspberryPi

Re: Driving multiple servos from the RaspberryPi

Re: Driving multiple servos from the RaspberryPi

Re: Driving multiple servos from the RaspberryPi

Re: Driving multiple servos from the RaspberryPi

Re: Driving multiple servos from the RaspberryPi

Re: Check if Servoblaster is actually working

Re: Driving multiple servos from the RaspberryPi

Re: Lightweight python motion detection

Re: Driving multiple servos from the RaspberryPi

Re: Yet more MPU6050 demo code

Re: Driving multiple servos from the RaspberryPi

Re: Driving multiple servos from the RaspberryPi

Re: Driving multiple servos from the RaspberryPi

Re: Driving multiple servos from the RaspberryPi

Re: Driving multiple servos from the RaspberryPi

Re: Driving multiple servos from the RaspberryPi