@joe: "Does anybody know of a good resource for setting up my IR Blaster within
FreeBSD?
I think I have a good lircd.conf with information about my remote, but
I'm sure I'm missing some information about how to get the kernel
modules I'll need to generate my /dev/lirc0.
Perhaps this might be a better question for a different FreeBSD list?
Just thinking about you guys since many seem to know the score in
getting MythTV setups to work...
Joe Auty
NetMusician: web publishing software for musicians
<url>
<email_address>
_______________________________________________
<email_address> mailing list
<url>
To unsubscribe, send any mail to "<email_address>"
Posted automagically by a mail2news carol70@example.org e.V.
Please direct questions, flames, donations, etc. to <email_address>"
    @antonstamenov: "for freebsd the lirc socket is not in /dev/ but in /var/lirc/lircd,
and almost all port software knows where to find it.
I've managed to set it up with my pinnacle serial remote, but I had
to patch the lirc port's Makefile in orther to include support for this
remote. I don't know if your hardware is supported... 
<quote>
___________
anton
_______________________________________________
<email_address> mailing list
<url>
To unsubscribe, send any mail to "<email_address>"
Posted automagically by a mail2news carol70@example.org e.V.
Please direct questions, flames, donations, etc. to <email_address>"
    @joe: "<quote>
Well, I have no idea about the FreeBSD end of things, but I do have a
good lircd.conf for my satellite box. Others have gotten it to work,
I've confirmed this. The only thing I'm not sure of is the extent of the
FreeBSD support and how FBSD factors into this mix?
I tried using /dev/ttyd0 since it just plugs into a serial port (I
bought one of of <url> I can do a:
# lircd -n device=/dev/ttyd0 /usr/local/etc/lircd.conf
lircd: lircd(dvico) ready
Does this confirm anything of value?
Cool! Would you like some suggestions for your guide?
Joe Auty
NetMusician: web publishing software for musicians
<url>
<email_address>
_______________________________________________
<email_address> mailing list
<url>
To unsubscribe, send any mail to "<email_address>"
Posted automagically by a mail2news carol70@example.org e.V.
Please direct questions, flames, donations, etc. to <email_address>"
    @antonstamenov: "This is how I start lircd serever
lircd -H pinsys -d /dev/cuad0 -p 644
I compile it with pinsys support (this is my remote), not with irman
(as in ports).
When started it will create the sockets. lirc need the same stuff as
in linux, except that not all drivers that are supported under linux
are ported in freebsd. 
<quote>
___________
anton
_______________________________________________
<email_address> mailing list
<url>
To unsubscribe, send any mail to "<email_address>"
Posted automagically by a mail2news carol70@example.org e.V.
Please direct questions, flames, donations, etc. to <email_address>"
    @scrappy: "-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- On Wednesday, March 14, 2007 16:11:17 +1030 Greg 'groggy' Lehey 
<quote>
Is there a list somewhere of which ones are?  I'd love to buy one for my "PVR" 
so that I don't have to use the keyboard all the time like now ... make it a 
bit more 'intuitive' for the wife to watch too :)
- 
Marc G. Fournier           Hub.Org Networking Services (<url>
Email . <email_address>                              MSN . <email_address>
Yahoo . yscrappy               Skype: hub.org        ICQ . 7615664
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (FreeBSD)
iD8DBQFF+ID14QvfyHIvDvMRAoWzAJ9nzIsPXO6ZpFth5AQD/hoCkmPjeACfSSds
hSpOVqt4W7JBPn9hECSzGCA=
=vfuO
-END PGP SIGNATURE-
_______________________________________________
<email_address> mailing list
<url>
To unsubscribe, send any mail to "<email_address>"
Posted automagically by a mail2news carol70@example.org e.V.
Please direct questions, flames, donations, etc. to <email_address>"
    @joe: "-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
<quote>
Okay, I think I know where this conversation is breaking down... please
correct me if I'm wrong.
My understanding is that there is two ways to change channels, one via
RF, and one via infrared.
I believe with cable and satellites that are RF based, changing channels
is as simple as sending a command line instruction to your capture
card/tuner. I think this is how discussion of remote controls came into
the picture in trying to issue commands to your tuner.
In my case, this part is covered. I own a MediaMVP which accepts
commands from my Hauppauge remote. I need an IR Blaster connected to my
FreeBSD box so that I can simulate the infrared signal sent by my
satellite remote so that I can send commands back to my satellite box to
change channels.
To do this, I have read that I need an IR Blaster, and I need to use
LIRC to mediate communication with my IR blaster. I also need a change
channel script which will interface with the Myth backend.
The piece I'm missing is getting LIRC listening on a device node so that
it can communicate with my IR Blaster connected to my serial port.
Am I completely out-to-lunch here in how I'm interpreting this conversation?
- 
Joe Auty
NetMusician: web publishing software for musicians
<url>
<email_address>
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (Darwin)
Comment: Using GnuPG with Mozilla - <url>
iD8DBQFF+IpSCgdfeCwsL5ERArA/AKCDRyfqJ/dUxq0vg4TRBtIjLSCPJQCeJP7f
YKLoy+M/7dwPug0+2i0jhz4=
=IF/f
-END PGP SIGNATURE-
_______________________________________________
<email_address> mailing list
<url>
To unsubscribe, send any mail to "<email_address>"
Posted automagically by a mail2news carol70@example.org e.V.
Please direct questions, flames, donations, etc. to <email_address>"
    @joe: "Hi Anton,
Could you do me a quick favor, and read my last post in this thread and
in light of my setup, tell me whether what you wrote (quoted below)
applies to me? If so, I have follow up questions...
I don't mean this in a confrontational way at all, I just want to feel
comfortable in knowing the score and having a handle over what my
problem is and what I need to accomplish. Throwing the issue of remotes
into the mix is making me less confident in my understanding, because I
had believed that this isn't a concern for me.
For your convenience, and possibly to illuminate further, here is my setup:
Satellite signal -> Satellite box -> Hauppauge card -> MediaMVP (via
Ethernet) run off of the MVPMC hack (<url> that provides a
Mythfrontend for the MediaMVP box which communicates with my Myth
backend hosted on FreeBSD -> TV
All of this is working fine, but in order for me to be able to change
channels with my FreeBSD box, I need an IR Blaster to simulate my
satellite remote control. I'm trying to use LIRC as a means for my
FreeBSD box to communicate with my IR Blaster to send the proper signals
to my satellite box.
This basically seems to amount to:
1) Getting LIRC installed
2) Finding a configuration file that contains the appropriate specs to
simulate my remote/satellite box (there are a ton of sample
configurations that can be downloaded, which I did)
3) Using LIRC to control/send signals to the IR Blaster
Where I'm at is that I've created my lircd.conf file with the
information about my satellite box, I have lirc installed from ports
(default build options), and I'm trying to get LIRC communicating with
my IR Blaster. I don't seem to have it installed correctly, and I'm at a
loss to know where to turn to for help, I can't find much online.
I'm able to do this:
# lircd -n device=/dev/ttyd0 /usr/local/etc/lircd.conf
lircd: lircd(dvico) ready
I'm not really sure what this feedback means though, nor do I know what
path the socket is written to.
Is this clear and/or helpful?
<quote>
Joe Auty
NetMusician: web publishing software for musicians
<url>
<email_address>
_______________________________________________
<email_address> mailing list
<url>
To unsubscribe, send any mail to "<email_address>"
Posted automagically by a mail2news carol70@example.org e.V.
Please direct questions, flames, donations, etc. to <email_address>"
    @joe: "-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
