Jump to content
The simFlight Network Forums

HBE66

Members
 View Profile  See their activity

  • Posts

    30

  • Joined

  • Last visited

 Content Type 

Posts posted by HBE66

  1. FSX InfoDB - new to FSX, or need that special something?

    in User Contributions

    Posted

    One thing I always found very enoying about FSX, every time you want to freshly setup your FSX, you need to search together all the information you need and last ages untill youve finally got it installed.

    Or you want to discover something new, but first you have to spend hours in google and try 7 things that wont work properly.

    So I recently started a little InfoDB and made it public, for everyone to enjoy:

    www.HBE66.com

    If you have any contributions or even corrections, everything is welcome ;-)

  3. J41 Macro by Question

    in User Contributions

    Posted

    hey, thats quite simple, place the macro file in your <fsx>\modules directory

    and then startup fsx

    then open up fsuipc and go to buttons and switches

    now press the button you want to assign (maybe choose "aircraft specific" aswell)

    and then select the macro file from the dropdown on the right

    if you can open up the dropdown you might need to activate "select for fs control" (but im not 100% sure about this point)

    now, in your macro file you have several numbers

    you have to fill these into the parameter field for the according button

    but you are probably going to have the difficulty that most buttons wont be recognized of the saitek panel/s - where the program SPAD can help, but its not a reliable solution in my opinion

    alternatively - probably the better solution

    i gave up on the saitek panels and got the mcp combo panel from vrinsight

    saitek is good for the basics, but the panels wouldnt please me...

    then you can use this HERE

    theres more to come on that page btw ;-)

  7. Uncalibrateable axis since fsuipc update

    in FSUIPC Support Pete Dowson Modules

    Posted

    ive just checked the axis assignments, and it seems the assignments have gone to dev-null :grin:

    i can now actually see things moving in the calibration

    just that even with calibration, things still seem jumpy

    i set both min and max values for the used leavers, all without reverse zone

    all slopes are on 0 and i tried it with and without filter

    if i increase both mixture leavers, the right one moves smoothly, while the left one sort of hangs at the center and then jumps to the top when i reach the top

    and the throttle behaves even stranger, first the right one moves faster, then arround the center the left leaver overtakes the right one, and just before max the right one takes the lead again :shock:

    can be entertaining, but when trying to handle an aircraft its a pain :mrgreen:

  8. Uncalibrateable axis since fsuipc update

    in FSUIPC Support Pete Dowson Modules

    Posted

    You have others? Without staying in thread I'm sorry but I cannot keep track of different folks' complaints!

    im not complaining, its a masterpiece you have developed there, im rather looking for a solution :grin:

    Where are you looking?

    fsx 3d cockpit: when i push both throttles to full power, one goes full and the other only half

    and basically the same problem with the mixture leavers

    So it does recognise axes, even though you just said is doesn't? You seem confused. The calibration section only sees assigned axes. If oyu don't assign them in FS or FSUIPC you cannot calibrate them.

    There's no difference between 4.60 and 4.645 or any in-between increments in any of that.

    Pete

    could it be that the axis assignments have dissapeared after the update?

  9. LUA + vriMCP = Altitude problems

    in FSUIPC Support Pete Dowson Modules

    Posted

    hehe, thank you for the offer, but ill try managing myself :wink:

    dont want to ask too much

    id probably have to think through everything myself too

    to be sure everything fits logically

    somehow the antiice buttons bug me, but maybee theres also no other reasonable way :grin:

    would you mind if i post your coding on my future site hbe66.com ?

    im thinking of linking my fsx experiences and things learned on there

    basically as a refference and so others can also enjoy an easier experience :grin:

  14. PFC and MCP connection issues

    in FSUIPC Support Pete Dowson Modules

    Posted

    lol, it seems i have understood something wrong :grin:

    Is this a newly connected VRInsight MCP COmbi you are wanting to use FSUIPC with?

    new, but not that new

    ive used it on the prior fsuipc version 4.60a

    Which PFC devices do you have?

    i assume i dont have any PFC device :blink:

    its only the vri mcp panel im trying to connect

    then i also have some saitek stuff, but that basically works

    What COM device did you use to have the PFC device connected ot?

    i think this question should be cleared =)

    serialfp2 starts with com4 and if thats used its com10

    I'm not that surprised. Why are you using COM50? What happened to COM11 through to COM49? Is it correctly created in your VSPE?

    does that matter?

    i basically thaught ill leave some space between one range and the other

    having the actual hardware link bellow 50 and the virtual ports above

    Pardon? If you don't want to use SerialFP2 you must program everything in the VRI device(s) yourself.

    i basically closed down serialfp2 and vpse because the pfc check wouldnt list any com port

    once those 2 applications wherent running, i could refresh and i had a port to choose from

    probably ill need to disable the pfc check somehow and carry on as i did with 4.60a

    thank you pete

  15. PFC and MCP connection issues

    in FSUIPC Support Pete Dowson Modules

    Posted

    hi pete :grin:

    ive now got 4.645 installed (thaught ill start a new thread for this)

    ive updated the ini file with the following, according to the vri pdf:

    [VRInsight]

    1=COM10, COM50

    [VRInsight.FMER]

    Lua=JS41_VRIH.lua

    DriverReads=YES

    DriverWrites=YES

    when i now start fsx, the PFC control connection check starts up, and sais:

    version of fsuipc module: FSUIPC okay. all options available 4.645

    com serial port port connection: none

    so i click, change port and COM4 shows up in the dropdown

    soo i select COM4 and click retry

    it takes a while and then i get "COM4 open okay"

    but bellow everything shows a red X

    next to "mode control panel (MCP) connection:" i get "No expected result received!"

    which is the panel im using

    what can this be?

    PS: if i change the com10 in the ini to com4, it will show com10 in the dropdown

    and i tried loging some com-port action if that might be any help

    PFCFSX.log

    what i found kind of strange about the fsuipc.log was:

    1591 VRI port 1 "COM10" opened

    1591 VRI driver port 1 "COM50" failed to open

    i presume it is correct if i dont run serialFP2 nor portemulator

  16. LUA + vriMCP = Altitude problems

    in FSUIPC Support Pete Dowson Modules

    Posted

    aaah my bad, i forgot to update the footer, i have 4.60a installed =)

    but ill try updating to 4.645 anyhow - thank you two for the tip

    and im sorry, i didnt want to put you under pressure kosta :grin:

    ive got tons of stuff to do too, tipical end of year without hollidays :cry:

    i was just unsure if you where still following this thread

    ill be waiting anxiously for your update :)

  19. LUA + vriMCP = Altitude problems

    in FSUIPC Support Pete Dowson Modules

    Posted

    thank you very much kosta!

    somehow i cant seem to manage it

    i tried:

    -- Test Lua			1

