Reply to thread

Message

<blockquote data-quote="Herr R aus B" data-source="post: 219126" data-attributes="member: 62807">Unfortunately it doesn't - I still have the same problem with the configuration. Clicking the &quot;advanced&quot; button in the configuration dialogue flashes the remote mapping dialogue once and gives me the red exclamation mark. Pressing the button for the second time then shows the remote mapping dialogue. Returning from this dialogue i still have the red exclamation mark and the &quot;OK&quot; button in the configuration dialogue remains disabled. Although the modified mapping is saved now.The driver DLL is still locked after closing the configuration application and the process is still running (as described above)Is this maybe an X64 issue as 64 bit windows is not officially supported?I'm gonna try that - thanks for the hint.That was rather less seriously meant as I can imagine the amount of work implicated. Never the less I am thinking of coding a C++ based service that offers sockets for IRTrans access and display control&nbsp; do you think you might be interested in coding the display driver to access that service *if* I succeed coding it?There still are some issues left, that might be not so hard to solve. Obviously there is a problem initializing the display. I peeked in your code and the only place where I found initializing stuff was:commPort.Write(new byte[] { 0xAA, 0xAA }, 0, 2); //Init IR &amp; DisplayThat's a little bit less than what the MHC software does. Obviously it leads to a different behaviour of the VFD. Using your driver will not initialize the fans - unfortunately they run on a rather high level after switching on (i wonder who designed this hardware...) und that's loud. The other point is, that sending windows to standby switches off the VFD. Thus it's not possible to get windows awake using the remote control. Using the MHC software instead of your driver lets you send windows to standby and one can wake it up with the romte. Now here is, what he MHC software sends to the VFD for initialization:A4 7D&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; ¤}AA AA&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; ªªAA AA&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; ªªAA AA&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; ªªAA AA&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; ªªAA AA&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; ªªAA AA&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; ªªAA AA&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; ªªAA AA&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; ªªAA AA&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; ªªAA AA&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; ªªA0&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; A5 38&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; ¥8Must be some &quot;hello are you out there?&quot;A1 00 A7 57 65 6C 63 6F 6D 65 20 74 6F 20 20 20&nbsp;&nbsp; ¡.§Welcome to&nbsp;&nbsp; 20 20 20 20 20 20 20 00&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; .A2 00 A7 20 20 4D 2E 50 6C 61 79 20 48 6F 6D 65&nbsp;&nbsp; ¢.§&nbsp; M.Play Home20 43 65 6E 74 65 72 00&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Center.AFThis sets the displayAC&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ¬00&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; .00&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; .as far as I tested it this sets the fans to 0% (AC &lt;fan1&gt; &lt;fan2&gt; with 00 = 0%, 47 = 40%, 58 = 50%, 6A = 60%, 7C = 70%, 8E = 80%, 9F = 90%, B1 = 100%)00 00 00&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ...AD 00 00 10 18 04 00 00 00 00 00 00 00 0C 1B 14&nbsp;&nbsp; *...............08 00 00 00 00 06 1B 05 02 00 00 01 03 07 09 00&nbsp;&nbsp; ................00 00 00 04 18 10 00 00 00 12 10 14 13 08 04 03&nbsp;&nbsp; ................00 09 01 05 19 02 04 18 00 00 09 07 03 01 00 00&nbsp;&nbsp; ................00&nbsp; &nbsp; &nbsp;&nbsp; .&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; This seems to be important.... I attached the complete communications log and a few more for those who might be interested...Do you think you can incorporate this in your driver? Or even better give us an opportunity to configure all this hex stuff ourselves? Maybe something like an XML file with several sections like Init1, Init2, FanSetup, etc...? That might help finding the exact initialization sequences without keeping on bothering you <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />Finally there is an issue with key press repeats. The M-Play remote is somewhat strange. As you can see in the PDF with the remote codes I posted some days ago, I always added a &quot;7E&quot; because i thought it belonged to the key code. Now somewhere here in the forum I read, that the &quot;7E&quot; just means &quot;repeat the last key&quot;. Would it be possible to evalute that behavior in the driver?GreetsAxel</blockquote>

