Interfacing aeroSystem737 avionics software with homemade 737MCP using SOIC

[glynndockry]

Hi, this is myfirst post, hope its in the correct area!
I have usedopencockpit boards to build my own MCP. I have this working with the standardFSUIPC offsets. I now want to start using my MCP with aeroSystem737 avionics software. The course,IAS, and Heading all work as they use the standard offsets. The MCP altitudeand VS use Aerosoft offsets. I have limited experience with SOIC and needhelp/examples of how to implement the Aerosoft requirements into SOIC.

Regards, Glynn

From Aerosoftwebpage http://www.aerosoft.com.au/aerosoft_australia/hardware.html




SENDING A COMMAND TO AEROSYSTEMS
Sending a command is very simple. A command is sentusing the addresses below.

Address description length
7370 command 1 byte
7371 value small integer (2 bytes)

Before you send a command you must first make surethat address 7370 hex has a value of 0. if it is 0 you can write a command tothat address, with an optional value to address 7371 hex. When aeroSystems hasfinished processing the command, aeroSystems will set 7370 hex back to 0,informing you that it’s ready to accept another command.

Here’s an easy example:

If value at address 7370 hex = 0 then
begin
FSUIPC begin request
write a command to address 7370 hex
write an optional value as a small integer(-32767 to +32767) to address 7371 hex
FSUIPC send request
end

So remember, if 7370 is not 0 you cannot send acommand until aeroSystems resets it back to 0.


Description

MCP
MCP altitude divided by 100. eg. to set MCP to37500 write 375
Vertical speed divided by 100



Command
(decimal)

1
2

10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26


Value
(decimal)

0 to 500
-79 to 60

none
none
none
none
none
none
none
none
none
none
none
none
none
none
none
none
none


Description

MCP
MCP altitude divided by 100. eg. to set MCP to 37500 write 375
Vertical speed divided by 100

flight director toggle (read status from FSX to determine initial state)
AT ARM toggle (read status from FSX to determine initial state)
Push N1
Push SPEED
Push VNAV
Push LVL CHG
Push HDL SEL
Push LNAV
Push VOR/LOC
Push APP
Push ALT HOLD
Push V/S
Push CMD A
Push IAS/MACH change over
Push TOGA takeoff mode 1 - pilot pitches aircraft manually for takeoff
Push TOGA takeoff mode 2 - autopilot pitches nose-up at Vr and takes off by itself (auto takeoff)
Push CMD B

[brian95]

I too have this problem as I've only been using standard FSUIPC offsets.
I emailed the developer who replied and said that you need to write your own software to access the two offsets listed on the web page, or otherwise it would be easier in the long run to buy pre-built electronics.
Sorry I can't be of more help, but seeing as you've already built your MCP you're already ahead of me.
Regards,
Brian

[fordgt40]

Glynn

This link shows you how to read and write to offsets using SIOC

http://www.lekseecon.nl/howto.html#writeFSUIPC

If you are using non standard FSUIPC offsets, then you may need to define them within FSUIPC - its in the docs. Not tried using non standard ones yet, so why not try just referencing the offset in SIOC and see if it works

David