-- AP Course Left		6
-- AP Course Left Fast		7
-- AP Course Right		8
-- AP Course Right Fast		9
-- AP Course Press		10

-- AP Speed Left		11
-- AP Speed Left Fast		12
-- AP Speed Right		13
-- AP Speed Right Fast		14
-- AP Speed Press		15

-- AP Heading Left		16
-- AP Heading Left Fast		17
-- AP Heading Right		18
-- AP Heading Right Fast	19
-- AP Heading Press		20

-- AP Altitude Left		21
-- AP Altitude Left Fast	22
-- AP Altitude Right		23
-- AP Altitude Right Fast	24
-- AP Altitude Press		25

-- AP V-Speed Press		30


-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 

if VRImodel == nil then
  VRIdevice = "COM4"
  VRIdriver = "COM255"
end

cspeed = 115200 
handshake = 0  
minsize = 8
maxsize = 8

dev = com.open(VRIdevice, cspeed, handshake)
if dev == 0 then
   ipc.log("Could not open VRIdevice port")
   ipc.exit()
end

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 

Var = ""
Speed = 0
Control1 = 0
Control2 = 0

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 

if ipcPARAM == 1 then 
  ipc.control(66587, 8031)  
  ipc.display("Test...")


-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 

-- AP COURSE LEFT
elseif ipcPARAM == 6 then
  Var = "L:AP_CRS_Left"
  Speed = 1
  Control1 = 66587
  Control2 = 26701

elseif ipcPARAM == 7 then
  Var = "L:AP_CRS_Left_Fast"
  Speed = 5
  Control1 = 66587
  Control2 = 26701


-- AP COURSE RIGHT
elseif ipcPARAM == 8 then
  Var = "L:AP_CRS_Right"
  Speed = 1
  Control1 = 66587
  Control2 = 26702

elseif ipcPARAM == 9 then
  Var = "L:AP_CRS_Right_Fast"
  Speed = 5
  Control1 = 66587
  Control2 = 26702


-- AP COURSE PRESS
elseif ipcPARAM == 10 then
  Var = "L:AP_CRS_Press"
  Speed = 1
  Control1 = 66587
  Control2 = 2672
end

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 

-- AP SPEED LEFT
if ipcPARAM == 11 then
  Var = "L:AP_SPD_Left"
  Speed = 1
  Control1 = 66587
  Control2 = 26801

elseif ipcPARAM == 12 then
  Var = "L:AP_SPD_Left_Fast"
  Speed = 10
  Control1 = 66587
  Control2 = 26801


-- AP SPEED RIGHT
elseif ipcPARAM == 13 then
  Var = "L:AP_SPD_Right"
  Speed = 1
  Control1 = 66587
  Control2 = 26802

elseif ipcPARAM == 14 then
  Var = "L:AP_SPD_Right_Fast"
  Speed = 10
  Control1 = 66587
  Control2 = 26802


-- AP SPEED PRESS
elseif ipcPARAM == 15 then
  Var = "L:AP_SPD_Press"
  Speed = 1
  Control1 = 66587
  Control2 = 2681


-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 

-- AP HEADING LEFT
elseif ipcPARAM == 16 then
  Var = "L:AP_HDG_Left"
  Speed = 1
  Control1 = 66587
  Control2 = 26901

elseif ipcPARAM == 17 then
  Var = "L:AP_HDG_Left_Fast"
  Speed = 5
  Control1 = 66587
  Control2 = 26901


-- AP HEADING RIGHT
elseif ipcPARAM == 18 then
  Var = "L:AP_HDG_Right"
  Speed = 1
  Control1 = 66587
  Control2 = 26902

elseif ipcPARAM == 19 then
  Var = "L:AP_HDG_Right_Fast"
  Speed = 5
  Control1 = 66587
  Control2 = 26902


-- AP HEADING PRESS
elseif ipcPARAM == 20 then
  Var = "L:AP_HDG_Press"
  Speed = 1
  Control1 = 66587
  Control2 = 2691


-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 

-- AP ALTITUDE LEFT
elseif ipcPARAM == 21 then
  Var = "L:AP_SPD_Left"
  Speed = 1
  Control1 = 66587
  Control2 = 3920

elseif ipcPARAM == 22 then
  Var = "L:AP_SPD_Left_Fast"
  Speed = 10
  Control1 = 66587
  Control2 = 3920


-- AP ALTITUDE RIGHT
elseif ipcPARAM == 23 then
  Var = "L:AP_SPD_Right"
  Speed = 1
  Control1 = 66587
  Control2 = 3921

elseif ipcPARAM == 24 then
  Var = "L:AP_SPD_Right_Fast"
  Speed = 10
  Control1 = 66587
  Control2 = 3921


-- AP ALTITUDE PRESS
elseif ipcPARAM == 25 then
  Var = "L:AP_SPD_Press"
  Speed = 1
  Control1 = 66587
  Control2 = 281


-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 

-- AP V-SPEED LEFT
elseif ipcPARAM == 26 then
  Var = "L:AP_VS_Left"
  Speed = 1
  Control1 = 66587
  Control2 = 283

elseif ipcPARAM == 27 then
  Var = "L:AP_VS_Left_Fast"
  Speed = 10
  Control1 = 66587
  Control2 = 283


-- AP V-SPEED RIGHT
elseif ipcPARAM == 28 then
  Var = "L:AP_VS_Right"
  Speed = 1
  Control1 = 66587
  Control2 = 283

elseif ipcPARAM == 29 then
  Var = "L:AP_VS_Right_Fast"
  Speed = 10
  Control1 = 66587
  Control2 = 283


-- AP V-SPEED PRESS
elseif ipcPARAM == 30 then
  Var = "L:AP_VS_Press"
  Speed = 1
  Control1 = 66587
  Control2 = 283
end


-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 

val = 0
if ipc.readLvar(Var) == 0  then
  val = 1
end

ipc.control(66587, 8031)

ipc.writeLvar(Var, val)

