Newbie help (with DVBViewer)

[ovim]

I'm trying to use girder to control DVBviewer, but its not working.

Heres what I did:

I'm using MCE remote, I've installed and started MCE plugin (girder sees buttons being pressed). I've also mapped some basic buttons from the remote.

I've downloaded DVBViewer GML and opened it in girder and assigned my MCE remote to it.

When I press any of the buttons nothing happens in DVBViewer (in foreground window). Also If I use test event (F5) in girder nothing happens. I tried using mapped buttons and also tried "learning" buttons.

What am I doing wrong? Im quessing its some minor detail I've overlooked.

[harryharry]

I have the same problem. I do not manage to get DVBviewer to work with Girder 4. DVBViewer works fine with Grider 3.3

[Benarty]

Same here: Girder4 with the dvbviewer plugin doesn't work.
I use an UIRT which detects the remote fast en learns codes very quick but that's the only thing that works.

None of the keys have an effect on dvbviewer, com interface (dll) added.

I would rather avoid starting from scratch to end up with a non working solution but now it's not avoidable anymore.

Too bad, I have no girder 3.3 and it's not offered as download niether to girder 4 users.

[Benarty]

I've removed Girder4 and installed v3.29 so latest free version.
Installed the girder 1.1 plugin that can be downloaded from the dvbviewer members download section and, the usb UIRT was able to access dvbviewer.

The signal is not stable yet, the UIRT recognizes the remote immediatly and girder acts on the IR signal fast (blinking led icon) but dvbviewer does not act all times but this could be caused by a wrong settings. The UIRT offers a clean signal, so not as simple serial IR receiver where winlirc has to access it as raw coded.

At least more success with v3.29 compared to v4

[Francois]

People,

I'm a bit busy at the moment, but with your help debugging what's going on, I'm sure we could get the Girder 4 plugin to work with DVBViewer (provided it's a recent version such as 3.6, as the fall back mode for DVBV GE is a bit iffy, I must admit)... as it works well for me, and ported well to Girder 5. :D

For starters, could you tell me if there is an error message in the Girder Log, or in the Lua Console when using my plugin with DVBViewer.

Tks

Francois (Eiffel)

[Benarty]

OK, the logger reports:


If I click a key and always the same key then the logger shows most of the time different results on the received signals.
Weird cause the UIRT is hardware based. Latest UIRT drivert used.
Girder 4 fresh installation. Learning key codes is also too fast and the girder stores 2 up to 4 different codes under one key and jumps to the next key , just too fast.

[Benarty]

I've reached now stable results on receiving IR data.


At this point, I've removed all key definitions.
But what I've done now is to test the dvbviewer.gml file with the F5 key
with enabled lua console and logger.


Tried functions:
complex next
complex previous

Logger : : script error:logic error
Lua console: [string "Eifell DVBviewer 3.6.gml\DVB Viewer\DVB V..."]:2:attempt to index global 'VFD' (a nil value)
stack traceback


On key functions channel 0/1/2/3/4 and yellow/green/red:

Logger: Lua success (Nothing triggered)


I'm gonna test again but this time with key definitions of the remote unit.

[Benarty]

OK, reconfigured remote.
IR reception is stable.

Same Lua messages and logger shows always (nothing triggered)

So there is no interaction between girder and DVBviewer.
Only DVBviewer GML file used, so all other gml's removed.
Played a bit with UIRT settings, but still no connection between girder and dvb viewer.

[Francois]

Benarty,

Thank you for your response. The last two postings indicate that there is something wrong with the plugin, or its initialization.

Could you try this updated version of the plugin, and see what kind of results you get if you follow this procedure:

* Load the new plugin,
* Select the 'OnGirderOpen' entry in the Girder tree,
* Press [F5] (To execut the associated scripts)
* Press [F7] (To open the lua console)
* Launch DVBViewer as usual, or select 'Launch DVB Viewer' and press [F5]

If all goes well, you should see text such as this in the console:



Line1 - DVB Viewer
Line2 -
DVBViewer COM connection established
Line2 - BBC News
Line1 - BBC NEWS -00:26 13%
Line1 - BBC NEWS -00:26 13%
...


The first three steps of this convoluted procedure are not needed if you have Girder set to start automatically execute scripts each time it is launched, and if you restart Girder after opening the plugin for the first time.

Let me know how it goes and good luck!

Eiffel

[Benarty]

Could you try this updated version of the plugin, and see what kind of results you get if you follow this procedure:

Updated version of the dvbviewer plugin?
I see only v1.0 on the download page.

Girder is set to automaticly enable scripts.


LUA mentions in line 1 dvbviewer but after that nothing.
The logger shows (nothing triggered) when a key on the remote is selected.

I don't get DVBviewer COM connection established.
I had the com plugin installed ..also latest I could find on dvbviewers website but that was approx 3 weeks ago so I will have to re-check that.

[Benarty]

Ok here latest results:
Installed latest COM plugin for DVBviewer.
Placed the comremote.dll under c:\program files\DVBViewer\Plugins folder
Registered comremote.dll
Started DVB viewer and enabled COM in the settings under section plugins.
The default winlirc plugin disabled.
Closed DVBviewer.


In Girder4:
Logger logs only USB UIRT and remote controller actions.

I switch on the logger and LUA.
I select "on girder open" and press on F5.

Logger reports:

VFD/LCD scripts Lua success (nothing triggered)
VFD Simulator Lua success (nothing triggered)
DVBviewer luacom initialisation Lua success (nothing triggered)

Then I start DVBviewer within Girder..."lauch DVBviewer" hit the F5 key again. DVBviewer starts.

In LUa console : Line 2 - Starting DVBviewer


In the logger:

Start DVBviewer command executed
Window exist DVBviewer? OK: Windows exists
On taskswitch DVBV Lua Success (nothing triggered)
On taskswitch DVBV Lua Success (nothing triggered)
On taskcreate DVBV Lua Success (nothing triggered)
On taskswitch DVBV Lua Success (nothing triggered)
On taskswitch DVBV Lua Success (nothing triggered)
On taskswitch DVBV Lua Success (nothing triggered)
On taskswitch DVBV Lua Success (nothing triggered)
On taskswitch DVBV Lua Success (nothing triggered)

I don't have to press any button , It's clear that dvbviewer will not react on the key strokes. Wrong com plugin settings perhaps, girder plugin problems..or combination...

The com plugin has some test function so will try to see if com on dvbviewer side works properly.

DVBviewer version 3.6.1.20

[Benarty]

I've enabled more girder plugins:
Full list is now:


Audio mixer (sound)
DL port IO extensions
Lua misc function library
Send message
Task create
Task switch
USB-UIRT driver
Windows conditional


Re-tested on same secuances as before resulted in:


Lua:

[string "Eiffel DVBViewer 3.6.gml:\DVBviewer\On Gi..."]:7: bad argument #1 to `sub' (string expected, got nil)
[c]: in function `sub'
[string "Eiffel DVBViewer 3.6.gml:\DVBviewer\On Gi..."]:7: in function `updateLine1'
[string "Eiffel DVBViewer 3.6.gml:\DVBviewer\DVBV...']:2: in main chunk


Logger:
Complex next script error: Logic error (check lua console)

Rest in the logger shows always (nothing triggered)


IR should not cause soo much problems.

[Francois]

Oops, the updated file didn't make it into my latest email...

This may not solve the issues which you seem to experience with your USB-UIRT, but let's first get the DVBViewer pluging to work.

Looking forward to your respons

[Benarty]

I will test this version.

But for those who can not beta test : this is a working solution:

Download latest free version of girder 3.29
Download girder plugin 1.1 from dvbviewer website.
Copy the files from the plugin section into the plugin directory of girder.
Copy dvbviewer.gml to the main directory of girder.
Be sure to use the correct dll for your usb device and copy it to the girder plugin directory.

Start girder and learn all keys.
Remember that a typical key press knows two states.
Or you use the state function of girder or learn for each key the two states.
If you don't do this then you need to press each key twice.
If the remote is too fast, add a delay for each key, typical between 200 and 500 ms.

If you learn a key, keep the button pressed for some seconds and whatch at the bottom of the girder screen to the hexadecimal data that girder shows.
If this hexadecimal number is stable and the same as shown in the saved hexadecimal number in the main screen then it's ok.

If girder keeps on changing that hexadecimal number at the bottom, then that means that th IR reception was not stable enough. In that case, remove the event and re-learn the key.

if too many keys are difficult to learn, choose the function that your remote is not detected in the settings, there pplace remote maximum 6 cm from the IR receiver and press a key, again, keep it pressed.


For Girder4: I will test the 3.6b plugin in combination with girder4 but this will be my last attempt for girder4 cause 3.29 works fluently , okay, less functionality compared to the girder4 plugin .


Note for the 56kHz UIRT users:
PL lights (well known in europe) spread some IR and the UIRT acts on it.
The led will keep on flashing and might trigger a function (pure by luck)
It has more impact on the 56kHz model.
Only solution is: hide the USB UIRT better so that it can't pick up any direct light comming from the PL bulbs.

[Benarty]

3.6b can connect to dvbviewer.
But I stick to girder 3.2.9 as being fully functional.
and for new users, also free solution.

[spacebob]

HI I Need to know how to add this command. DVBV:SendCommand(DVBV.OSDOK)
to (Eiffel DVB Viewer 3.6b.gml) I think the OK funktion missing or??


/Jesper

[Francois]

I can't find any value for OSDOK, or OK...

Have you tried DVBV:SendCommand(DVBV.ENTER)?

[spacebob]

Thanks its works with DVBV:SendCommand(DVBV.ENTER)

/Jesper