<quote>
Ahhh... so getting a remote to work involves remote-specific OS support
beyond just grabbing a good lirc.conf? I thought that lirc was simply a
protocol, and would speak to any IR receiver using the frequencies and
configuration included within its config file?
Would you like to see my lircd.conf? I'm fairly certain it is correct,
but I'd be more than happy to pass it on for your inspection.
Unfortunately, I guess I can't really change the remote I'm trying to
emulate, right?
I'll add my commentary once I've completed my setup here. I think I'm
going to kill off my MediaMVP deal and sell it on eBay, and just use the
OS X frontend for scheduling recordings. The only missing piece is being
able to change channels so that I don't have to remember to preset my
satellite to the correct channel prior to a recording.
- 
Joe Auty
NetMusician: web publishing software for musicians
<url>
<email_address>
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (Darwin)
Comment: Using GnuPG with Mozilla - <url>
iD4DBQFF+NHYCgdfeCwsL5ERAnFSAJ4xKeqSABFFobxhuCGEWNIiakTlGACYw+oL
eUf0F/f7wTYRWFebNqxb1g==
=AEQp
-END PGP SIGNATURE-
_______________________________________________
<email_address> mailing list
<url>
To unsubscribe, send any mail to "<email_address>"
Posted automagically by a mail2news carol70@example.org e.V.
Please direct questions, flames, donations, etc. to <email_address>"
    @torfinningolfsen: "On Wed, 14 Mar 2007 19:50:42 -0400