for n=1, Speed, 1 do

  ipc.control(Control1, Control2)

end

buffer = ipc.readLvar(Var)/100
com.write(dev, string.format("ALT%03d", buffer), 8)

    but it sets the alt on the panel to 0 (where it remains)

    and the fsx alt changes according to the trigers

    so i then tried the second part with the function

    but i cant follow you there

    i tried copy-pasting your code into mine and adapted the variables

    but nothing seemed to change in fsx

    after turning the knob a while fsx suddenly crashed =)

  22. LUA + vriMCP = Altitude problems

    in FSUIPC Support Pete Dowson Modules

    Posted

    hi pete, thats more or less what im doing =)

    only that im doing that by lua what guenseli did by macros there

    which has the advantage that i can also use the fast turning function of the mcp panel

    im not reading/writing anything - but i think im going to need it

    the only thing that the lua does is to send commands to fsx, when a button is triggered through fsuipc

    from that point i would think; ok so now "button press" causes to change the altitude by 100 (which is the value change on the panel), so the altitude goes up by 100 - but it doesnt always happen

    so in both cases the altitude on panel and fsx are not synchronized

    my guess is, that sometimes a turn of fast-fast-slow gets recognized as fast-slow-slow-slow-slow ie.

    so the altitude changes by 1000+100+100+100+100 instead of 1000+1000+100 for egsample

    which is why i was/am trying to figure out if there is a way to overcome this and

    - read the altitude from one side (ie. fsx)

    - to write it to the other side (ie. panel)

    do the methods to read/write such values differ from aircraft to aircraft?

    isnt it "just" a value in fsx? that can be provided by ie. fsuipc

  23. LUA + vriMCP = Altitude problems

    in FSUIPC Support Pete Dowson Modules

    Posted

    i need some help geting my mcp panel working for the js41

    sofar i managed creating a lua to control crs, spd, hdg, alt and v/s

    and sofar the heading works nicely, im not quite sure about the course

    because there is no display for it on the mcp

    the speed doesnt yet work, as the js41 has several speeds that can be set

    but thats a topic i could leave till later

    my biggest headache ist the altitude

    1. after starting fsx i get 4000ft on the panel and 10000 in fsx

    2. eventhough i managed controlling the altitude more or less (assigning both slow and fast turning of the knob)

    with fast turning it still happenes that the values mushup ie. 5300 and 11000 instead of 5000 and 11000 or vise versa.

    obviously 5000 and 5000 would be even better, but id already be glad with the other result :grin:

    in my point of view, i need something to check the panels altitude and "write" it to fsx, or the other way arround

    but i could be heading in the wrong direction

    has someone got me some advice?

    my lua:

    -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 

Var = ""
Speed = 0
Control1 = 0
Control2 = 0

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 

if ipcPARAM == 1 then 
  ipc.control(66587, 8031)  
  ipc.display("Test...")


-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 

-- AP COURSE LEFT
elseif ipcPARAM == 6 then
  Var = "L:AP_CRS_Left"
  Speed = 1
  Control1 = 66587
  Control2 = 26701

elseif ipcPARAM == 7 then
  Var = "L:AP_CRS_Left_Fast"
  Speed = 5
  Control1 = 66587
  Control2 = 26701


-- AP COURSE RIGHT
elseif ipcPARAM == 8 then
  Var = "L:AP_CRS_Right"
  Speed = 1
  Control1 = 66587
  Control2 = 26702

elseif ipcPARAM == 9 then
  Var = "L:AP_CRS_Right_Fast"
  Speed = 5
  Control1 = 66587
  Control2 = 26702


-- AP COURSE PRESS
elseif ipcPARAM == 10 then
  Var = "L:AP_CRS_Press"
  Speed = 1
  Control1 = 66587
  Control2 = 2672
end

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 

-- AP SPEED LEFT
if ipcPARAM == 11 then
  Var = "L:AP_SPD_Left"
  Speed = 1
  Control1 = 66587
  Control2 = 26801

elseif ipcPARAM == 12 then
  Var = "L:AP_SPD_Left_Fast"
  Speed = 10
  Control1 = 66587
  Control2 = 26801


-- AP SPEED RIGHT
elseif ipcPARAM == 13 then
  Var = "L:AP_SPD_Right"
  Speed = 1
  Control1 = 66587
  Control2 = 26802

