Mini Display Plugin (2 Viewers)

[chemelli]

Hi,

being an owner of a Mäusekino display, I wrote a driver for ExternalDisplay a while ago. CybrMage ported my driver to CybrDisplay, however the port had a bug. The MiniDisplay plugin of course had the same bug. I finally could fix the bug and have compiled a working MiniDisplay driver for the Mäusekino.

What should I do to for the bugfix to be included in the SVN?

Best regards,

Astronaut

Hi Astronaut,

please attach here a .patch file with the code changes. I will take care of adding them to SVN.

Simone

 

[astronaut]

Hi Astronaut,

please attach here a .patch file with the code changes. I will take care of adding them to SVN.

Simone

Hi chemelli,

thank you for the reply. The patch file is attached.

As I am not very good in writing code, there might be a better solution for setting the array to zero - you might have a look at the code and see yourself. Anyway, my solution works...

Cheers,

Astronaut

 

[chemelli]

Astronaut,

please can you give me a desc of what the bug was ?

Simone

 

[astronaut]

Astronaut,

please can you give me a desc of what the bug was ?

Simone

Ciao Simone,

The display controlled by the IOWarrior chip has 128*64=8192 pixels. The bitmap information for all pixels thus can be stored in a byte array with 1024 elements. The absolute value of each array element controls which pixels out of 8 pixels in a row are set (e.g. "1" for pixel 1, "2" for pixel 2, "3" for pixel 1 and 2 and so on).

In the buggy code, the byte array was not set to zero before new pixel information was stored in the array. The new value simply was added to the old value, e.g. if the old value was 255 (all 8 pixels) and the new value was 1 (just the first pixel), the value in the array element was 0 instead of 1, as 1 was added to 255 and the byte can not contain numbers larger than 255.

All I did was enter a loop that sets all array elements to 0 each time an image is processed. Maybe there is a better way to set the array to 0 of which I do not know.

I hope that my explanation is comprehensible?

Greetings to Italy, I hope you have better weather than we have here in Germany! But I am hungover anyway...

Astronaut

 

[chemelli]

Astronaut,

patch is now commited (SVN21936).

Cheers,

Simone

 

[Izikd]

Hello,

I have T6963c based graphic LCD 240*128.
It works fine with LCDStudio, LCDHype and MiniDisplay in text mode.
But, it doesn't want to work in graphic mode in MiniDisplay.
I use Vista 32Bit.
Tried working with the columns and rows number, and nothing.

The logs doesn't show any errors (Just debug and Info).


Any help?

Edit:
About every second it sends this message to log:

2009-03-16 00:45:58.153324 [Info.][MiniDisplay]: MiniDisplayPlugin.DisplayHandler.DisplayLines(): Sending lines to display.
2009-03-16 00:45:58.153324 [Info.][MiniDisplay]: MiniDisplayPlugin.DisplayHandler.SendGraphics(): Processing graphics display.
2009-03-16 00:45:58.153324 [Info.][MiniDisplay]: MiniDisplayPlugin.DisplayHandler.DrawImages(): No images to process

 

[waskol]

"force keyboard" mode doesnt work. Unfortunately this option is crucial for operation of the mediaportal, otherwise on every[/B]

I've updated my solution in the "Solution database"

I speak about my Minidisplay settings, and more over about the registry setting that will prevent a iMon mini remote to act as a mouse :

Main settings of Minidisplay:
A little word about Brightness and Contrast settings : the most comfortable I found was setting both to 25% (sliders put close to left end side)

I checked only :
- Ensure is running...
- Force to use keyboard mode...
and that's it !

If you enforce driver restart--> bam, your remote will act as a mouse.
Other else, there is a specific entry in the windows registry to change: with regedit, look for SoundGraph or Imon entries so that you find the all bunch of settings for the iMon driver : HKEY_CURRENT_USER\Software\SOUNDGRAP\IMON\

You will find here some particularly interesting entries and in particular "MouseMode" : if you have a value of "1" showing here, turn it into a "0"

Chemelli, may be could you include this registry trick in your plugin ?


Looking towards the Registry Settings of iMon, I am pretty sure there is also something for the MCE remote


I have to precise also, that the VFD draws a lot of power from the USB, and that if you have some other USB devices (Game pads, usb key, etc...) plugged on the same USB controller than the one used by your VFD, a lot of annoying thing can occur :
- Your VFD can be slow
- Your system can become crazy (do you hear somwarning sound notifications coming from Windows ? Once it disables your USB controller, 2 second afters it powers it up again, then shutdow (look at your device manager))
- Your system may become instable.

A solution is to plug the vfd usb plug onto a small auto-powered USB hub

Edit : Soundgraph has just released a solution and a patch for this particular problem
here --> http://www.soundgraph.com/Eng_/Foru...TB=T&CurrentPage=1&fcStateId=1&writingLevel=8

 

[chris882]

You did connect the adapter onto the main power supply cable didn't you?

Sorry for the late answer. What cable is this you mean? I only use the cable to connect it to usb and the other ones to the mainboard. I think there is no cable to the power supply.

 

[Frantid]

You did connect the adapter onto the main power supply cable didn't you?

Sorry for the late answer. What cable is this you mean? I only use the cable to connect it to usb and the other ones to the mainboard. I think there is no cable to the power supply.

It looks like a 24 pin power supply cable connector, you plug the power supply into it, then you put the coupled together into the motherboard.

 

[chris882]

Ah, sure, this one. Yes, it is connected.

This afternoon i tested other onboard usb boards, i connected the usb cable to them and tried a lot of times to get the display started. But nothing happens, the display lights only blue without any text. It seems to be defect, didn't it?