Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

strange behavior runnig headless #73

Open
yanoschik opened this issue Jul 7, 2016 · 6 comments
Open

strange behavior runnig headless #73

yanoschik opened this issue Jul 7, 2016 · 6 comments
Labels

Comments

@yanoschik
Copy link

I've run into a strange issue...
Using pi-blaster to control two servos in a camera pan-tilt setup (here). RPi 2 running Raspbian Jessie, Linux raspberrypi 4.4.13-v7+ #894

Everything works fine, except when starting up headless - only in that case, the servos go crazy = a full power spasm. I believe it's the PWM firing up 100%. There is a script that sets a default servo position at startup, and it runs fine as I can see the camera going into position. But in a moment, the servos go nuts and I have to pull the plug as not to fry them :(
When I start up with the monitor connected to HDMI - no problem.
Any ideas why this happens and where/what to investigate further?
Thanks

@penfold42
Copy link
Collaborator

Yes ... And kinda.

We've got the same problem with the rpi_281x library.

My best guessing the timers are set up differently by the firmware depending on the presence or absence of an HDMI connector.

Short term workaround I've heard of but not tried is to plug in a HDMI to micro HDMI adaptor - that's enough to fool it

@yanoschik
Copy link
Author

yanoschik commented Jul 7, 2016

I've tried to plug in an active HDMI->VGA adapter ...bud it did not help :(
(well, but I did not power it up, got it modified for external power because of overloading problems, so I'll try that again later)

@sarfata
Copy link
Owner

sarfata commented Jul 7, 2016

We are not sure how to explain that but could you try with --pcm when launching pi-blaster? This will use a different timing source that seems to work better.

Also can you confirm what version of RaspberryPi you are using?

@sarfata sarfata added the bug label Jul 7, 2016
@yanoschik
Copy link
Author

yanoschik commented Jul 7, 2016

Could you explain a bit more (o refer to) what is and how to use --pcm? I'm not that good with this stuff yet ;) Only managed to google that it might be something regarding PCM/I2S clock for audio...

And it's Raspberry Pi 2 Model B ...I already wrote in the first post.
pi-blaster is launching with reboot as I've used sudo make install

@yanoschik
Copy link
Author

Just a note: it works OK with the powered HDMI->VGA adapter

@yanoschik
Copy link
Author

yanoschik commented Sep 29, 2016

Well, the --pcm option seems to work fine...
It just took a while for me to figure out how to use it :/
I've added a line with DAEMON_OPTS='--pcm' to /etc/default/pi-blaster (as this file was empty in my case, and I did not know at first where and how to pass that argument).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants