Turtle beach remote/PB never sending same codes..

[Mark F]

I just saw this thread. Sorry for being so late. :sad:

I'll try to reproduce this.

EDIT: Which version of the serial plugin are you using?

_________________
Mark F

<font size=-1>[ This Message was edited by: Mark F on 2002-01-19 13:55 ]</font>

[Mark F]

... and now I don't see a failure mode. When the receive length is changed on the receive message properties page and you press OK on that page and the device page, the plugin places the length and message type (fixed, in this case) into the registry and in the code's local variables. These are used immediately.

What is the failure mode you are talking about? Are the events too long/short? Is the incomming data translated wrong? Have you used the logger plugin to see what events are being sent through Girder? I don't understand and need to in order to fix this so what is the failure mode? What is the bug you are seeing? :sad:

Thanks for bearing with me. I want this BUG DEAD!

[Mark F]

I can see this failure is hard to explain. :smile:

A failure mode is the symptoms of the failure itself. At this point, in my testing of the receive dialog, I don't see one. :sad:

The provided data is very interesting.

D5AAEE70AD is 5 bytes in size, not 8. Each byte is two hex digits (D5 AA EE 70 AD). Do you have "receive timeout" turned on? If so, what is the number of milliseconds (the numeric field)?

I know you said this is approximate but 15A15ED154D is 5 1/2 bytes. This is just about impossible. :smile:

Logger tells you the data the serial plugin passes to Girder. Without being able to correlate between all the data coming into the PC and all the data being passed to Girder, I can't really tell what processing the serial plugin is applying to the data.


... this can only be fixed by the method descibred in the above in this thread
What else did you try? For example, did you try a receive timeout of 10-20 msec?


so there could be two bugs - the one that does'nt saves the WL and the one that makes it hard to choose a desires Wl
OR it is possible you don't have the correct receive settings for the device figured out yet.

Would you please export your device and send the file to:

Mark_Fiechtner'at'Rocketmail'dot'com

Where 'at' is @, 'dot' is . and there are no spaces. Thanks. :smile:

[Mark F]

Without help (the exported device file, at least), I cannot get to the bottom of this. Sorry.

[Mark F]

It might help. :smile: Right away I see the value TimeoutValid=238 is in error since it represents a boolean and should be 0 or 1.

Did you intend to have a 1 msec timeout for incoming messages?

I noticed you didn't include the [OutputMessage] section but it shouldn't be used if this is an input only device.

I'll have to get into this further this evening (at home) if I get away from work at a reasonable hour.

THANKS!!! for the exported data. :smile:

[Mark F]

That would be great, Joe!