elseif ipcPARAM == 14 then
  Var = "L:AP_SPD_Right_Fast"
  Speed = 10
  Control1 = 66587
  Control2 = 26802


-- AP SPEED PRESS
elseif ipcPARAM == 15 then
  Var = "L:AP_SPD_Press"
  Speed = 1
  Control1 = 66587
  Control2 = 2681


-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 

-- AP HEADING LEFT
elseif ipcPARAM == 16 then
  Var = "L:AP_HDG_Left"
  Speed = 1
  Control1 = 66587
  Control2 = 26901

elseif ipcPARAM == 17 then
  Var = "L:AP_HDG_Left_Fast"
  Speed = 5
  Control1 = 66587
  Control2 = 26901


-- AP HEADING RIGHT
elseif ipcPARAM == 18 then
  Var = "L:AP_HDG_Right"
  Speed = 1
  Control1 = 66587
  Control2 = 26902

elseif ipcPARAM == 19 then
  Var = "L:AP_HDG_Right_Fast"
  Speed = 5
  Control1 = 66587
  Control2 = 26902


-- AP HEADING PRESS
elseif ipcPARAM == 20 then
  Var = "L:AP_HDG_Press"
  Speed = 1
  Control1 = 66587
  Control2 = 2691


-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 

-- AP ALTITUDE LEFT
elseif ipcPARAM == 21 then
  Var = "L:AP_SPD_Left"
  Speed = 1
  Control1 = 66587
  Control2 = 3920

elseif ipcPARAM == 22 then
  Var = "L:AP_SPD_Left_Fast"
  Speed = 10
  Control1 = 66587
  Control2 = 3920


-- AP ALTITUDE RIGHT
elseif ipcPARAM == 23 then
  Var = "L:AP_SPD_Right"
  Speed = 1
  Control1 = 66587
  Control2 = 3921

elseif ipcPARAM == 24 then
  Var = "L:AP_SPD_Right_Fast"
  Speed = 10
  Control1 = 66587
  Control2 = 3921


-- AP ALTITUDE PRESS
elseif ipcPARAM == 25 then
  Var = "L:AP_SPD_Press"
  Speed = 1
  Control1 = 66587
  Control2 = 281


-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 

-- AP V-SPEED LEFT
elseif ipcPARAM == 26 then
  Var = "L:AP_VS_Left"
  Speed = 1
  Control1 = 66587
  Control2 = 283

elseif ipcPARAM == 27 then
  Var = "L:AP_VS_Left_Fast"
  Speed = 10
  Control1 = 66587
  Control2 = 283


-- AP V-SPEED RIGHT
elseif ipcPARAM == 28 then
  Var = "L:AP_VS_Right"
  Speed = 1
  Control1 = 66587
  Control2 = 283

elseif ipcPARAM == 29 then
  Var = "L:AP_VS_Right_Fast"
  Speed = 10
  Control1 = 66587
  Control2 = 283


-- AP V-SPEED PRESS
elseif ipcPARAM == 30 then
  Var = "L:AP_VS_Press"
  Speed = 1
  Control1 = 66587
  Control2 = 283
end


-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 

  val = 0
  if ipc.readLvar(Var) == 0  then
    val = 1
  end

  ipc.control(66587, 8031)

  ipc.writeLvar(Var, val)

  for n=1, Speed, 1 do

    ipc.control(Control1, Control2)

  end

    thank you!

    FSC causing keypresses?

    in (Former) FS Commander Support Forum

    Posted

    my bad, maybe i should make it a little clearer =)

    you probably know, if you press "S" in fsx the camera view changes

    ie. from cockpit to exterior view

    (assuming 3d cockpit is used)

    well it seems as if fsc would be pressing "S" from time to time

    its not always an equal time interval unfortunately

    first i thaught it might be a different addon

    but then i tried flying without fsc open and the problem didnt occur anymore

    i dont know if it might also be causing other key presses

    but "S" is quite an obvious one

    my thaught comes from vbscripting, as i sometimes use keypresses there

    to controll gui actions ie. filling the online form for the pizza order

    nb: i dont use vbscripts within or while fsx is running...

    so i thaught fsc might be using a similar technique

    theoretically the programmer should know

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.