start eng 1 Overhead Cockpitsonic

[iceblue77]

Hi,

 

I'm having some trouble trying to use my overhead, and want to discard if it is a software of hardware problem, the situation is this, using overhead cockpitsonic, project magenta and FSUIPC with wideFS modules. I go to FSUIPC in FSX module > Logging > Select IPC reads and IPC writes and send to console window.. then i Move the selector in the overhead Engine two and it shows in the console the different values it writes:

 

2188515 WRITEex 5611, 1 bytes: 00 for GRD

2236375 WRITEex 5611, 1 bytes: 01 for OFF

etc

 

But when i do the same for ENGINE START 1

 

nothing happens!!!

 

Have same trouble for 

RUNWAY TURN OFF lights L and R

and for WHEEL WELL

 

All the other switches and encoders send info to FSUIPC console log.

 

I tried with 3 different versions of drivers for Overhead Cockitsonic and same result.

Check the wires in the overhead and everything seems right, change the encoder rotary for the engine 2 and same result.

 

Kind of lost here.... 

 

If there are no info showing in the console, could be a bad driver or mostly a hardware problem??

 

thank you very much!

Edited October 16, 2014 by iceblue77

[Pete Dowson]

I'm having some trouble trying to use my overhead, and want to discard if it is a software of hardware problem, the situation is this, using overhead cockpitsonic, project magenta and FSUIPC with wideFS modules. I go to FSUIPC in FSX module > Logging > Select IPC reads and IPC writes and send to console window.. then i Move the selector in the overhead Engine two and it shows in the console the different values it writes:

 

If there are no info showing in the console, could be a bad driver or mostly a hardware problem??

 

I'm not really responsible for either Cockpitsonic hardware support nor Project Magenta support. But I do use a Cockpitsonic overhead, much altered since first delivery, and not using their driver because of the changes. however, here goes:

 

It should be writing to 5611 for Engine 2 -- 0=GND, 1=OFF, 2=CONT, 3=FLIGHT.

For Engine 1, the offset is 5610, with the same values.

 

I would guess that there is a connection problem to the switch. Try making sure all the cables in that area are firmly seated. I found that unplugging them and plugging them in again sometimes helps make better contact. Also I found that the workmanship on some of those little "BOBs" (break out boards) leaves something to be desired, with dry joints and incorrect wiring on several in mine. I was disappointed with the standard, and eventually replaced some parts, rewired others and resoldered several of the BOB connection boards. I replaced the Duct Pressure and Cabin Pressurisation gauges with proper dual-needle Flight Illusion ones. (Actually a friend of mine did all the work, as my eyesight leaves a lot to be desired these days).

 

If you cannot find the problem I suggest you contact Cockpitsonic support, see if they will respond. don't they have a place in Canada? Mine came from Germany, but via a UK dealer who doesn't deal with them any more.

 

Good luck!

Pete

[iceblue77]

Thank you very much for your answer, and sorry for the late reply!

 

I will try your recommendation, maybe some wire is wrong in the BOB, I tried to change the encoder and this didn't work, maybe is the wires... lets see..

 

And I have another question? how you make it work without the driver? because if I don't execute the driver PM doesn't recognize it...

 

I appreciate your answer even knowing that is not a FSUIPC problem... thank you very much Pete.

 

cheers

[Pete Dowson]

And I have another question? how you make it work without the driver? because if I don't execute the driver PM doesn't recognize it...

 

I'm a programmer, I wrote my own. All of the hardware in my cockpit is handled by my own software. I don't like other uncontrolled (i.e. not in my control) software handling any of it. Since I program it I can adjust it to suit me exactly! ;-)

 

Regards

Pete

[iceblue77]

That's GREAT!  bad luck for me that im not and really this overhead is  real pain!!!!

 

Thank you!

 

I will update if I get some result after rewiring!

 

BTW do you know how is the connection in this BOB?

 