Find, download, install and enable the Logger plugin from the download page (http://www.girder.nl/download.php). Be sure to check the "Add device" and "Add time" boxes. This plugin will record and time stamp the events as they pass through Girder.

With the device FAILING, export your serial device information into a file called "Failing.ini".

Use the device for a bit and using copy and paste, place some of the event log (showing the failure) into a .txt file.

Do the "bug fix method" described above or whatever you do to make this thing work. :smile:

Use the device a bit and using copy and paste, place some of the event log (showing the working thing) into the same .txt file. Leave space and maybe a comment between the two sets of event data. If you can correlate button presses with both sets of data, that would be even more helpful.

For example:
(Output from the logger plugin)
Dev: 14 4kt3nU2p00003 13:10:24
Dev: 14 4kt3nU2p00003 13:10:21
Dev: 14 4kt3nU2p00003 13:10:18 <-- pressed button 1
Dev: 14 4kt3nU2p00003 13:10:15
Dev: 14 4kt3nU2p00003 13:10:14 <-- Pressed button 2

With the device WORKING, export your serial device information into a file called "working.ini".

This should leave you with two device (.ini) files and a .txt file. Use WinZip to make these three into one file and send it to me at:

Mark_Fiechtner'at'Rocketmail'dot'com

Where 'at' is @, 'dot' is . and there are no spaces.

I know this is a pain but since I don't have the hardware, this is the only way I know to get the info I need to figure this out.

THANKS!!! for being so understanding.

[Mark F]

The timeout is useful to bound the amount of time used to wait for a short event to be received. Not all serial devices can be counted on to send a full event every time. If the timeout expires, the plugin will send whatever data it has accumulated, even if it is less than the current fixed length definition, to Girder.

An example:

Assume you set the fixed message length to 8 and the timeout to 1 msec. Once the first byte arrives, the timer is set to 1 msec. When the next byte is received, the timer is set to 1 msec and so on. If the timeout expires between any two bytes of the 8 byte length, the plugin sends the current data to Girder as the event.

EDIT: The end result of the above is for messages less than 8 bytes in length (say, 5 bytes), as long as there was a 1 msec delay between them, they would be received correctly. This may be what your "bug fix method" above does in some weird way.

_________________
Mark F

<font size=-1>[ This Message was edited by: Mark F on 2002-01-21 22:50 ]</font>

[mkc2000]

Make sure you have Mark's latest serial plugin. Settings that work for me:
E,8,1
None 9600
Com1
Receive:
Fixed 8
Enable timeout 0
Translate
Works great!!

[mkc2000]

Here is my export for the TB RF remote:

[Device]
UserName=COM1
[Properties]
BaudRate=6
Handshaking=1
ParityBits=2
WordSize=4
StopBits=0
[InputMessage]
Timeout=0
TimeoutValid=1
Timeout2=0
Timeout2Valid=0
ShowEvents=0
TermVal=2559
TermSize=2
TerminatorProcessing=1
PrefixProcessing=0
Length=8
Translate=1
Type=1
[OutputMessage]
Timeout=0
TimeoutValid=0
Timeout2=0
Timeout2Valid=0
ShowEvents=0
TermVal=13
TermSize=1
TerminatorProcessing=1
PrefixProcessing=0
Length=1
Translate=1
Type=1

I also emailed the zip file to Ron.
:smile:

[Amok]

the problem maybe with the serial plugin settings bug, as ive tried with xp and 2000 with no probs maybe this is happenign to you with girder:
when u press a key on the RF control is not differnt commands that get recongnized by the serial plug-in but the same comannd that does not "FIT" in the expected "space" (fixed lenght) and scrolls giving the inpression of different commands
Try serialWatcher.exe with settings: size:8 lenght8 and others default it worked perfecly with the rf control
To avoid the bug in girder serial plug Try This but be aware that u have to do this everytime u restar grirder (so never restart it!_


serial plug setting: size:8 lenght8
and leave others default
but is not that easy, for a setting to work u have to:
choose your word size( 8 for this remote)
then click on recieve (another page opens, why can't it be on the same page??)
set your fixed lenght (8) click ok(the page closes)
click on recieve again, click on variable lenght click ok (the page closes)
then recieve one more time (page opens)and fixed lenght again click ok and close the pluging page
in 4 seconds you should be set up
Basically what u have to so is switch between the two lenght modes for the plugin to start working as it should

http://www.manucar.com/pcrc/serialwatcher.zip

http://www.girder.nl/phpBB/viewtopic.php?topic=555&forum=2&12

If this does not help, post here


<font size=-1>[ This Message was edited by: Amok on 2001-12-30 06:30 ]</font>

<font size=-1>[ This Message was edited by: Amok on 2001-12-30 06:30 ]</font>

[Amok]

The thing is... once u got it working, don't touch it!
Be sure to set the size to 8 length 8
With this settings works ok,(once it does)
i have the setup on for a couple of days with no probs at all (i use a dedicated pc 4 this, never shutdown)
with setting size:8 length:8 messages are as follows:
D5AAEE70AD (STOP)
D5AAEEB8AD (FF)
D5AAEE38AD (REW)
etc.

I had the same issue when i tried setting the SIZE to "6" (messages look like 15A15A12)to overcome the "scroll" prob.
Avoid this because messages get confused,
Use size: 8 length: 8 they work perfect
NOTE: if all else fails try size: 8 length: 10.i don't remeber correctly and i. . . DON"T WANNA OPEN THE PLUGIN PANEL OUT OF FEAR IL LOOSE the settings :smile:
Glad 2 help
P.D. get the amazing "registers demostation (SIC)" for keypad functionality(if the link don't work search this forum)

http://www.stack.nl/~stilgar/windoze/files/playlist.gir



<font size=-1>[ This Message was edited by: Amok on 2001-12-30 09:17 ]</font>

[Amok]

3 questions:
What values u ended up using? (S:8 L8:??)
does your remote send the same valuesthan mine?? (for additional remote purchasing)
D5AAEE70AD (STOP)
D5AAEEB8AD (FF)
D5AAEE38AD (REW)
etc.
is 9600 the default speed in the serial plug-in?
thanks?


<font size=-1>[ This Message was edited by: Amok on 2001-12-30 09:36 ]</font>

[Amok]

u sneaked that post while i was editing the last one!!!
Fast!
i added a question
thanks

<font size=-1>[ This Message was edited by: Amok on 2001-12-30 09:38 ]</font>

[Amok]

im on messenger as amok@velocom.com.ar :wink:

[Amok]

i use Latest Version
i try to explain more . . .
1) i don't know what failure mode means
2)when girder is started the events arrive as if they where of a different work lenght(WL).
with a Wl of 8 the events should look like this: D5AAEE70AD, but when u start girder the same command arrives as 15A15ED154D (approx., a differnt WL i assume) but the pulgin setting page shows the correct Wl of 8 this can only be fixed by the method descibred in the above in this thread
3) i have not used the logger, but i have used serial watcher(see above in thread) to see that incoming serial data is ok
4) so there could be two bugs - the one that does'nt saves the WL and the one that makes it hard to choose a desires Wl
hope this helps, this bug is very hard to explain :wink:

[Amok]

ok.
so . . when girder starts the WL of 8 that is displayed on the recieve page is correct.
At WL 8 events are to "large?" for girder causing the events to "scroll" and it renders them unusable.
The value i need for this device must be WL 5 then (D5AAEE70AD).
but . . . the only way i can get the events to come up as i want (WL 5) is to do the "bug method" (described above), remember that in the "bug method" i set a WL to 8, this is (i suppose) the main bug.

This is only an "annoy" bug and with the "bug method" i can get it to work as expected and once its set up it never fails
but everytime girder is restarted i have to do the "bug method" (5 mins of wasted time :wink:)

I have not tried Logger, could it be a bug in girder instead???

Sorry if i can't test more, but i don't want to have downtime on the music server (other users at my home and on the internet ,via shoutcast, expect 24/7 service from this machine)
Maybe "jfarro" (same symptoms) can help us.

and the messages in wl 8 look something like this AAEEDD0025AADDEE (totally aprox. in size and content, from the back of my head)

And . . . Thanks.! the plug is exelent and an indispensable piece im my digital life

<font size=-1>[ This Message was edited by: Amok on 2002-01-20 18:03 ]</font>

[Amok]

Mark , here's the export:

[Device]
UserName=2
[Properties]
BaudRate=6
Handshaking=0
ParityBits=0
WordSize=4
StopBits=0
[InputMessage]
Timeout=1
TimeoutValid=238
Timeout2=1
Timeout2Valid=0
ShowEvents=0
TermVal=29
TermSize=1
TerminatorProcessing=0
PrefixProcessing=0
Length=8
Translate=1
Type=1

hope it helps

[Amok]

mark:
i've never touched the timeout setting.
what is the purpose of the timeout function?

[jfarro]

Hey, I've seen a recent thread about this, but no real solution. I'm seeing this to the point where Girder has been unusable to me, and I'm wondering if we can narrow down whats causing it.

