Simple Feedback Yoke (OpenCockpits DCmotors Card)

[Jay]

Hi everybody

I'm trying to build a simple FFB yoke as an alternative to still very expensive products out there. I'm calling it "simple FFB" because the idea is very simple. The yoke's axis will freely move and rotate when the aircraft is still. With raising airspeed, tensors will tighten four bungee cords and build up a tension forcing the yoke to it's central position.
After some research I decided to buy Opencockpits DCmotors card to do the job.
Although I would like to add more motors in the future for runway vibration, prop wash effect and other forces, I will begin with simple setup using only one motor driving the tension of the bungee cords.

I'm quite good with mechanical stuff, basic/advanced understanding of electronics but newbie to coding. I also understand that most of you guys don't really want to become a full time tutors when it comes to beginners 
Therefore I set on the long and steep road of SIOC code learning even after very flustrating realisation that most of the manuals and tutorials available online are either badly translated or quite advanced to catch up with..
So far I set up my DCmotors card with one pot and one motor and managed to run simple test script provided within the card's original manual. That pretty much covered the "very" basics.

Now I am going through the pile of code examples trying to understand correct procedure and here I really need someone to give me a clue about what to do next.
Very simple description of my application could be "Airspeed Gauge driven by DCmotors card". Simply one DC motor and potentiometer, turning the motor into certain position
defined by IAS.

Could anyone pleeease point me the right direction?

My code (if we can call it that) 

////////////////////////////////////////////////////////////////////////////////
//
// SIOC Simple-FFB Yoke file
// Date 31/10/2015
// v 0.1
//
Var 100, Value 0 // Initialisation
Var 001, name Motor_1_out, Link USB_DCMOTOR, Output 1
Var 002, name Pot_1_value, Link USB_ANALOGIC Input 1, PosL 0, PosC128, PosR 255
Var 003, name IAS_from_FS, Link FSUIPC_IN Offset $02BC, length 4

[727737Nut]

Having built 3 sims using OC stuff here is my advice.  Drop it in the trash can and run! Fast!  Joking a little bit here but not much, the outputs card and relay card are the only thing I would remotely suggest using.  WAY  cheaper to go the Ardunio route and have much better results.  That being said, if you still want poor resolution and inconsistent results, I will help with the SIOC code as much as I can.

Rob

[Jay]

Thanks for you reply

I was tinkering with arduino and FS in the past and I think arduino community support is much greater however I thought that OC DCmotors cards will be fairly simple for my aplication
Low resolution is fine here as the card will only operate the bungee tensors.
The actual yoke reading for FS control will be done with Leo Bodnar's Axis card.
I am stuck with the next lines of the code   I understand that I need to divide the FSUIPC IAS value so I suppose under FSUIPS IN line will go somethink like this:
{
L0 = DIV &IAS ,128
{

Then I'm really confused about how to specify the behaviour for the motor and it's feedback from pot along wit IAS data from FS..
I would very much appreciate your help with this.
Thank you  Jay   

[Jay]

guys please, I don't think this is something too complicated for someone who understand SIOC code..
I'm even willing to appreciate your effort financially as there is much more work to this project then just the coding therefore I need to start rolling.
I only have few weeks for the whole build because I'll be away from my workshop for couple of months and really want to finish this before I leave.

Thanks Jay

     

[RayS]

This week is probably not the best week for a timely response. Some of the members are attending an annual worldwide event that has most of them fairly exhausted for the entire week.

I dont know SIOC but I'm in agreement that something like Arduino might be easier to interface in the long run.

More to come probably next week as members return from the event and slowly return to reality.