We have completed an install using Digital Projections M-Vision CineLED projector in conjunction with a Panamorph lens system. The client is using a RTI T3V with an RP1.
I need the IR discretes of the aspect ratios. I found the serial codes but need them converted to hex.
Can anyone help?

Thanks

Have you tried contacting Digital Projection to see if they have an IR code sheet or if it even has discrete's aspect codes?

I had a look on their site but didn't find any.
[Link: digitalprojection.com]


Cheers
Jason

 I've got a document with their IR codes but it doesnt' have the device ID nor do I know the protocol.  If I had that I can dust off makehex and generate them.

Anyone?

Do you have a learnt hex code you can post?

Can you send me the document? My address is in my profile.

iVision is NEC custom-code: 20DF (Device Number in decimal is 32 or 32.223 both are the same)

I don't think my Universal Remote software will let me see the learned hex. 

That's the only programmable remotes I have.

I think the iVisions are made by Projection Design, and the one I have is not.  Don't know if that will be a factor or not. 

I verified.  I can add hex, but can't see what's there.

What's the best way to capture it?

You need a Pronto/Marantz remote or a RTI learner to capture hex codes...maybe other ways.

Can you send me the IR Code Sheet you have?


Cheers
Jason

A very good way to capture Pronto Hex is the IR Widget, which cost $29.  It captures signals, and can directly export the raw capture as Pronto Hex, or it can decode the IR signals and use MakeHex.dll to export a cleaned up version of the capture.

It uses the free software IRScope.

As an aside (since this thread is in the CI World section of the website) , I think any custom installer who deals in learned signals and remotes which need Pronto Hex should have the IR WIdget (or something similar) in his toolbox.

Thanks for the tip 3FG. Might have to get one of those, saves carrying a Pronto remote around. :)


Cheers
Jason

3FG:  Beautiful.  As often as I run into this need, I've orderend one of those.  Thank you.

Jason:  DPI confirmed the iVision remote will not work with the Mvision+.  (My perception is) because the iVision is sourced (OEM) from PD, and the M's+ come from delta.

And, they (USA ops) did not have the codes, nor the device ID, etc.

I'll get the IR Widget and capture the code.  Look forward to seeign how it does.

Cheers,
Scott

3Fg or anyone:

My irwidget arrived today.  I captured and decoded the signal.  Cool device, thans for the pointer.  I

I can't figure out how to do somethign that I bet is staring me in the face.  I want to get the correct device info to do a full makehex run, but I dont' see how to get the data I need for the IRP file.  Can anyone help?


This is the irp form line:
{37.7k,565,msb}<1,-1|1,-3>(16,-8,A:32,1,^108m,(16,-4,1,^108m)+){A=$609F807F}

Here is my default makehex irp for NEC1.  I can see some of the things I can match up, but as I get near the end I get lost:

=======================
Device=7
Function=0..255

Protocol=NECx2
Frequency=38000
Time Base=564
One=1,-3
Zero=1,-1
Prefix=8,-8
Suffix=1,-78
Default S=D
Form=*,D:8,S:8,F:8,~F:8,_;*,_

=============================
If it helps, here is a exported pronto line:

Protocol=NEC1 Device=6 OBC=1 (Pronto from signal)
0000 006E 0022 0002 0156 00AA 0016 0014 0016 003F 0016 003F 0016 0014 0016 0014 0016 0014 0016 0014 0016 0014 0016 003F 0016 0014 0016 0014 0016 003F 0016 003F 0016 003F 0016 003F 0016 003F 0016 003F 0016 0014 0016 0014 0016 0014 0016 0014 0016 0014 0016 0014 0016 0014 0016 0014 0016 003F 0016 003F 0016 003F 0016 003F 0016 003F 0016 003F 0016 003F 0016 05E3 0156 0054 0016 0E34

I'm more interested in learning how to do it than the answer  ( but I need answer, too).

Thanks,
Scott
 

Oops, posted the wrong .irp sample file.  I think the format I need is:

Device=135.78
Function=57..58

Protocol=NEC
Frequency=38000
Time Base=564
One=1,-3
Zero=1,-1
Prefix=16,-8
Suffix=1,-78
R-Prefix=16,-4
R-Suffix=1,-174
Default S=~D
Form=*,D:8,S:8,F:8,~F:8,_;*,_

Now, How to take this and turn it into that?:

Freq 37692, device 6  IRP line:
{37.7k,565,msb}<1,-1|1,-3>(16,-8,A:32,1,^108m,(16,-4,1,^108m)+){A=$609F807F}



=====================
Is this right?:

Device=6
Function=1..255

Protocol=NEC
Frequency=37692
Time Base=564
One=1,-1
Zero=1,-3
Prefix=16,-8
Suffix=1,-78
R-Prefix=16,-4
R-Suffix=1,-173
Default S=~D
Form=*,D:8,S:8,F:8,~F:8,_;*,_


 

OK, I'm confused on what you need. Perhaps there's too much info being presented. I think that you've learned some signals, and these should be displayed (after you close the 'scope window) as
Freq......Protocol...Device....OBC + more stuff that isn't important right now.
37677...NEC1.........6.........1..
I used your exported Pronto as the template for the above line. All you need is NEC1 (which is different from NEC2 or NECx1 or NECx2)
Device 6
OBC (or Function) 1
You'll probably find that all the learns are NEC1 device 6, with varying OBCs.

If you only want to get a file with the learned signals in Pronto Hex format, just select all the rows of the learned signals, and click Export. Make sure that you have done a Files/Set Folder/Set Export Folder.

To output all 255 possible function numbers, use the MakeHex GUI. Select nec1, Device Main a as 6, leave Sub b blank, Function Start as 0, Function End as 255, and click Make Hex. No messy editing required.

BTW, "NEC1" incorporates almost all of the information on the IRP line, other than A=$609F807F, which is the specific data from that learned signal.

Yes, I did learn some signals with the IR widget.  And Yes, I may be giving too much info.


OK.  I am with you there.  I did find it surprising they just used "6" as the device ID.  I'd think that would be so common as to be a conflict.  All the one's I've done in the past are more unusual pairs.  That threw me off.  Was hiding right in front of my eyes :)


No, I wanted to generate them "clean" from a proper model.  And I wanted to have/check some that aren't on the remote to learn from (possible hidden functions that correlate to their RS232 command set.).


That is exactly what I want to do.  I didn't realize John made a GUI, I always used the command line version.  Been a while since I needed one.  Very nice.


Thank you, I was making it much harder than it should have been. I just figured with only a "6" as the device ID, their must have been some other variant in that code that made it more unique.  I had figured out the A=$xxx was the data.  Or I thought so.  Thank you for confirming.

So, with the spiffy little GUI, and no need to edit the NEC1 irp, and only a device ID to change, I should be good to go.

I'll load some of these up and test.

Thanks very much for the help.

To give credit where it is due, mdavej wrote the GUI. And I didn't mean that you had presented too much information, but rather IRScope is providing more than you need to handle a vanilla NEC signal. Sometime you'll probably run into an IR protocol that isn't classifiable, and in that case some of the other info is a big help to sort it out.