Translate

Development Status

Development outlines for SimVimCockpit (working title - ArdSimX.2)

Development status levels:

  • "Red" - plans, start level ( 1 - Planned, considered for development, 2 - Started, 3 - Started, but Postponed )
  • "Yellow" - development level ( 1 - Underway, 2 - Active development, 3 - Mostly finished, Set "On Hold" )
  • "Green" - finishing level ( 1 - Debugging, 2 - Testing, 3 - Fully completed)

Note: Sometimes the status level is changed backwards.
Website, Configurator, Manuals
Website pages related to SimVimCockpit
SimVimCockpit Configurator
Parameters database fill-up
INPUTFirmwarePlugin/Cfg
Expansible (multiplexed) digital inputs - every pin can be used as input for 16 toggle switches or push buttons
Encoder can be connected to any pair of multiplexer inputs (up to 8 encoders for one multiplexer) the same way as to a pair of direct inputs
Switches and encoders can be connected to the same multiplexer alternately
Improved encoder processing ("synchronizing" with X-Plane frame rate, no missing steps, acceleration - read more in this post )
Improved and unified mode switch functionality for all input types no need
Any X-Plane parameter value can be stored in memory stack with memory button (e.g. radio frequencies). no need
Axis and other analog inputs
Expansible Analog inputs (16 axes for pins A0, A1),
Non-linear input for analog axis (Quadratic curve), higher precision near of neutral (or zero) position. no need
Axis calibration menu in the plugin, setting the axis zero-position and movement range (auto-saved in a file) no need
Stepped axis mapping (parameter values can be mapped for different analog sensor positions) no need
"Digital" axis inputs, using contactless magnetic rotary encoders
Head position tracking to emulate far-distance view effect on a closely located screen (not related to a head rotation).
Output, Displays
Universal configurable output for any type of 7-Segment Displays (built around latch registers, LED drivers or complete modules)
7-Segment Displays based on 74HC595 registers Supported
7-Segment Displays built on DM13A or similar 16-bit LED drivers
Direct control of MAX7219 LED diver for 7-Segment Displays
Direct control of TM1637 LED diver for 7-Segment Displays
Any display can be configured for several dataref values output, each with its own offset Supported
Conditional power control for every display. Any display can be "connected" to specific electric bus that your plane has on-board Supported
Brightness control for MAX2719 displays from brightness dataref. Any display can be associated with specific regulator Supported
Brightness control for displays built on 595 registers (or DM13A LED drivers). Controlled with separate PWM signal Supported
LCD
Native LCD display support. Configurable output to character display 16x2, 16x4 charcters
LEDs, Digital Outputs
Multiple serial LED output based on DM13A or similar 16-bit LED drivers
Support for LED bargraph output (i.e. linear flaps trimmers position indication etc.).
Analog output
Analog outputs support (12-bit PWM), totally 24 outputs for moving-coil meter, adjustable LEDs, PWM controlled devices...
Gear vibration effect outputs. Plane moving on the ground, touching down all simulate realistic impact and vibration forces.
Force Feedback outputs for yoke
Stepper motors
Stepper motors output development (base protocol)
Stepper motors ...
Stepper motors ...
Protocol, Features
New ArdSimX.2 Configurator, more simple and convenient than ASX1
Improved data exchange protocol
Dataref values can be transmitted to additional slave board for custom output devices only Supported
Any input or output is configurable" by condition" (can be activated/deactivated on specific parameters conditions) no need
Uploading firmware into Arduino and updating it from the the plugin
.......
.......
Configuration, macros
More compact configuration file with less overall number of lines no need
Named options inside config lines, without the need to keep all values ordered no need
Database with predefined parameter Keywords, to support one config file with customization for multiple aircrafts no need
Data substitution table for most popular custom planes (such as EADT x737project, laminar-b738, some Carenado planes etc.)
.......
.......
.......
.......



If you have questions or suggestions concerning adding more functionality, please use our email:








10 comments:

  1. Data substitution table for the "laminar" b738x

    Are you refering that we are getting data table for famous Boeing B738-800 modified by Zibo ? :) ( https://forums.x-plane.org/index.php?/forums/topic/111305-boeing-b738-800-modified/ ) if yes, then this is big news for me. I have been waiting it like a maniac.

    ReplyDelete
    Replies
    1. In ASX2 instead of parameters list as in ASX1 configurator there will be the list of predefined "keywords", that will represent dataref line with values and all needed options, or this keyword can include commands or custom macros/functions. All these "keywords" will be universal, independent of aircraft you fly. So, instead of such config line as this one (for standard planes):

      13L 1 sim/flightmodel2/gear/deploy_ratio 1 0.9,1

      ..or this line for the llaminar B738:

      13L 1 laminar/B738/annunciator/nose_gear_safe 1 0.1,1

      .. only one line will be used (one data file for all planes):

      13L Nose_Gear_Green

      Additionally, in each custom plane you will be able to place simple "data correction" text file where will be possible to change any parameter options, values or whole dataref line...

      We will make these data files for several most used custom planes.

      Vlad

      Delete
  2. Vlad,
    I suspect many of us cockpit builders are on hold waiting for your superb tool V2 and Zibo's 738X... to work together as seamlessly as possible! This will open many doors to make XPlane the new standard in home cockpit building.

    ReplyDelete
    Replies
    1. We try to make switching between standard and various custom aircrafts as convenient as possible for this version of the interface.
      However, custom aircrafts can still present problems for cockpit builders, which only depend on how these aircrafts are programmed.
      Most of these problems are due to the focus on virtual cockpits in these aircrafts. They have a lot of datarefs for cockpit controls animations, and some of these are not easily compatible with actual cockpit controls, especially when a lot of datarefs are not writeable.

      There was an example with one custom aircraft that had a switch under a safety cap. It was programmed in a way that only allowed the switch position dataref to be changed when the cap is opened.
      Making a control for cap opening makes no sense for a physical cockpit. What's worse, the control couldn't even be assigned to the switch itself to "fake" the opening before changing the switch position dataref, because the only cap control was to make it go through a 2-second opening animation, with the switch only becoming available for change when it is fully open.

      With things like this, sometimes the solution may be to reprogram the aircraft itself, if such functions are done with LUA scripts and not a compiled plugin, or ask the aircraft creators for better support of direct controls that don't rely on the virtual cockpit. Alternatively, you can make the cap itself in your cockpit attached to another switch, which will send the cap opening command to the simulator.

      This is one example of the difficulties you can face when using custom aircrafts, which can usually be solved with some know-how.

      Delete
  3. I see it is not easy... only hope that we in XP world could have a PMDG equivalent as state of the art for building cockpits. Even if is not a freeware, I would be glad to pay a reasonable amount for it, considering the investment in time and money one involves in this enterprise... and thanks for tools like Arsdimx that for many of us make it possible in a reasonable time frame.

    ReplyDelete
  4. Mr. Roman, Good morning please can you tell me if the encoder reference magnetic encoder AS5600 would be viable for the ArdSimX2 axes project, thanks for your response.

    ReplyDelete
    Replies
    1. I'm waiting for AS5040 sensors now from AliExpress, this encoder will be first that I plan to add into ASX2 firmware. Any other, including AS5045, AS5600 will be considered too.
      Vlad

      Delete
  5. Greetings to all members of the forum, I want to share this link on how to program AS5600 encoder for analogous output, is to understand how this type of encoders works, later Mr. Roman will provide the firware in a short time so that ASX2 work in the axes of command, I just want you to explain if you work with ABI / UVW / PWM or I2C, thanks for your collaboration.

    http://ams.com/eng/Products/Magnetic-Position-Sensors/Angle-Position-On-Axis/AS5600

    the price is very cheap about US $ 19 Dollars 10 pieces including shipping.

    ReplyDelete
    Replies
    1. Thanks, but we have all needed documentation.

      The main goal is to write our own data exchange functions for each device used in ASX (displays, sensors, etc.). No any existed library are used in our interface (except Ethernet).

      All I need is technical datasheets for every used devices.

      We will place all needed links and instructions in this Blog (or on the website) related to all needed components, like this on this page - http://ardsimx.blogspot.ru/p/axis-input-sensors.html

      Regards,
      Vlad

      ..

      Delete
  6. Thanks for your reply, we will be pending

    ReplyDelete