Girder 4 and MR26A

[molitar]

Version 4 seems to be crap. In version 3.3 we could create our own ini files for serial com support. So that it would work properly and not be missing button presses and such. But no you decide to remove any capability of supporting ini files and giving us a generic serial plugin that we have NO CONTROL over at all. How stupid is that?

What is it with companies lately removing customization support? Look at M$ new IE 7 which is total CRAP! It removed all the customization control we have.. Looks like I need to go back to Girder 3.3 that works properly since 4 removed customization by removing the capability of using ini files.

[Rob H]

Girder 4 is a lot more customisable than Girder 3.3, but ini files have been replaced with Lua serial devices. This is a little more complex, but a fair bit more flexible.

If you want help with Girder 4 then please just ask for it.

[cpdlink]

Hi Rob,

I know it's an old post, but if your offer is still standing I'd like to take advantage of it ... yes I need help with setting up my MR26a remote with Girder4, attached is a copy of my mr26a.ini used with Girder3

Thanks in advace,
Chris.

[Rob H]

Okay, try this one - put the file in the plugins\serial folder and reset Girder.

Then go to File|Settings|Plugins and select the serial tab. Then select the relevant COM port for the MR26A and press the Change Device button.
Select the MR26A device from the list and press the OK change button.

Clear the Lua console then try pressing a few of the buttons on the remote.

Post the console output here.

[cpdlink]

Hi Rob,

First of all THANK YOU VERY MUCH for your help, and SORRY for the delay - frankly I was so hopeless about getting any kind of help with this device in G4 that I even forgot to select a notification type, SORRY again!

Now about the file posted and your instructions, everything worked well, here is the console output (the attached file). It represents remote buttons from 1 to 0, each and every one of them generated, as you probably see, two entries in the console.

Thanks again,
Chris.

[Rob H]

Good, that conforms to the protocol description that I found.

Okay, try this version and press the Volume Up and Volume Down buttons and you should get a VolUp and VolDown event in the logger.

If that works, then you'll need to add the appropriate entries to the EventTable for the other keys. Take a look at http://www.drsegal.com/technical/mp3_remote.htm for a table that should get you started, as that's where I got the values for VolUp and VolDown.

Also, visit the thread at http://www.promixis.com/forums/showthread.php?t=12038 and claim a device number for the MR26A and use that on line 22.

[cpdlink]

hi,

as per your instructions, i've changed the file with the new one, but the logger does not show anything and the console shows an error, please see attached file.

comparing the two files i saw that ReceiveFixedLength in the first one was 5 and in the new one 10, so i changed 10 to 5; as a result, line:

local hex = math.bytetohex(byte1)

makes girder crash.

please advise,
chris

[Rob H]

Change it back to 10 and increase the IncompleteResponseTimeout - try doubling it first.

[cpdlink]

hi,

changed the following:

ReceiveFixedLength = 10
IncompleteResponseTimeout = 200

and the result is in attached file, still nothing in the logger, not to mention the two green leds in the girder status bar are still...

thanks,
chris

[Rob H]

Try this one, not sure what I was thinking in the previous version.

[cpdlink]

here is the output with the new version, when pressing vol+, vol-:
Serial: MR26A : Simple Receive: Data D5 AA EE 60 AD Õªî`* Code: 8192
Serial: MR26A : ERROR: Incomplete response to last command
Serial: MR26A : Simple Receive: Data D5 AA EE 60 AD Õªî`* Code: 8192
Serial: MR26A : ERROR: Incomplete response to last command
Serial: MR26A : Simple Receive: Data D5 AA EE E0 AD Õªîà* Code: 8192
Serial: MR26A : ERROR: Incomplete response to last command
Serial: MR26A : Simple Receive: Data D5 AA EE E0 AD Õªîà* Code: 8192
Serial: MR26A : ERROR: Incomplete response to last command

still nothing in the logger and still no led activity

increasing IncompleteResponseTimeout to 200 crashes girder

chris

[Rob H]

It crashes Girder?? That's weird!

Okay, try this one.

[cpdlink]

hi rob,

here is console output after initialization:
Serial: MR26A : Opened Device: MR26A Port: 1 Settings: 9600 N 0 8 0
Serial: MR26A : Callback Installed 1

and here is after i hit any key (in this case -vol):
Raw data is D5 AA EE E0 AD D5 AA EE E0 AD Õªîà*Õªîà
then crash ...

here is the console output with incompleteresponsetimeout set to 100:
Serial: MR26A : Simple Receive: Data D5 AA EE 60 AD Õªî`* Code: 8192
Serial: MR26A : ERROR: Incomplete response to last command
Serial: MR26A : Simple Receive: Data D5 AA EE 60 AD Õªî`* Code: 8192
Serial: MR26A : ERROR: Incomplete response to last command

it actually crashes with anything greater than 105

if it helps, I could post the crash report too

or send you my mr26a for a hands-on test...

cheers,
chris

[Rob H]

When you say it crashes Girder - you mean that Girder itself crashes and burns? Or is this just a Lua script error?

What exact version of Girder is this?

[cpdlink]

Hi Rob,

It crashes as in "This program has performed an illegal operation..." or something like that and it then proposes me to send the error report to Microsoft, and girder icon from tray disappears.

But right now I am trying this on a computer at work with a freshly downloaded version of Girder4 and amazingly it's working: i can see led activity, logger shows vol+ vol- ... i don't know what to say ... it must be something wrong at home ... do you have any idea? i'll look again and keep you posted

thanks again for everything,
Chris

[cpdlink]

Hi,

Here is my final version of the mr26a.lua configuration file with codes for all the keys, and since not all remotes are the same, I've also added a picture of my remote.

It's working very well!!!

Thanks again Rob for your help and your patience.

Cheers Everybody,
Chris