Jump to content
The simFlight Network Forums

Snooky

Members
  • Posts

    13
  • Joined

  • Last visited

Everything posted by Snooky

  1. Hey Pete, the configuration of our buttons and LEDs is nearly complete, but there are still some LEDs and buttons we don't really know about. We are still using the Bombardier CRJ-700. I hope you have some ideas where we can read the desired information from FSUIPC. I haven't found anything by now :( The first 2 LEDs indicate a failure in the generators, LED 1 for generator 1 und LED 2 for generator 2. I searched the offset status pdf but haven't found any offset related to generator or alternator failures. Then we have 2 LEDs indicating, that crossfeed is inoperable. You can see that here at the upper middle panel: http://www.digital-aviation.de/site/wp-d_pre1.jpg There is one LED for the left engine and one for the second engine. Then again, there are two LEDs named "BTL 1 armed" and "BTL 2 armed". I weren't even able to find out what BTL means. I always got to pages related to some military operations or something. You can find the LEDs here, right under the engine fire ones: http://flightsimx.s3.amazonaws.com/wp-c2d_day.jpg For all those LEDs we only need something to read a state like 0 = ok, 1 = failure to control the LEDs. The last problem I am currently facing is the altitude together with the pull up and ground proximity warning. I tried to light up the LEDs according to the aircraft altitude, but the altitude always seems to be absolute. I would rather like to have the altitude in relation to the ground height. For example, if we are flying to a valley we are 1000 meters high. Now we fly over a mountain, but don't change the absolute altitude. Then we are only like 200 meters high and the ground proximity warning would show up. Is there any offset providing this or can it be calculated from 2 offsets via luascript? Thanks in advance and keep up the good work! Snooky
  2. That was the basic idea i had, too :) Unfortunately i don't have FS or FSUIPC here, so i'll try it tomorrow. Little Endian would be best, though.
  3. Hey Pete, i recognized, that the dll used for interfacing fsuipc with java only functions as a wrapper calling the functions of the c dll. Do you maybe know by any chance in which way the fsuipc read and write functions want the data? It should be a byte array anyway, but in which order? Little Endian or Big Endian? Thanks Snooky
  4. I don't know if java is capable of middle Endian, but it can operate with both little and big endian or at least i could write methods that can. But for that i have to know in which way the bytes are given. Unfortunately i can't try it until monday. On monday i will read/write some 4 byte integers and try to determine the byte order. Thanks anyway, i will report back on monday!
  5. Hey Pete, i downloaded your FSUIPC SDK and found the java dll. So i started programming around a bit, and the read/write methods from FSUIPC provide the data in a byte-array. But there is no documentation along with the dll, and it seems the author has changed his e-mail address. I wrote to him, but mailer-daemon returned. Is there any doc about the dll, especially in which byte order the data has to be provided for writes and is provided from reads? Thanks Snooky
  6. Hey Pete, everything working now, i also fixed the issue with those paramaters by taking a user free offset and an lua plugin sending the control via ipc.control(control, paramater) whenever the offset changes from 0 to 1 or the other way around. Thanks again
  7. Thanks Pete, i'll try this tomorrow morning when I'm back at university and will report back with the control i use and the parameters needed, thanks :)
  8. Hi Pete, again we are facing 2 issues with our CRJ-700. First one: The radio stack is working a bit difficult here. Switching all the combinations of receiving/not receiving work, but we don't get any visual feedback of which one is actually receiving and which one not. Therefor we implented 2 LEDs representing the status of the com (receiving / not receiving). Since we have to use two buttons doing exactly the same, i can't get those LEDs working properly, so I decided to try a lua plugin, doing the following: Take 2 user-free offsets. Look up the value in Offset 3122. Write it to a variable. Then i found out, that you can determine the status of both coms from the value received, even though things like dme, nav1 and/or nav2 are up. So i decided to fake a flag for com1 and com2 receive status (1=receive, 0=off) to get the LEDs working with it. The values are the following: If value < 95, only com2 is receiving If 95 < value < 128, both are receiving If 128 < value < 160, only com1 is receiving If value > 160, both are receiving So i wrote a lua file named Ipcinit to load it when FS starts: function findCom() local n = ipc.readUB("3122") if n < 95 then ipc.writeUB("66C0", 1) ipc.writeUB("another userfree offset", 0) elseif n < 128 then ipc.writeUB("66C0", 1) ipc.writeUB("another userfree offset", 1) elseif n < 160 then ipc.writeUB("another userfreeoffset", 0) ipc.writeUB("66C0", 0) elseif n < 191 then ipc.writeUB("66C0", 1) ipc.writeUB("another userfree offset", 1) end end event.offset("3122", UB, findCom) another userfree offset is of course a real offset in the file. But this one is not working, there's no value displayed at 66C0 when monitoring it via FSUIPC. Any idea why we don't get a value here? The second issues is about controls sended via offset 3110. We found a control here to toggle the hydraulic switches for the engines, but the control needs a parameter which we are not able to send with the program we use. Is there any way to avoid this one, maybe through another user facility, faking an on/off flag for thosw switches? I tried to send the parameter by just putting it at the end of the control, e.g. 655552 for 65555, parameter 2, but that doesn't work. You helped us out many times now, so i thought you might be interested in what we are actually doing here. So here's a picture of our current progress (about 2 weeks old, we have built in more buttons now). http://img194.imageshack.us/img194/9282/imag0044y.jpg Thanks in advance Sascha
  9. I'll check this out when i'm back at university on thursday. First I will try the Mouse Macro facilities of FSUIPC. I will report back when i found a solution.
  10. The offset i thought of was 3110 i think. The one where you can just send numbers like 65731 to and it increases Com1 frequency (for example). The EFIS of the Bombardier CRJ 700 looks like this http://www.fspilotshop.com/images/FPeic_01.jpg All pages are accessible via the up and down buttons, primary returns you to the upper left page from wherever you are at the moment. So basically you have one display and 3 buttons. Up/down let you move through the different displays, primary returns you to the upper left one in the picture. Unfortunately i don't have access to FSX at home (only at university) but if i remember correctly, you are not able to push any other buttons in the EFIS. Just the three ones i mentioned.
  11. Hey Pete, we want to Control the EFIS of the Bombardier CRJ-700 in FSX! The EFIS here only contains 3 Buttons, page up, page down und primary (back to main screen). Unfortunately i wasn't able to find the commands. Neither for the Up/Down buttons nor for the Primary button. I thought they were in the offset from which you can control most of the FS functions, but i haven't found them. Do you have any clue how we can control this nice little thing? We only need the 3 buttons. Thanks in advance Snooky
  12. Thank you very much for your answer. We'll try to isolate the procedure or function causing the error. But, generally spoken, FSUIPC4 is operating the same way FSUIPC does? This means, the provided functions in your SDK for Delphi have the same name and work the same? I ask this because functions like FSUIPC_Open are called in FSHWPanel. The guy who made FSHWPanel wrote this for himself only but provided us the sourcecode. So we can't really expect real support for this program and have to find a solution on our own.
  13. Hello there, we recently decided to use FSX instead of FS2004, just because it looks much better. In FS2004, we used to assign Hardware Buttons to FS Functions, using FSUIPC and FSHWPanel ( http://www.familienvater-cockpit.de/inde/Software ). FSHWPanel can control an IO-Warrior from Codemercs. Now we bought FSUIPC4 and tried to make FSHWPanel work with it, but we always get a strange error message we don't understand. In German, the error is "Fehler bei Bereichsprüfung". In English it's maybe something like "Error while range testing" or "Error testing range". We google'd and found some people having the same problem, but with many other programs having nothing to do with FS or FSUIPC. FSHWPanel is written in Delphi. Maybe someone encountered a similar Error and is able to help us. Thank you in advance, Snooky
×
×
  • 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.