Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

driver for MDV Lilli #241

Closed
nvaccessAuto opened this issue Jan 1, 2010 · 23 comments
Closed

driver for MDV Lilli #241

nvaccessAuto opened this issue Jan 1, 2010 · 23 comments

Comments

@nvaccessAuto
Copy link

Reported by GianBrix on 2008-11-25 20:00
Lilli and Mb408 are two Italian braille display of 40 cells. Lilli is connected via usb and Mb408 has two models, one connected in serial mode and the other with bluetooth too.
I tested directly this two drivers.

@nvaccessAuto
Copy link
Author

Attachment mb408.zip added by GianBrix on 2008-11-25 20:01
Description:
mb408 driver

@nvaccessAuto
Copy link
Author

Attachment lilli.zip added by GianBrix on 2008-11-25 20:02
Description:
lilli driver

@nvaccessAuto
Copy link
Author

Comment 2 by jteh on 2008-12-02 12:33
Just to update you on this, we have no problem with including the Python drivers in NVDA. However, I'm still uncertain as to whether we want to start including dlls like this into misc-deps. While they're not too large, the more we include, the bigger things will get. Mick and I will need to discuss this at more length. Perhaps the optional components proposal is the best solution for this, although I'm still not sure about this.

@nvaccessAuto
Copy link
Author

Comment 3 by jteh on 2009-08-07 05:41
I suspect that the USB display requires drivers to be installed on the system. When the drivers are installed, is the required dll also installed? This would make more sense than multiple products carrying around their own copy of the dll. If not, we should at least request that the manufacturer do this. I'd rather not include dlls for hardware which isn't portable and requires software installation anyway.

The bluetooth and serial displays may be another matter, as they possibly don't require software to be installed on the system, which makes them essentially portable. Is this correct?

@nvaccessAuto
Copy link
Author

Comment 4 by jteh on 2009-08-26 02:47
No response from the contributor, so this won't make it into 2009.1.
Changes:
Milestone changed from 2009.1 to 2009.2

@nvaccessAuto
Copy link
Author

Comment 5 by GianBrix (in reply to comment 4) on 2009-10-04 08:23
Replying to jteh:

No response from the contributor, so this won't make it into 2009.1.

I can confirm that both drivers do not need components already installed. The included dlls are completely portable. The only issue to solve is related to the port and baurdrate choices. At this moment serial port is setted to com1 and baudrate to 19200. Thanks you

@nvaccessAuto
Copy link
Author

Comment by jteh on 2009-12-08 05:24
(In #426) Note that this won't work for BRLTTY, which is what is used to support all serial displays at present, as all display configuration has to be done using the BRLTTY configuration. It will only be useful for native NVDA drivers such as the MB408 driver proposed in #241.

@nvaccessAuto
Copy link
Author

Comment 6 by jteh on 2009-12-08 05:26
So I assume the Lilli must use the USB HID protocol in order to function under Windows without a driver? If you plug this display into a computer which it has never been installed on before, will it just work without needing driver installation? That is, does Windows have drivers for it by default?

The MB408 driver probably requires #426 (dialog to set serial port) to be useful, so it will need to wait until that is done.
Changes:
Milestone changed from 2010.1 to 2010.2

@nvaccessAuto
Copy link
Author

Comment 7 by jteh on 2009-12-08 05:35
Bah, silly Trac.

@nvaccessAuto
Copy link
Author

Comment 8 by drein on 2010-03-01 14:30
why silly ticket?
I see Alva dll is shipped with NVDA, so I don't understand the problem to include at least the lilli driver.

@nvaccessAuto
Copy link
Author

Comment 9 by jteh on 2010-03-01 20:12
I've already explained the difference. To summarise, the Alva BC640 does not require any drivers to be installed on the system, so the dll must be shipped with NVDA and it is then useable portably. If the Lilli does not use HID, it is not possible for it to be completely portable and it requires drivers, so the dll should be shipped with the drivers instead. This is why I keep asking whether it uses USB HI`D.

@nvaccessAuto
Copy link
Author

Comment 10 by drein on 2010-03-04 08:28
I don't see any difference in fact.
When you attach Lilli for the first time, Windows sees it as a standard generic device.
You don't install any driver, Lilli needs only the dll and the .py driver in order to work properly.
If you don't believe me, I can show this ticket to the engeneers that make and work to this display braille, since we are in strict contact.

@nvaccessAuto
Copy link
Author

Comment 11 by jteh on 2010-03-04 11:31
So I assume it appears as a USB HID (human interface device), as that is the only way to have Windows automatically install drivers. If this is the case (and this is what I've been trying to get a straight answer to for a while now), then we can certainly include the driver for Lilli.

Have you tested this NVDA driver? Does it still work?

@nvaccessAuto
Copy link
Author

Comment 12 by drein on 2010-05-13 07:41
Yes, Lilli drivers works without any problem with NVDA.

@nvaccessAuto
Copy link
Author

Comment 13 by jteh on 2010-07-16 05:32
Lilli driver added in eb64a07. It'd be great if someone can confirm that this works, as I made a couple of very minor changes.

The MB408 driver is going to have to wait until #426 is implemented.
Changes:
Milestone changed from 2010.2 to 2010.3

@nvaccessAuto
Copy link
Author

Comment 14 by drein on 2010-07-22 11:48
Hello James,
Lilli drivers work very well without any problem.
Tested with snapshot 3638.
Thank you.

@nvaccessAuto
Copy link
Author

Comment 15 by jteh on 2011-01-17 00:36
Even if #426 gets implemented in 2011.1, the MB408 driver needs to be updated for the new input framework. The Lilli driver needs updating as well, but it's already included and will still work.
Changes:
Milestone changed from 2011.1 to near-term

@nvaccessAuto
Copy link
Author

Attachment lilli.2.zip added by drein on 2011-02-25 08:51
Description:
new driver for 2011.1 with gestures and some bugs solved

@nvaccessAuto
Copy link
Author

Comment 16 by drein on 2011-02-25 08:56
New driver for Lilli.
The dll has been updated in order to solve some USB connection issues.
the .py file now contain following gestures:
"braille_routeTo": route
"braille_scrollBack": LF
"braille_previousLine": UP
"braille_nextLine": DN
"braille_scrollForward": RG
"kb:shift+tab": SLF
"kb:tab": SRG
"kb:alt+tab": SDN
"kb:alt+shift+tab": SUP

I know it is quite impossible to put this changes in NVDA user guide for 2011.1, but if you can put the driver it will be good for italian users.
The driver has been tested before committing it.

@nvaccessAuto
Copy link
Author

Comment 17 by jteh on 2011-02-27 23:18
Thanks for the new driver. Unfortunately, it cannot be added to 2011.1. It will be considered for 2011.2.

@nvaccessAuto
Copy link
Author

Comment 18 by jteh on 2011-06-09 03:27
MB408 should be addressed separately and is extremely low priority as per #426. I still need to commit the updated Lilli driver.
Changes:
Changed title from "drivers for Lilli and Mb408: two Italian display braille from MDV" to "driver for MDV Lilli"
Milestone changed from near-term to 2011.3

@nvaccessAuto
Copy link
Author

Comment 19 by drein on 2011-07-08 08:27
Can you commit the lilli driver for 2011.2 please?
It is here for a long time, and we must say every user to download NVDA and update the driver manually.
It has not sense for me...

@nvaccessAuto
Copy link
Author

Comment 21 by jteh on 2011-07-29 05:31
Forgot to close this ticket. Done in d3a4338.
Changes:
Milestone changed from 2011.3 to 2011.2
State: closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant