algerad3

IRIS-core, So I take it you are good for Now? IF you use the example i put together for the x52 pro and change the model from X52p to fip it should work. would love to see what you have going on . Oh, and welcome to the club.

A new directoutput for the X52 Pro? Does this affect the Fips as well?

If you want "force sensing " joystick then the only option is the Saitek X-65f. For pedals I use the saitek pros. I hear the combat pedals are good. As for the other questions , I am at a loss for answers.

Iris , give me a little time to sort through some issues and I will try to help with what i know /learned. This is still a learning experience for us.

Awesome.. It will be a minute before I can do anything . RL stuff at the moment.

Maverick, It should work on all directions. Make sure your stick is with out issues. I have it set up like you do on both my x52 pro and x65 Except I only use the four basic commands(u,d.l.r.) works perfectly. I don't think you should need the "directions in between". I have not gotten around to using the Hms So I can not answer that ....yet

hey guy's here is something we are trying to cook up for the X52 pro.

Digital Aura, we are working on getting the x52pro working on the DCS lineup. http://forums.eagle.ru/showthread.php?t=94174 You can control the leds with this project as they can be controlled via the dll. You can find the sdk in "c\\program files (x86)\\saitek\\directoutput\\sdk or C\\program filles\\saitek\\sdk. This is dependent on the drivers install.

me again, I can not quite figure out how to get the example to function correctly. It will not print "Gear1up on" just "gear1up off". it is like it is not receiving the change in the variable. Racking my skull on this one.

I got the X52 pro and my 4 fip to work together. Finally. sending commands to turn of the lights without crashing and banging. So on to the next step. try to send to dcs and make things happen. Gonna be a rough task as I still have not sorted out the data rec stuff. Since I got this far .... any advice would help..... again I post my "Masterpieces" :helpsmilie:for review. dcs export lua using sockets in the previous post and the new receiver is right here .. restart.lua

O.k a little progress here. Never mind the mess its still under construction. know it does not freeze black shark, info comes in but does not update. For know I will leave the data part alone and work on sending button commands. After I set up pages and callbacks for the fip. so 1) add fip pages and callbacks ( should be quick) 2) add button commands function 3) sort data update issue 4) clean up 5) make files for specific set ups ( 1 for x-52p only, 1 for fip only , 1 for fip and x52p combined ) 6) implement start up and modules sorter. ( start dcs , pick proper module , send command to open saitek prog.) To test the attached attempt you will need both files. ( export for dcs and restart to run the saitek x52p listener. have fun restart.lua Export.lua

I think I am getting it sorted .... Had to think about it for a minute or two. be back soon.

Making more progress....Kinda Back again..... Mixed bag of news. First foray at real programming has left me in a quandary. I have a listener socket set up with the saitek module ( hitting the lua for windows saitek module . 32 bit) As of right know I can not get the data to update on the mfd and after about a minute black shark freezes. I can still change pages and get things to work as desired only black shark frozen( not crashed ). When i shut down the saitek module without stopping the blackshark , it ( the sim) picks up where it left off. Weird stuff.. anyways I present my current works in progress in case anyone is willing to help/ or share their knowledge or want to tinker. would like to know where i made the wrong turn.... Export.lua restart.lua

I have had the regular and the pro for over five -six years. No real complaints yet ( other than trying to program the pro's mfd. The joystick seems a bit loose compared to the others I demo'd but like anything else you get used to your equipment. The rotaries on the throttle tend to get particular when you rotate them.Sometimes you have to dial it into the right spot or it jitters. Again , you'll find the sweet spot and get used to it. I actually enjoy the x52 pro and it would be my fave if I had not also gotten the x65f. I still use the 52 ..... still a happy camper.

hey there peoples .... Slow going over here.. I believe I have found myself beyond the boundaries of "cut and paste " programming. Got some trial and error stuff going on. Have not forgotten the team. I hope everyone else is making some progress. I hope to have something to show here soon.

Oh, Crap.... Missed the fin details.. My apologies. As for the real question...I don't know...

So now , we need to get a little more control over the button functions so that it stops at the required increments. I believe I need to work through the "end" and place them properly. Once that is done, I can the create a script that utilizes the functions better and in a more organized fashion. One other question....does your pages jump around? One minute your are looking at fuel and the next it jumps to alt ,then mode page back to something else?

Yes, why yes you can.... The answer you seek ...here: https://play.google.com/store/apps/details?id=com.portman.panel.uh1h&feature=search_result And here: https://play.google.com/store/apps/details?id=com.portman.panel&feature=search_result Start from the beginning here for more detailed info. http://forums.eagle.ru/showthread.php?t=97890

I am using the x52pro right now. The fip's also causes a crashes only they are more random. This issue I know is due to my lack of programming style/ skills. On a side note: My skills are slowly improving.

Just some quick and dirty tinkering. I am reducing the crashes on the buttons. as the button states are for now.... We are indeed calling and sending things out of order. I changed the Radiocallback function as noted below and was able to just roll the wheel as fast as i wanted, but also the wheel takes a little time to stop , sometimes it rolls on its own . Still working out the kinks. Also , you have to have fine control when using the scroll wheel with this config as it sometimes reads more than one press. function RadioCallback(model, index, state) function LuaExportBeforeNextFrame() -- NEW ADJUSTMENT. if rot ==1 then if bitSet(state, bitMask["rswup"]) then do GetDevice(48):performClickableAction(3007,-1) end elseif bitSet(state, bitMask["rswdown"]) then do GetDevice(48):performClickableAction(3007,1) end if bitSet(state, bitMask["rswc"]) then rot = rot+1 end end end end end I am not sure which Dll I am using as I have everything organized on my box at this time. I believe I have the first 64 release for this test.

Hey guy's , Again been busy. Real life is getting in the way of my sim life. I had issues with my scripts for awhile , could not get things working. Now that it is sorted out, I found the same thing Moburma had going on , every hit on the scroll wheels caused a crash. I will look at thew crash logs to verify ,but I think in a way this is a good thing. Now we some thing that may explain the crashes or an easier way to sort things out , I will play with both dll this afternoon( barring more interruptions.)

go to the option page and find the slot for the collective. Clear the assignment. Click the add button and then move the throttle. By default for some reason when you use the x52 ( pro and Non pro) collective is assigned to the slider. Just clear the command and add the throttle.

Just as the pro , the x52 uses a cable to connect the two pieces. Make sure both ends are secure ,even thought the power light is on the rest of the connection may be severed. Just the other day, my cable came loose , not out just loose and the lights flickered and I had erratic control. If that is not the case and you are a brave soul, tale a look inside for any loose wires/connectors. Also make sure the connection cable is not severed /shorted.

Sweet , I'll give it a go real soon and let you know.

Cool, I will use this as a learning tool for a bit and then ,if I don't figure it out will as for more help.