JP1 Remotes

Is it anyone out there that can explain to me how to convert this ?

I have a Vision VTB100 tuner, se site http://www.visiontech.com.tw/products/vtb100.html

The problem is that my pronto NG receives some ir code but the tuner will not respond to the ir code when i send it from the pronto. Works fine with the original remote.

Some samples for the PENG GUI:

Channel up:
900A 006D 0000 0001 02FD 13EC
Channel down:
900A 006D 0000 0001 02FD 0FF0
On/off:
900A 006D 0000 0001 02FD 0EF1
Menu:
900A 006D 0000 0001 02FD 06F9

I have sent a request to the manufacturer i recived this list:
0x0E: Power //power
0x58: PCVideo //PC <==> VIDEO
0x4C: Source //Source Select
0x1A: Mode //Display Resolution change VGA<==>XGA
0x12: Display //display message
0x16: Sleep //Sleep
0x50: Band //Air or Cable
0x07: Mute //mute
0x0b: Vol+ //volume up
0x47: Vol- //volume down
0x04: MTS //Sound System Select
0x06: Menu //OSD Menu
0x44: Up Arrow //Up
0x1D: Dn Arrow //Down
0x1C: Left Arrow //Left
0x48: Right Arrow //Right
0x5C: Enter //Enter
0x1E: Exit //OSD Menu / Information Exit
0x4F: 0 //0
0x10: 1 //1
0x11: 2 //2
0x51: 3 //3
0x0C: 4 //4
0x0D: 5 //5
0x4D: 6 //6
0x08: 7 //7
0x09: 8 //8
0x49: 9 //9
0x4B: 100 //100
0x13: Ch+ //channel up
0x0F: Ch- //channel down
0x43: CH RTN //channel return
0x54: Autoscan //TV tuner auto scan
0x42: Finetune- //tuner fine tune -
0x0a: Finetune+ //tuner fine tune +
0x02: CH Add //tuner channel add
0x40: CH Erase //tuner channel erase
0x05: Favorite //tuner favorite channel
0x45: Fav. Set //tuner favorite channel set
0x17: red key //Teletext R
0x14: green key //Teletext G
0x15: yellow key //Teletext Y
0x55: blue key //Teletext B
0x1B: TTX On/Off //Teletext ON/OFF
0x18: Reveal //Teletext Reveal
0x19: Page- //Teletext PAGE Down
0x59: Page+ //Teletext PAGE Up
0x03: Surround //Surround
0x00: Loudness //Loudness
0x01: Static //Static De-Interlace Mode
0x41: Sports //Sports De-Interlace Mode

From the code from the pronto it looks like the Vision tuner uses NEC1 protocol, but i do not have the carrier/Hz. Is it possible to read it form the PENG code or hex code that i received for the manufacturer ?

Are there any tools that will do this ?

Thanks

I think you're in the wrong forum. I think the right forum is:
http://www.remotecentral.com/cgi-bin/mb ... g/list.cgi

So far as I understand the NG Prontos learn and store the frequency (represented by that 006D in your learned signals) as accurately for NEC1 signals as for any other type. Then they ignore the frequency they learned and stored and use the default NEC1 frequency instead.

Sometimes an NEC1 signal is learned but won't reproduce correctly because of that frequency problem. But 006D is the default NEC1 frequency, so that doesn't seem to be the problem in this case. So I don't have a good guess.

Unless Rob jumps in to say I've misunderstood forum topics (again) I think any further discussion of this should move to a better forum.

If I'm reading the data correctly, this signal is NEC1 with a device code of 2. My only suggestion is that you could use John's MakeHex program to generate regular Pronto hex and see if that works instead.

I know nothing about the NG Prontos and I don't have any suggestion as to why the 900A signals wouldn't work.

The Robman wrote:If I'm reading the data correctly, this signal is NEC1 with a device code of 2.

Correct.

The Robman wrote:My only suggestion is that you could use John's MakeHex program to generate regular Pronto hex and see if that works instead.

No good. MakeHex generates clean signals in 0000 format. Pronto Edit NG recognizes clean NEC1 signals in 0000 and changes them to 900A format, which gets you right back to what you already have.

Got a mail from the manufacturer, my device uses NEC with 37.9 KHz.

Also got an explanation for Vishay Telefunken on the NEC/RC5 protocol, i can post it on the yahoo group if anyone have interest reading the document. The person mentions the their remote uses Custom Code: 0x02FD, could that be the device code of 2 that The Robman mentions in his post ?

I have used makehex, I'll test the code when i get home.

oagers wrote:Got a mail from the manufacturer, my device uses NEC with 37.9 KHz.

That is the default frequency for NEC. That's the frequency used by over 90% of the devices using NEC protocol. That's the frequency represented by the 006D in your learned signal. And that's the frequency a 900A format signal would use regardless of its learned frequency.

oagers wrote: Also got an explanation for Vishay Telefunken on the NEC/RC5 protocol, i can post it on the yahoo group if anyone have interest reading the document.

It wouldn't hurt to post it, but NEC and RC5 are totally unrelated protocols and I expect we know more about both of them then the experts at Vishay do. There is some small chance that they use a distorted form of the NEC protocol, such as the one we call NECx, and that the Pronto NG ignored the distortion and incorrectly translated to 900A format. In that case their document would tell us what to put in an .irp file for MakeHex to generate correct 0000 format signals that PENG wouldn't translate. But I don't really expect that. I expect ordinary NEC with no explanation why the 900A form didn't work.

oagers wrote: The person mentions the their remote uses Custom Code: 0x02FD, could that be the device code of 2 that The Robman mentions in his post ?

Correct.

oagers wrote: I have used makehex, I'll test the code when i get home.

Good luck, but I can't see how it might help.

Now I have tested the codes, but with no luck. It did not work. I post the pdf from Vishay.

Anyone that have solution ? Can it be the NECx code that johnsfine mentions ?

Then the file is posted under Special Protocols, the file is named Vishay_data_formats.pdf

I moved it to the Diagnosis Area:
http://groups.yahoo.com/group/jp1/files ... ormats.pdf

I know the data sheet that you are referring to and IIRC it describes the older NEC1 (where the second data byte must always be the binary complement of the first) and the older RC5 protocol that was limited to 64 commands. Nonetheless, your commands look like they meet the the more restrictive case described in the Vishay document.

Since few if any people here have a ProntoNG, the advice here will be pretty limited. IIRC, the ProntoNG's send out both IR and RF commands and have some sort of RF to IR device that can work remotely. Have you tried these commands just using IR with the Pronto pointed straight at the equipment in the IR mode -- with no RF receiver connected?

If that still isn't working I suspect some sort of framing error. I haven't had many instances of the NEC1 protocol being tricky, but I have had several cases where the gap between frames is very critical.

Since you are in the JP1 world, you could invest ~$35 for a JP1 learning remote and a JP1 cable and learn the commands. The JP1 software (and the OFA remote) quite accurately measure the exact timing and you could with our help compare the same command from the OEM remote to what the Pronto is sending out.

Other than that we have to rely on trying to trick the NG software into behaving correctly. That is, at this point, little more than educated guesswork since we neither know exactly what the OEM remote is putting out nor exactly what then NG is transmitting.

No, I have no RF receiver connected to my pronto.

What about the NEC2 protocol to the MakeHex.exe program, could it work ? What is the difference of NEC1 and NEC2?

Is it possible to manipulate the second data byte so it will work ? If, how ?