#39 ModeName Special Function

Graham Dixon — Thu, 13 Oct 2016 09:55:28 -0000

status: open --> pending
assigned_to: Graham Dixon

ModeName Special Function

Curt — Thu, 13 Oct 2016 04:17:04 -0000

In v2.02a RMIR the Special Function "ModeName" worked properly as follows: Clicking New on the Special Function tab brings up a dialog box that includes a dropdown field for "Type:". When selecting ModeName another parameter box pops up called "Text:". The user can type in a natural language name like "YAMAHA". Closing the dialog box the automatically generates the proper hex codes.

Now in all versions (2.03 and 2.04) ModeName does not work properly. The field is now called "Hex:" instead of "Text:". No matter what is typed in the field the dialog box does not record it as a function nor does it create the hex (in the table of Special Functions the entry only shows as two quotes "" and the Hex column is blank).

In fact the dialog box cannot be cleared and fails to reset when changing to another entry. I have to make ModeName entries in v2.02a then, because I am on Yosemite I have to switch to v2.03/2.04 to upload to the remote. (seems like I read that RMIR v2.02 does not work well on Yosemite with FTDI driver v2.3).

Upgrade Code 0 = CC 53 (Misc Audio/1107) Custom Mode Name Device (RM v2.04 build 8)
F8 00 01
End

Upgrade protocol 0 = 01 F8 (S3C80) Manual Settings: 01 F8 (RM v2.04 build 8)
00 00 01 C6 CA 07 F7 C6 CC 00 2D EC 09 F6 06 ED
E6 B1 01 AF
End

ModeName Special Function

Curt — Thu, 13 Oct 2016 04:17:04 -0000

Ticket 39 has been modified: ModeName Special Function
Edited By: Graham Dixon (mathsdon)
Status updated: u'open' => u'pending'
Owner updated: None => u'mathsdon'

Recent changes to 39: ModeName Special Function

#39 ModeName Special Function

ModeName Special Function

ModeName Special Function