I sent several mails to cockpitsonic but after send me a picture of the BOB circuit no more communication... and after search I found a lot of people really disappointed with their customer service...

 

thanks

[Pete Dowson]

BTW do you know how is the connection in this BOB?

 

No, sorry. You might be able to trace the wiring. With a couple of the BOBs I just used a hot soldering iron to remake all the joints in case one or more was dry. That fixed the problems I had.

 

Pete

[iceblue77]

Thank you.

[iceblue77]

Hi,  again!

 

Just solder again the wires and nothing happen... Maybe I'm not doing it right.

 

I have open the FSUIPC in logging... i move the engine 2 and I see: WRITEex  5611, 1 bytes: 02  etc

But after soldering again as i said and change the encoder also, there are no info when i move...

 

Just a question Do you know if in yours both engines are connected to the cabin climb instrument in a extension BOB??with center pin connected in the number 20 and the other parallel to each other?except the orange that is opposite?

 

thank you again and sorry for not be a related question with FSUIPC!

 

thanks

[Pete Dowson]

Just a question Do you know if in yours both engines are connected to the cabin climb instrument in a extension BOB??with center pin connected in the number 20 and the other parallel to each other?except the orange that is opposite?

 

Sorry, I don't know, and I'm not in a position to take a look at present. With my poor eyesight I leave all that stuff to my good friend Thomas, but he lives a long way away and isn't due to visit till December earliest.

 

I know that with some of the stuff on that overhead we simply gave up and re-wired it through some Leo Bodnar boards instead. We also replaced the Duct Pressure and Cabin Pressure gauges with proper dual-needle ones from Flight Illusion.

 

I think you need a friend like Thomas who is good with hardware! I am just very lucky in that department.

 

Pete

[Thomas Richter]

Hi Pete,

 

your Start-switches are connected to a separate start-switch board from Cockpitsonic that controls also their solenoids.

[Pete Dowson]

Hi Pete,

 

your Start-switches are connected to a separate start-switch board from Cockpitsonic that controls also their solenoids.

 

Would that be the same as on iceBlue77's CS overhead? Can you help him at all? I realise it must be difficult from memory of my overhead!

 

Pete

[Thomas Richter]

Hi Pete,

 

no he has apparently the standard version where the switches are connected to the BOB of the pressure gauge.

As he describes that the Start-switch 1 not showing changes in Offset 5610, also not after re-soldering and replacing the rotary, it looks like the common cable for the rotary doesn't work or the BOB is broken for that function. There are SMD diodes/ resistors on the BOB for the coded connections (lines/ rows).

[iceblue77]

Yes, it is as you said  EW321, i also tried to change the common to another of the non-used common but doesnt work, i think that will replace it for a leo bodnar or maybe try to get one of this BOB new. because also the wheel well and turn off rwy doesnt work too... something is wrong in this BOB.and change the SMd diodes seems really dificult for my level with the soldier :))

 

My question is how with a leo bodnar the overhead will work all together? could be that possible only add in the bodnar the  items that doesnt work ?? and also add part of the FWD OVHD that is not wired.

[Thomas Richter]

Hi,

My question is how with a leo bodnar the overhead will work all together? could be that possible only add in the bodnar the  items that doesnt work ??
and also add part of the FWD OVHD that is not wired.

No that is not possible because the BOB is connected to different Inputs and Outputs (Annunciators). In Cockpitsonic driver you cannot disable some functions of a BOB and others not but only the whole BOB of a gauge.

That means the driver would always overwrite those switch inputs with what it believes is the actual state.

The only way then would be to disable the BOB of that gauge and connect all Inputs and Outputs of that BOB to a different I/O board. Or getting a replacement BOB.

[iceblue77]

Thanks Thomas, I will try to go for a replacement and see whats happen...

 

It is being a real headache!!!

 

Thanks Pete and Thomas I really appreciate the help. Will update as soon have it working properly.

 

Cheers.