Notice: This forum has been recovered from an old backup, so some content, links, and dates may be outdated. The forum is currently read-only while we restore sign-in and registration functionality. Details

If you find this forum valuable and would like to help keep it online, donations to help cover hosting and domain costs are greatly appreciated, but never expected. You can support the forum through Buy Me a Coffee or Ko-fi. Thank you for helping preserve the EventGhost community.

EventGhost / UDPSender / CMD Communication

Questions and comments specific to a particular plugin should go here.
Post Reply
MuadDib
Posts: 4
Joined: Thu Sep 29, 2011 4:08 pm

EventGhost / UDPSender / CMD Communication

Post by MuadDib »

I am trying to get my USB-UIRT working after my need has grown for an additional settop box. Currently, I have a HDPVR already installed on my WHS 2011 box and it is performing great. However, as many know, you cannot install the MCE ir blaster :x because there are no signed drivers that supports a WHS 2011 installation. I have tried all kinds of methods that were said to be successful in a limited capacity on the server 2008 64 platform. Also, another limitation is you cannot have more than one internal blaster operating concurrently. :x

So my only recourse is to install and try to get working the complicated mess better known as USB-UIRT with Hooks because support is not integrated in DVBLink. :x

So far I have installed the USB-UIRT without any complications. I modified my CMD and I think it is good to go. I placed the udpsender in the appropriate directory that is called from CMD. I also have the ir codes for USB-UIRT that will work with my VIP 1200 boxes, obtain via sagetv forum. Lastly, I installed event-ghost and setup actions for USB-UIRT transceiver and broadcaster but I don't know how I should configure the aforementioned actions to get everything communicating.

Can some help with this? Or at a minimum can someone posts some screen captures of their eventghost setup so I can get an idea of what to do next? In other words, I don't know what I should do with the USB-UIRT action in eventghost and I don't know what I should do with the broadcaster action within eventghost.
MuadDib
Posts: 4
Joined: Thu Sep 29, 2011 4:08 pm

Re: EventGhost / UDPSender / CMD Communication

Post by MuadDib »

Still no joy...can anyone help?
piert
Experienced User
Posts: 321
Joined: Tue Jun 14, 2011 2:53 pm

Re: EventGhost / UDPSender / CMD Communication

Post by piert »

I think you need to explain your configuration better.

Is the computer that you are using near your tv and set top boxes?
Are the settop boxes the same and near each other (in which case you should create separate signal paths for each)
Are you using a standard remote or programmable one?

I do not understand why you would need UDP sender in your set-up. As far as I know, this is only needed if you want to broadcast between different PC's?

As general process explanation: add an USB-UIRT action within eventghost. You can then either copy and paste the ir codes or learn the appropriate command if you have the remote. After you have done this, you can now execute the new command. You place this action inside a macro (that you have to rename appropriately for the command) which you then can trigger using different methods. The methods include any action from your pc, but also ir signals that you send to your USB-UIRT receiver.
MuadDib
Posts: 4
Joined: Thu Sep 29, 2011 4:08 pm

Re: EventGhost / UDPSender / CMD Communication

Post by MuadDib »

I fixed it.

Thanks for your comment but had I waited I would have had a angry wife and kids.

The internet ain't what it use to be.
piert
Experienced User
Posts: 321
Joined: Tue Jun 14, 2011 2:53 pm

Re: EventGhost / UDPSender / CMD Communication

Post by piert »

Glad you worked it out.
MuadDib wrote:I fixed it.

Thanks for your comment but had I waited I would have had a angry wife and kids.

The internet ain't what it use to be.
I think you are right.

Then again, I also recall the days of early internet when people posted back they had fixed a problem themselves, thus avoiding other people spending time unnecessarily that they could have devoted to solving somebody else's problem (on time).... :wink:

Best regards,
Perry
Post Reply