<quote>
I *think* that the problem is related to the fact that IR Blasters are
using the serial port in a non-standard way.
Instead of using the Tx signal to transmit data, they are using the DTR
signal. This page seems to support that view:
<url>
Thus, you need a special driver for the serial port which allows it to
work in this way. It is probably a year or two since I looked at it,
but the problem then was that LIRC's "driver" for serial ports was
totally Linux-specific, not very clean code, and not easy to port over
to FreeBSD. So nobody did make a LIRC serial port driver for FreeBSD .
See also /usr/ports/comms/lirc/pkg-message
So, either you need to write a "LIRC driver" for serial piorts under
FreeBSD, or you need to get a "IR Blaster" type device that doesn't use
the serial port, AND is spported both by FreeBSD and LIRC, if such
devices exists.
HTH
Regards,
Torfinn Ingolfsen,
Norway
_______________________________________________
<email_address> mailing list
<url>
To unsubscribe, send any mail to "<email_address>"
Posted automagically by a mail2news carol70@example.org e.V.
Please direct questions, flames, donations, etc. to <email_address>"
    @antonstamenov: "I don't have deep knowledge about remotes and infrared and lirc, what
I can help is to show my success story. 
My dongle, is also serial, and there is a serial driver for lirc under
freebsd. I'm using it. My setup is little bit oposite, I have a
FreeBSD box which is setup as media box and I controll different
multimedia (not only) stuff on this box using my remote. I'm watching
TV, using one old Pinncle PCTV Pro card which is well supported under
FreeBSD. 
<quote>
___________
anton
_______________________________________________
<email_address> mailing list
<url>
To unsubscribe, send any mail to "<email_address>"
Posted automagically by a mail2news carol70@example.org e.V.
Please direct questions, flames, donations, etc. to <email_address>"
    @akm: "+-[ Torfinn Ingolfsen ]
| On Wed, 14 Mar 2007 19:50:42 -0400
| 
| > The piece I'm missing is getting LIRC listening on a device node so
| > that it can communicate with my IR Blaster connected to my serial
| > port.
| 
| I *think* that the problem is related to the fact that IR Blasters are
| using the serial port in a non-standard way.
| Instead of using the Tx signal to transmit data, they are using the DTR
| signal. This page seems to support that view:
| <url>
| 
| Thus, you need a special driver for the serial port which allows it to
| work in this way. It is probably a year or two since I looked at it,
| but the problem then was that LIRC's "driver" for serial ports was
| totally Linux-specific, not very clean code, and not easy to port over
| to FreeBSD. So nobody did make a LIRC serial port driver for FreeBSD .
You don't really "send" or "receive" data to and from IR devices.
You don't really need a driver, you just need to be able to strobe the control
line at the right frequency, in the right burst lengths. You can do it from userland 
if you need to.
The serial drivers for LIRC simply monitor the relevant pin and decode the
incoming data. You can do this in userland, without needing a lirc kernel
module to watch the serial port.
The reason they use the control lines instead of tx/rx is that you don't need
to be concerned with baud settings on the port.
Andrew Milton
<email_address>
_______________________________________________
<email_address> mailing list
<url>
To unsubscribe, send any mail to "<email_address>"
Posted automagically by a mail2news carol70@example.org e.V.
Please direct questions, flames, donations, etc. to <email_address>"
    @freebsd: "<quote>
