lenz-static-linux-en
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
— | lenz-static-linux-en [2018/11/12 08:56] (current) – created - external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ======Lenz====== | ||
+ | [[: | ||
+ | [[english|Content]] -> [[english# | ||
+ | * **[[lenz-static-linux-en|Linux static driver install]]** | ||
+ | |||
+ | \\ | ||
+ | ===== Static method (install driver at boot time) ===== | ||
+ | |||
+ | This method is proven to work with openSUSE 11.1. | ||
+ | |||
+ | You need to modify the file '' | ||
+ | |||
+ | Now that we have got the '' | ||
+ | |||
+ | <code xml> | ||
+ | <digint lib=" | ||
+ | </ | ||
+ | |||
+ | with the new line: | ||
+ | |||
+ | <code xml> | ||
+ | <digint iid=" | ||
+ | </ | ||
+ | |||
+ | Please note the ''/ | ||
+ | |||
+ | In the interface box, Lenz use a chip from Future Technology Devices International, | ||
+ | |||
+ | Use an editor to modify the file ''/ | ||
+ | |||
+ | < | ||
+ | ## Type: | ||
+ | ## ServiceRestart: | ||
+ | # | ||
+ | # This variable contains the list of modules to be loaded | ||
+ | # once the main filesystem is active | ||
+ | # You will find a few default modules for hardware which | ||
+ | # can not be detected automatically. | ||
+ | # | ||
+ | MODULES_LOADED_ON_BOOT=" | ||
+ | </ | ||
+ | |||
+ | Now you also need to make sure the driver knows about the vendor and procut ID of the Lenz interface, by adding that data to the file ''/ | ||
+ | |||
+ | < | ||
+ | # | ||
+ | # please add local extensions to this file | ||
+ | # | ||
+ | options ftdi_sio vendor=0x0403 product=0xd780 | ||
+ | |||
+ | </ | ||
+ | |||
+ | The above vendor and product id are the ones my interface came with. This should in theory be the same for all the Lenz boxes. | ||
+ | |||
+ | Lenz may have shipped some with dummy values of vendor=0x1111 and product=0x1234. | ||
+ | You can find out the values of your box by connecting it and typing '' | ||
+ | |||
+ | < | ||
+ | hans@Taurus:/> | ||
+ | Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub | ||
+ | Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub | ||
+ | Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub | ||
+ | Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub | ||
+ | Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub | ||
+ | Bus 005 Device 004: ID 0403:d780 Future Technology Devices International, | ||
+ | Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub | ||
+ | Bus 003 Device 003: ID 046a:0050 Cherry GmbH | ||
+ | Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub | ||
+ | Bus 002 Device 003: ID 0c4b:0100 Reiner SCT Kartensysteme GmbH cyberJack e-com/ | ||
+ | Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub | ||
+ | hans@Taurus:/> | ||
+ | </ | ||
+ | |||
+ | Having done all of the above, you will find that rocrail still cannot talk to the Lenz interface. This is because the device ''/ | ||
+ | |||
+ | You can do this e.g. in yast with Security and Users -> User and Groupmanagement -> double click on the user you want to add -> Details -> check the box for uucp on the right (you may have to scroll down to see uucp). Finish by clicking OK twice. | ||
+ | |||
+ | Now | ||
+ | * reboot your machine | ||
+ | * plug in the interface and switch on the power to your Lenz equipment | ||
+ | * check in the ''/ | ||
+ | * start the rocrail server | ||
+ | * start rocview | ||
+ | * go to Tables -> Locomotive table... and create a new locomotive table | ||
+ | * the new locomotive table will appear above the clock - double click on it | ||
+ | * don't forget to switch on the power using Control -> Power on | ||
+ | * and hopefully you're off running your first loco !!!!!! | ||
lenz-static-linux-en.txt · Last modified: 2018/11/12 08:56 by 127.0.0.1