- Drivers Policy Template
- Drivers Policy And Procedure
- Drivers Policy Insurance
MediaWiki has been updated to version 1.35.1. Please report any problems here.
PoKeys software setup package contains PoKeys configuration tool (also used for firmware updating), USB drivers, manuals, PoBlocks tool, Mach3 plugin etc. After installation, run the PoKeys application to update the firmware of PoKeys devices. Windows 8/10: make sure that.NET framework 3.5 is enabled on your system before installing the PoKeys setup package. The next step is configure the Postep60-265 programmable motor driver. We do that in PoStep60v1.20 application. Use USB cable to connect with the PoStep60-256. Run the PoStep60v1.20.exe and in a Driver setup tab select “Enable auto run” and set Modbus address and configuration. In our case we will set address to “0x20” and choose “BR: 9600; P: Even” configuration.
If you want to build your own procedure trainer or fully fledged home cockpit, the hardware interface is the core of all. Somehow, you need to connect all the buttons and lamps to your computer. Here is a list of some suppliers:
Europe
Opencockpits, Spain
http://www.opencockpits.org/
Wide range of interface cards plus lots of other hardware.
Drivers: Official drivers for Windows only. Driver development for other platforms is not desired - Opencockpits does not provide hardware communication SDK. No Flightgear implementation yet.
Unknown location
Drivers Policy Template
PoLabs
http://www.poscope.com/
Very nice USB HID hardware interfaces.
Drivers: None required. Interfaces register as USB joystick/keyboard at the computer. The interfaces are programmed with a MSWIN software with keycodes and/or macros. For using the interface NO software is necessary. The whole config is stored on the interface itself!
Drivers Policy And Procedure
Retrieved from 'https://wiki.flightgear.org/w/index.php?title=Hardware_interfaces&oldid=40011'
After reading my 'Reverse engineer and re purpose an old Keyboard' article Boris over at PoLabs kindly sent me a 'PoKeys56U' to have a play with :).
This looks like an updated version of the one I mentioned in my article.
'U' designates the USB version and 'E' the Ethernet version
Standard USB keyboard simulation (with triggering support for up/down keys)
Standard USB joystick simulation (6 axis, 32 buttons with triggering support)
55 digital inputs with pull-up resistors, freely mappable to virtual USB keyboard’s keys
7 analog inputs (12-bit) with adjustable low-pass filtering support
Up to 26 encoder pair inputs (3 high-speed encoder inputs, 1 ultra high speed encoder input)
Two 8x8 matrix LED display support
Up to 64 256-character long keyboard macro sequences
Up to 16x8 matrix keyboard with triggered keys/alternate function support
Up to 6 high-speed fully configurable PWM outputs support (25MHz PWM timer)
HD44780-based character LCD support (up to 4x20 characters)
PoExtBus support for adding up to 10 external shift registers = 80 aditiona outputs
PoNET devices support (48-key CNC keyboard mapped to matrix keyboard, etc)
Support for up to 10 sensors on I2C bus, up to 10 sensors on 1-wire bus and up to 7 analog sensors
Communication compatible with PoKeys55 on application layer (data packet structure)
Drivers Policy Insurance
Third-party support via communication DLL library and extensive protocol specification document that allows porting to other systems
After looking at the new PoLabs website it appears that Boris has quite alot of new things ranging from Oscilloscopes to Stepper motor drivers!
I will have to come up with an interesting project for the blog using it in the coming months :)