[QUOTE="Herr R aus B, post: 219126, member: 62807"] Unfortunately it doesn't - I still have the same problem with the configuration. Clicking the "advanced" button in the configuration dialogue flashes the remote mapping dialogue once and gives me the red exclamation mark. Pressing the button for the second time then shows the remote mapping dialogue. Returning from this dialogue i still have the red exclamation mark and the "OK" button in the configuration dialogue remains disabled. Although the modified mapping is saved now. The driver DLL is still locked after closing the configuration application and the process is still running (as described above) Is this maybe an X64 issue as 64 bit windows is not officially supported? I'm gonna try that - thanks for the hint. That was rather less seriously meant as I can imagine the amount of work implicated. Never the less I am thinking of coding a C++ based service that offers sockets for IRTrans access and display control do you think you might be interested in coding the display driver to access that service *if* I succeed coding it? There still are some issues left, that might be not so hard to solve. Obviously there is a problem initializing the display. I peeked in your code and the only place where I found initializing stuff was: [FONT="Courier New"][SIZE="2"][B]commPort.Write(new byte[] { 0xAA, 0xAA }, 0, 2); //Init IR & Display[/B][/SIZE][/FONT] That's a little bit less than what the MHC software does. Obviously it leads to a different behaviour of the VFD. Using your driver will not initialize the fans - unfortunately they run on a rather high level after switching on (i wonder who designed this hardware...) und that's loud. The other point is, that sending windows to standby switches off the VFD. Thus it's not possible to get windows awake using the remote control. Using the MHC software instead of your driver lets you send windows to standby and one can wake it up with the romte. Now here is, what he MHC software sends to the VFD for initialization: [B][FONT="Courier New"][SIZE="2"]A4 7D ¤} AA AA ªª AA AA ªª AA AA ªª AA AA ªª AA AA ªª AA AA ªª AA AA ªª AA AA ªª AA AA ªª AA AA ªª A0 A5 38 ¥8[/SIZE][/FONT][/B] Must be some "hello are you out there?" [FONT="Courier New"][SIZE="2"][B]A1 00 A7 57 65 6C 63 6F 6D 65 20 74 6F 20 20 20 ¡.§Welcome to 20 20 20 20 20 20 20 00 . A2 00 A7 20 20 4D 2E 50 6C 61 79 20 48 6F 6D 65 ¢.§ M.Play Home 20 43 65 6E 74 65 72 00 Center. AF[/B][/SIZE][/FONT] This sets the display [FONT="Courier New"][SIZE="2"][B]AC ¬ 00 . 00 .[/B][/SIZE][/FONT] as far as I tested it this sets the fans to 0% (AC <fan1> <fan2> with 00 = 0%, 47 = 40%, 58 = 50%, 6A = 60%, 7C = 70%, 8E = 80%, 9F = 90%, B1 = 100%) [FONT="Courier New"][B][SIZE="2"]00 00 00 ... AD 00 00 10 18 04 00 00 00 00 00 00 00 0C 1B 14 *............... 08 00 00 00 00 06 1B 05 02 00 00 01 03 07 09 00 ................ 00 00 00 04 18 10 00 00 00 12 10 14 13 08 04 03 ................ 00 09 01 05 19 02 04 18 00 00 09 07 03 01 00 00 ................ 00 .[/SIZE][/B][/FONT] This seems to be important.... I attached the complete communications log and a few more for those who might be interested... Do you think you can incorporate this in your driver? Or even better give us an opportunity to configure all this hex stuff ourselves? Maybe something like an XML file with several sections like Init1, Init2, FanSetup, etc...? That might help finding the exact initialization sequences without keeping on bothering you :-) Finally there is an issue with key press repeats. The M-Play remote is somewhat strange. As you can see in the PDF with the remote codes I posted some days ago, I always added a "7E" because i thought it belonged to the key code. Now somewhere here in the forum I read, that the "7E" just means "repeat the last key". Would it be possible to evalute that behavior in the driver? Greets Axel [/QUOTE]

Verification