I've tried two different remote setups...one is a Turtle Beach RF remote (saw a previous post of this working using the generic serial port driver). I tried this remote on XP on an Asus/Athlon combo. I get different codes each time, but similar ones. I tried a baud rate of 300, but to no avail. I also tried turning off 16550 UART in xp but no dice.

The other remote I tried on both an XP and a 2k machine, and I tried it using a serial port sniffer. From the sniff, I see that the codes getting entered vary greatly, and so I know its not a girder issues. Its gotta be some kinda 2k/XP issue, and remote specific. Any ideas or other reports (so we can try to narrow down what does/doesn't work) is much appreciated. Specificially any info on 2k, XP and/or experiences with the PB remote/RF Turtle beach remotes...

Joe

[jfarro]

Ok, you rock! You were absolutely right on all accounts. Using serial watcher, I was able to see that the remote worked great (btw, I picked it up at CompUSA in Kirkland,wa for 50 bucks..and it came with the full audiostation 4 setup...not bad for an IR remote, plus an audio 2.4 ghz transmitter, reciever, and all necessary cables...and a crappy program).

Some notes about this remote..

The remote has yellow labeled functions which work with the audio station (crappy) software..but the software only works with the yellow buttons. This really sucked.

The good news is that I was worried only those buttons transmitted via RF. Not so...ALL the buttons on the remote (when the PC setting is set) transmit on RF...which gives you about 40 buttons to play with (including all your favs such as volume, channel, 0-9, menus, subtitle, etc. Based on these findings, I highly recommend this remote.

Thankyou so much for your help! Girder is the program I've been hoping,looking for for a long time, and I look forward to contributing what I can to this project. Well done!

note: the above mentioned bug is annoying...is that a girder fix, or a serial plugin fix thats needed?

Joe

[jfarro]

Actually, I'm seeing a new issue, maybe you've got help for it. Seems that alot of my keys seem to be sending the same codes now (opposite of what i had before). At least, that is what girder seems to be seeing...any ideas on how to make it more sensitive?

[jfarro]

Ok, figured it out using serial watcher, and the vals you sent...I had my port speed set to 4800, which was bad. it works perfect (so far) at 9600.

This may help those trying to debug thier settings..if you get the same value for various buttons, you may have to adjust the speed of the serial port. I'm seeing (for the remote I'm using) that you seem to get a more precise reading at faster port speeds. I changed the View in serial watcher to Hex to match up with what Girder shows. This helped quite a bit.

Thanks!

[jfarro]

Yes, the exact same.

Others:
FF - D5AAEEB8AD
Rewind - D5AAEE38AD
Rand/Display - D5AAEE3AAD
Looping - D5AAEED8AD

Vol. Down D5AAEE0AD

I'm working on a Windows Media Player 7.1 set using as many of these as possible (and using the shortcut keys so that it doesnt matter what skin is on, etc).

Is the file I'm working on useful to the community? should I up it when I'm done?

Joe

[jfarro]

oh, sorry, forgot the first part...

The default for the plugin was 4800

[jfarro]

LOL,
using size 8, Len 8, 9600

Looks like the remotes are perfect clones, I may have to go pick up another then.

Only things I changed was:

1. Upped baud rate to 9600
2. Set Device to Com2
3. Added a Name
4. Clicked on recieve and set the len. to 8

Proceeded to follow your instructions on switching back and forth (man, that seemed odd the first time, but its definitely necessary...I even tried cutting stuff out to see if I coudl shorten it..no dice)

I'm on msn messenger (joefarro@hotmail.com). added you to that

[jfarro]

I've been busy and have just gotten back to this thread. I'll try to setup a repro tonight and get you the information you requested. From memory, the girder display showed it picking up a large amount of numbers (the display just about filled up) and each time I hit a button the digits would "shift" a varied number to the left or right. They would be the same digits in the same order, but some of the ones at the end would now be at the start, and it would change each time.

Please send a list of what information you'd like, and I'll compile a bug report for you.

Joe