Last time I looked (a few weeks ago) LIRC wasn't even close to being
64 bit clean.  And there are reports of LIRC not working even on
32 bit Linux.
Isn't there an alternative to LIRC?  If not, perhaps a summer of code
idea?  (Either fix LIRC or start a new program that works.)
_______________________________________________
<email_address> mailing list
<url>
To unsubscribe, send any mail to "<email_address>"
Posted automagically by a mail2news carol70@example.org e.V.
Please direct questions, flames, donations, etc. to <email_address>"
    @joe: "-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
<quote>
control
from userland
don't need
Cool, so this is just a matter of software configuration then? Any
ideas how I can setup LIRC to do this?
- 
Joe Auty
NetMusician: web publishing software for musicians
<url>
<email_address>
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (Darwin)
Comment: Using GnuPG with Mozilla - <url>
iD8DBQFF+rzoCgdfeCwsL5ERAg2hAJ4nlb50QgV1t+FQxaNwPVtmtXf/jwCgn5Uq
wmoTYwhLZjJ57Jtuqyen2sM=
=d+mX
-END PGP SIGNATURE-
_______________________________________________
<email_address> mailing list
<url>
To unsubscribe, send any mail to "<email_address>"
Posted automagically by a mail2news carol70@example.org e.V.
Please direct questions, flames, donations, etc. to <email_address>"
    @akm: "+-[ Joe Auty ]
| 
| Cool, so this is just a matter of software configuration then?
You need some strobing code.. this is assuming you don't have something neat like
a niveus IR blaster.
| Any
| ideas how I can setup LIRC to do this?
For your device that you want to send to, you need to know two things (other
than the codes).
Pulse width, and the carrier frequency.
The pulse usually consists of an on then an off period,
so a '1' is an on/off period, and a '0' is an all off period.
 +-+
 |   |
-+   +-+
 |   |   |   |   |
 |-  1  -|-  0  -|
OK, now inside the part of the pulse that's high, you need to strobe the
correct control line at the carrier frequency. These are normally in the 
range of 37Khz - 40Khz for consumer infrared.
You need to find out the remote codes for your device, there's plenty of
remote sites out there that have CCF files or whatever (if there's no LIRC
config that has them), that should give you what you need to send.
Once you have that you simply set up your lirc config to run your 'send' app
when ever it receives your incoming button and tell it to send the write code. 
You can also then use this to directly send commands to it etc from the
commandline or whatever.
I used to have code to handle all this (as well as an IR receiver app that had
dvico USB receiver code, it had a LIRC output mode, so that applications that
used the LIRC lib could work with it). I had a look on a few DLT cartridges,
but, I can't find it. I basically had learnt codes for heaps of remotes that I
had lying around, TV Remotes, DVD Remotes, XBOX, PS2. I guess I should make a
better effort to find it.
It's not really rocket science to build a receiver / sender system. The
"hard" problem is if you want to learn codes from remotes in some sane fashion.
Andrew Milton
<email_address>
_______________________________________________
<email_address> mailing list
<url>
To unsubscribe, send any mail to "<email_address>"
Posted automagically by a mail2news carol70@example.org e.V.
Please direct questions, flames, donations, etc. to <email_address>"
{'source': 'USENET', 'other_information': '{"reply_count": 13, "forum_name": "muc.lists.freebsd.multimedia.20140618.mbox"}', 'file': 'data/output/usenet-muc.lists.parquet'}