2021-01-25, 07:11 PM
ok, my winLIRC config file?
NextPVR Forums
Public
NextPVR Support
Legacy (v4.x and earlier)
send channel chanes via winLIRC??
send channel chanes via winLIRC??
|
2021-01-25, 07:14 PM
The config file you configured and entered in the Remote Configs dialog in WinLIRC
Martin
2021-01-25, 07:33 PM
(This post was last modified: 2021-01-25, 07:33 PM by mvallevand.)
Ok I feel there are two issues with that file, first you told me that you saw KEY_1 etc but it seems you don't even have the KEY_ prefix.
Then the remote name is wrong for some reason it has the full path we were talking using Starsat I'd do extra testing to make sure every key works for WinLIRC Code: # Please make this file available to othersMartin
2021-01-25, 08:00 PM
yea, sorry, i just assumed based on your drake.ps1 that you were using "key_1" 0r "key_0" etc in the Winlirc config file, whereas mine are just "0" or "1" etc which i didn't specify when creating the config file, so i removed "key_" from my drake.ps file thinking that would be ok.
Wierdly, the "manual" blasting from WinLIRC itself does work for each digit individually, even with my config file being so f*cked up! However, i've just foud a "starsat 120" config file (different model of stb but same brand) in the LIRC remote archives. (actually i'd seen it before but dismissed it as being the wrong stb model number.) It has the correct structure with "key_" for each remote key, (eg "key_0" etc) and a Remote name that doesn't innclude file path. (TBH at this point, I don't even know how/why my config has a file path instead of a remmote name there). It also has the same/'very similar codes for each of the numerical digit keys (1 & 0 are slightly different), so i'm wondering wether i should try this as my WinLIRC config instead. The file i found reads as: # # this config file was automatically generated # using WinLIRC 0.6.5 (LIRC 0.6.1pre3) on Sun Oct 16 04:58:37 2005 # # contributed by # # brand: StarSat # model: 120 # supported devices: # begin remote name Starsat_120 bits 16 flags SPACE_ENC eps 25 aeps 100 header 9040 4397 one 641 1595 zero 641 469 ptrail 641 repeat 9023 2161 pre_data_bits 16 pre_data 0x202 gap 46721 toggle_bit 0 begin codes KEY_POWER 0x50AF # Was: Power KEY_MUTE 0x30CF # Was: Mute TV/SAT 0xF00F Read 0x6897 Sabz 0xE817 Yellowe 0x18E7 Bule 0x9867 KEY_1 0x807F # Was: 1 KEY_2 0x40BF # Was: 2 KEY_3 0xC03F # Was: 3 KEY_AUDIO 0xC837 # Was: Audio KEY_4 0x20DF # Was: 4 KEY_5 0xA05F # Was: 5 KEY_6 0x609F # Was: 6 KEY_TEXT 0x28D7 # Was: Text KEY_7 0xE01F # Was: 7 KEY_8 0x10EF # Was: 8 KEY_9 0x906F # Was: 9 KEY_EPG 0x58A7 # Was: EPG KEY_TIME 0x48B7 # Was: Time KEY_0 0x00FF # Was: 0 Media 0xB847 LAN 0xD827 KEY_UP 0xD02F # Was: UP KEY_DOWN 0x708F # Was: Down KEY_LEFT 0x08F7 # Was: Left Ritgh 0x8877 KEY_OK 0xB04F # Was: OK KEY_VOLUMEUP 0xA857 # Was: VOL+ KEY_VOLUMEDOWN 0x38C7 # Was: VOL- KEY_CHANNELDOWN 0x7887 # Was: CH- KEY_CHANNELUP 0xF807 # Was: CH+ KEY_MENU 0x02FD # Was: MENU KEY_EXIT 0x827D # Was: Exit KEY_I 0x42BD # Was: i KEY_AGAIN 0xC23D # Was: RCL A-Z 0x22DD KEY_SAT 0xA25D # Was: Sat FUNC 0x629D KEY_FAVORITES 0xE21D # Was: FAV # >^ 0xD02F end codes end remote # # regression-test: skip # (Don't remove this comment used by lirc-codec-regression-text.sh) (I dont know why it says "# Was: 1" and "# Was: FAV" etc after some of the keys, but as they're hashed out im guessig theyr'e irrelevant)
2021-01-25, 08:04 PM
If the file works from the WinLIRC dialog the choice is yours. I like the look of their 0 and 1 better which is why I wanted you to test the keys.
You would have to use Starsat_120 as the name in the script. Martin
2021-01-25, 08:20 PM
even with the Starsat_120 config file (which blasts ok from winLIRC), i still can't get a succesful blast from command line. honestly don't know what i'm doing wrong at this point. Out of curiosity does your winLIRC blast from command prompt?
thanks
2021-01-25, 08:23 PM
Using my powershell script yes I can send IR codes from the command line if that is what you mean. The IR flashes and I see the corrects codes being received.
Martin
2021-01-25, 08:43 PM
(This post was last modified: 2021-01-25, 08:46 PM by chef Paula.)
Actually, i just meant wether or not you can access WinLIRC from command line and make it blast, as i presumed that if i could do that then your script would work from within Next PVR, BUT, i set powershell.exe as the blaster executable in Next PVR, set the argument to:
"-File C:\winLIRC\Drake.ps1 {channel_d1} {channel_d2} {channel_d3} {channel_d4}" changed the remote name in drake.ps1 to match mine (after replacing my remote config file in WinLIRC completely with the one from the web), and Voila, ... I now have working blasting from within Next PVR.  (I still can't do any of the above from command line, but i don' t care!) I CAN CHANGE CHANNEL ON MY NEW STB!!!!!! You Mr Mvalleland are a genius! (and i might add very patient too) Thank you a million times!!
2021-01-25, 08:53 PM
(This post was last modified: 2021-01-25, 08:56 PM by chef Paula.)
THAT SAID, lol, it seems to be blasting 4 times, is it as simple as just taking out the {channel_d4}? (my channel numbers are all 3 digit anyway)
|
|
|
