USB-Expansion & MasterCard. 5-th pin input problem

[601]

Hi there!

A320homecockpit wrote at OC forum:

I have a strange problem with my inputs.
I got 2 mastercards connected to usb expansion
both mastercards receive 5 volt (checked) from a computer power supply.
I have some swithes connected (not pushbutton but switches with OFF-ON)
Those switches which are connected to the last input of each inputblock (input 8 - 17 - 26 - 35 - 44 - 53 ...) and are in ON position when the controlador program or the SIOC start are not seen as ON but as OFF. When I switch the button of and on again then it is seen and everything works fine. Also for pushbuttons this is no problem because because they are not making contact upon start of the programs and when pushed they are seen.

I have send some emails to Niko Kaan in Holland and he also confirmed he has got the same problem as I have!!!

We’ve faced the same problem. An initial value of logical inputs 8, 17, 26, … (the 5-th physical pin in each group) is wrong. If we change the state of any input in the same group (not exactly the 5-th) everything starts working fine.

A starting value of 5-th input depends on number of mastercards in sioc.ini: if number of mastercards is 1 or 2 – the initial value of 5-th input is “1”; if 3 or 4 mastercards in use – the initial value of 5-th input is “0”.

Does anybody know, is there a solution?

Regards,
Yakov.

[kiek]

Yakov,
I don't think it is of much use to post this problem here. It seems to be something to be solved by the developers of IOcards and/or SIOC.

Regards,
Nico Kaan

[601]

Yakov,
I don't think it is of much use to post this problem here. It seems to be something to be solved by the developers of IOcards and/or SIOC.

Regards,
Nico Kaan

Hi Nico!

I`ve posted this question at opencockpits forum, but I have little hope for quick bug fix, actually…

So I`m just looking for a different ways to overcome this issue (it`s really crucial for us now, because the one kind of our panels is specially designed to use ALL 9 inputs in a group). It forces us to find any possible way to get it work properly.

May be someone has a positive experience -- that is why I have posted here…

Now we are going to try to reset a Mastercards power, may be it can help – will see…

Yakov.

[kiek]

Hi Yakov,
One way to get around it is to rewire your inputs such that you connect a switch terminal (preferrably 1 of N of a rotary switch) that most likely is off at cockpit start up to logical input 9 of a group of 9. Then you have no problems.

But I'm very curious ofcourse to your findings.

Cheers,
Nico

[601]

Thank you, Nico!

But we don’t deal with a rotary switch. We have a mechanical radio-compass panel that provides us with a binary code of frequency set. So we are not able to predict which frequency is set when cockpit starts…

[601]

We’ve found a solution which works for us: a Mastercards’ power reset helps!

We use a relay that is controlled by SIOC-script – relay resets the Mastercards’ power when SIOC stars, and bingo – we have no mistakes anymore!

Regards,
Yakov.

[kiek]

Hi Yakov,

That is a nice 'trick' indeed!

I've noticed that this problem also disappers if you start up SIOC for the second time (while MC is still powered). Hence, another solution for this problem, costing no extra hardware, would be to make a script that starts SIOC, stops it after 2 seconds and restarts it ... Worth a try, I think.

Nico