NI700 and Philips Pronto
VladaPUB
Posts: 139
I have Ni700 and PhilipsPronto remote controller. I would like to control DVD player that is connected to Com port 1 on Ni700 with Philips Pronto.
Do anyone have code sample, I have found some module, but is does not work.
I have attached that module file that i have.
Do anyone have code sample, I have found some module, but is does not work.
I have attached that module file that i have.
0
Comments
The IR reciever's channel will then show a button_event when you pulse the Pronto. You can have up to 255 channels on the pronto to work with. You'll have to label them whatever you want.
I will warn you that there are a few bad captures on the file. I think I found something like 5-6 that don't work. However, that should be plenty of channels to control a DVD player.
I've done a pretty sophisicated system with both normal AMX touch panels and secondary MX-700 remotes using the same idea. It works pretty well.
However, there are major issues if you're are trying to simultaneously use the NI-700s IR reciever and then pulse the IR emitter on the same NI-700. both devices apparently use the same resources and conflict when you try to use them at the same time. Found this out after driving myself insane troubleshooting the matter.
hope that helps.
ejm
Oh, well that might be pretty simple then. Just create an IP interface within your Netlinx program on the appropriate port and let the Pronto connect to it.
I'm not familiar with the Pronto's abilities (or lack thereof) to communicate over IP. But, if it does it, you should be able to get the Netlinx master to communicate with it.
After looking at the module you sent, it seems pretty straight-forward. You'll get a button push from the virtual device in the module when it gets a button push from the Pronto. The buttons are a 1 to 1 correspondence. ex. button 21 on the Pronto will equal button 21 on the virtual device.
Definitely more possibilities then the iPronto.
Kevin D.
Can you post a sample code, or just part of code ?
I'm going to guess that you haven't declared the module.
in your code you'll want to these things in the correct parts of the code.
You need to add the module to the project. You do this by right-clicking on the Module folder in the Workspace manager window. select 'Add existing module' from the drop menu. Browse to the module file called Pronto_Module and import it to the project.
If you get a good complile you're now ready to program for the pronto.
I'm not sure what setup you'll have to do with the Pronto itself. My guess is that you'll have to tell the Pronto to look for the IP address of the Netlinx master since it seems to need to initiate the conversation.
Once everything is talking, you should see button pushes on the Pronto as button pushes on the virtual device.
,
So let's assume you make buton number 101 on the Pronto a play button for a DVD player.
BUTTON_EVENT[vdv_Pronto,101] // play dvd { PUSH: { // CODE TO MAKE THE DVD PLAY } }There's also something I noticed in the module you may want to change.
I'd change the line below
to
dvMASTER 0:1:0
The example above assumes you are making the Master's system number '1'. You may or may not be. If you change it to '0' it'll work for whatever your system number may be.
Hope this helps
e
Kevin D.
Like I said, I do not know anything about the Pronto side of things in this situation. If I were you I'd scour the Remote Central site and see if you can cull anything about it there. From what I see in the AMX module, it doesn't look too difficult. The communication protocol seems to be pretty simple.
Sorry...
Ricardo
Are you sure that?s an accurate statement, Eric? IR in and IR out are different port numbers and the limitation you cited does not exist according to good folks at AMX.
Is it possible the IR device you tried to control got flooded with the AMX IR codes sent by the handheld remote and the native device IR codes sent by the NI-700 at the same time causing your IR device to freak out?
I?ve seen that happen before, the last time was with a Yamaha YSP-1000. The YSP was unresponsive when it saw the AMX IR codes and its native IR codes at the same time. As soon as the eye of the Yamaha was out of site so that it couldn?t see the AMX IR codes sent by the handheld remote, all was fine.
I've also run into the same situation but using the old AXR-ISRM+ boxes. I was using a Pronto with AMX IR codes to talk to the master, which then sent the IR code back to the TV. Single commands worked fine, but push-hold events like volume ramping simply wouldn't work. Drove me crazy, to the point where I just put the volume control codes directly on the Pronto and bypassed the AMX.
Joe
I've covered the IR receiver on the TV set and placed the AMX receiver around the corner and it still gives me the problem. It really seems like the master can't receive and pulse IRs at the same time.
Joe
DEFINE_DEVICE //NI-700 dvSonyRecvr = 5001:3:0 //IR out to Sony STG-DG810 receiver dvRemote = 5001:5:0 //IR RX from MX-850 remote DEFINE_EVENT BUTTON_EVENT[dvRemote,1] { PUSH: { TO[dvSonyRecvr,24] //ramp volume up } } BUTTON_EVENT[dvRemote,2] { PUSH: { TO[dvSonyRecvr,25] //ramp volume down } }It did not always fail. One thing that we seemed to figure out is that it was worse depending upon the rates of the IR files.
I may not be correct for the purpose of this thread, but I seem to remember the AMX IR file and the ComCast cable box as having a similar or close flash rate. However, in one room we were doing an older Runco plasma that had a rate in the 50s. That seemed to cause lots of problems.
And, as I said, Jon and Steve at AMX were working with me and were able to reproduce the problem in Dallas. It's something they're aware of.
Also, concerning the eye being in line, the Runco was wired IR. There was no IR emmitter involved.
Edit: Forgot the word not.
That's all well and good. But it still doesn't explain the wired IR on the display. you can turn off the IR eye in the front of the panel so it is not even in the picture. So, unless the IR light photons can run around the back side of the display and magically turn themselves into elctrons and create enough current to interfere with the incoming electricity I don't see how IR interference can be discussed.
Another little clue is that the Red LED indicator of IR activity on the NI-700 is significantly darker when what I'm describing occurs.
I'm not sure why tech support is throwing me under the bus on this occasion. I did have the discussions with them and I document what we talk about every time I call. It's part of our process here. I'm not sure why someone would infer that I'd lie about such a thing. But, alas and anon.
The original module converted pronto actions into button presses, but I thought this was a bit of a waste of time as the pronto can be used to send string commands to the controller. The controller can then act on the strings, a bit like responding to a device.
I've just set it up so when the AMX test page is accessed the pronto asks AMX to update the text on a panel on the pronto. It does this by sending the command 'UD-Radio' when the page is accessed. The controller then sends a string to the pronto with the info for that panel.
This is just playing really, but if it helps anyone to start writing integration then good stuff!