Jump to content
Flirc Forums
Sign in to follow this  
shddroc

Can't get repeat to work with Flirc V2 and Verizon P265 remote (some buttons)

Recommended Posts

Holding remote's arrow button down invokes repeated presses on STB.

Doing the same with Flirc (checking via GUI debug window and Kodi) does not. Only get single event.

However, the volume button (which remote maps to TV's volume code) does repeat.

Flirc 2.0 dori

FW: 4.4.2

Verizon remotes: P265v3.1, P265v5

 

flirc_p265_1button_log.txt

flirc_p265_arrow_log.txt

Share this post


Link to post
Share on other sites

Can you record the arrow button again, but this time hold it longer? Because the log file for the arrow key contains only a single signal. Then post the new log file.

Share this post


Link to post
Share on other sites

Thanks for the reply.

Flirc GUI Device Log w/Enable IR Debugging only shows 1 event even when holding arrow down for 10 secs (log attached). No event registered when button released.

However, the Fios DVR (model QIP7232) detects multiple keypresses. Example: in DVR's EPG, holding down arrow will continuously move down the channels.

The remote is setup such that the Volume button maps to the TV's volume control (i.e. TV's remote code for volume). This is a feature of the remote.

Flirc does detect multiple of that button (log attached).

Thanks for the help.

flirc_p265_arrow10secs_log.txt

flirc_p265_arrow5secs_then_volume_log.txt

Share this post


Link to post
Share on other sites

Tried 2nd Flirc running FW 4.3.0

It behaves the same with same looking logs (single event on press, no event on release).

Appears all buttons destined for QIP STB, flirc does not detect multiple presses (but STB does).

Buttons mapped to TV (vol, separate TV power button on remote) do generate multiple flirc detections.

Share this post


Link to post
Share on other sites

Your TV uses NEC signals. These are well known and work well with Flirc.

On the other hand your STB probably uses G.I.Cable protocol. If I'm right the remote should produce one full frame (the one you see) and then multiple short frames (called ditto frames), which should all look like this (real values can oscillate a little around these values):
0,8820,2205,490

NEC1 also uses ditto frames for repeats (but for NEC1 the timings are different) and Flirc supports them properly. Theoretically it should be possible to support that but I don't know why you don't see these in the log.

Share this post


Link to post
Share on other sites

The remote is very common in the US. It was supplied by many of the cable TV providers (Verizon, Time Warner, etc).

I believe Motorola makes the QIP STBs. I have seen some forum posts mentioning they often use G.I. (apparently Motorola bought GI).

The remote is designed to control the STB (most buttons) and then allow user to enter their TV code to program  a few buttons (volume, etc) to their specific TV.

Example of remote:

https://www.amazon.com/Verizon-FiOS-Replacement-Remote-Control/dp/B00ARLKW8M/ref=cm_cr_arp_d_product_top?ie=UTF8

https://www.verizon.com/home/accessories/media/images-accessories/productPDF/P265_brochure.pdf

Definitely not seeing ditto codes in the debug log. Not getting multiple presses when using flirc on rpi running lirc/kodi/etc either.

Could flirc fw may be filtering the GI ditto codes? Any way to debug further?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×