LabFaca

Thanks! Maury

Dear Mr. Dowson, The first set of logs was generated after the full reinstallation of all software relevant to the situation.I only left the "SideWinder Precision 2" connected and only one axis (elevator) for testing purposes. When the prosim is activated, FSX no longer receives information about the position of the elevator, and when ProSim is disabled, FSX will receive the information normally. The axis related to the elevator was moved from the activation of the FSX, through the activation of the ProSim and its disengagement and shutdown of the FSX. During the period that the prosim is active, if we enable the reading of the joystick in FSX, without going through the FSUIPC4, there is no problem. I've attached a new log, without the DLL, and without the SimConnect log, the problem may be clearer. Best regards Maury Maia FSUIPC4.ini FSUIPC4.JoyScan.csv FSUIPC4.log FSUIPC4_prev.log WideServer.log

Dear Sirs, I assemble a simulation setup with Sismo panels and commands based on a BU836A board. Currently Windows 7 Professional, FSX SE, Prosim 1.56B and FSUIPC4, Version 4.974 are used as software. It had the BU836A board disabled in FSX and the analog axes calibrated by the "FSUIPC Calibration". At first it worked without problems. Last week I noticed that when the prosim is activated, the commands coming from the BU836 Card are recognized by FSUIPC4, but stop being forwarded to FSX. If you enable the recognition of the BU836 Card in FSX, the commands work. I tested it with a Microsoft Joystick instead of the BU836 Card and the result does not change. I tested the BU836 Card on another CPU with a unique Microsoft FSX in conjunction with FSUIPC4 and ProSim and the Set works through the "FSUIPC Calibration" Option and disabled the Joystick in FSX. I made an installation of the operating system, FSX, FSUIPC and ProSim, with the minimum resources needed to test the commands (in conjunction with the Microsoft Joystick) and the result remains the same. The new installation decided to carry out, as in the former had performed several experiments with other applications and had even installed the Elise-NG Fly Software and had doubts if there was something interfering in the operation of the simulation setup. Attached are the logs generated by the software that I installed after the last installation. I've also activated some more logging options. I will post this question also in the ProSim support forum, but I would like to hear from you about what might have happened and if there is something to be corrected, as I may have changed some configuration. Appreciate your attention. Best Regards Maury Maia FSUIPC4 Install.log FSUIPC4.DLL FSUIPC4.ini FSUIPC4.JoyScan.csv FSUIPC4.log FSUIPC4_prev.log SimConnect0.Log WideServer.log WideServer0.log (PS)config.xml (PS)log.txt (PS)rlm1202.dll (FSXSE)dll.xml

Mr. Dowson, I apologize for the delay in returning your last message. With your information, I performed some tests on the system and I noticed that shooting Trim Wheel keeps on happening. When I assume the maintenance of simulator , the noise generated by potentiometers of the controls (the originals installed by PFC) they were so significant, that there was no need to move commands for the system to recognize the existence of the interfaces. For this reason, the trim respond immediately, without the need for external assistance. The pots have been replaced by new and starting from this moment, to start the Power on, it is necessary to act on the commands and keys so as to prepare the system for it to work right away in training sessions. The problem is that when you activate the A / P, and act manually on the trim wheel so that it is recognized, it begins to move in and only to its backstop. It does not assume the position given by MSFS or Project Magenta (do I not know who determines this situation). Mr. Dowson, please, which the suggested settings for the "PFC.dll" and "FSUIPC" for use with the "PFC 737 '? Therefore, if the problem persists I suppose that is a defect on the hardware. I'm trying to renew contact with the PFC, I suppose they should not have received the first e-mail request for information. Thank you for your attention.

Dear Mr. Dowson, The equipment is a cabin A.A.T. A.C.T. 737 PFC. Below two pictures of the simulator. In the options screen interface "PFC.dll", I indicated the existence of Motor-driven for the stick shaker, and this is working correctly, and in relation to trim, he stopped to move the position at the end of the course, but does not function acts in conjunction with the A / P. Using the "rocker switches", the operation of Stab Trim Wheels is normal. Accept my apologies for i not being able to describe the situation in a simpler way. Kind regards, Maury Maia Pontifical Catholic University of Rio Grande Do Sul Faculty of Aeronautical Sciences Laboratory

Yes, the term is used in relation to the autopilot. I apologize for the mistake. Thought in Portuguese (Piloto Automático) and I wrote literally "P / A". We use FS9 for the sake of legal contract between the University and Microsoft. There is an agreement of license usage and in this specific case, the software version also is meeting our needs. The license in question accompanied the equipment at the time of its acquisition, in 2006, and this unit has register of almost 14,000 hours of total operation. The hardware utilizes a serial interface. For proper identification, what are the necessary information? I have been informed that at the beginning, the trim system worked correctly. After noting that: How can compensate the attitude, in manual mode, operating in the the rockers switchs; the interrupters of end course are working; to the activate the "A / P", triggers the "Trim wheels"; and after shutting off the "A / P" and acting in the system physical, the new trim position is recognized by FS9; I'm checking if no is only one configuration error in the software interface to the system. I am awaiting a return of Technical Support PFC, the more I believe it is more a question of configuration. I don't rule out a malfunction of hardware, the equipment operates 12 hours per day at certain periods of the year, but first I have to exclude a disastrous intervention in the software. Thank you for your guidance and assistance, Kind regards, Maury Maia Pontifical Catholic University of Rio Grande Do Sul Faculty of Aeronautical Sciences Laboratory

Dear Mr. Dowson, When I took over the maintenance of the faculty, one of the reports of failures I received was that the "stick shaker" was not operational, activated randomly and not turning off, only after restarting the system, and that the "Stab Trim Wheels" turned to the limits when it engages the " P / A (MCP) ". After decoupling the "P / A", to the lowest trim command, "rocker switches" or manually, the flight attitude of the aircraft assumes indicated in the "stab trim indicator". I checked that the installation of the various elements of the system was changed in an uncontrolled manner, not original aircraft, scenarios of unknown origin, versions of programs "Project Magenta" mixed and various configuration options MS flight Simulator aircraft and not installed proper operation proposal . I checked that the electrical connections of the "stick shaker" and "Stab Trim" was disconnected. Redid the connections. I installed from the OS to the original aircraft, "737 NG PFC". Currently the configuration is installed: Windows XP Professional SP3 MS Flight Simulator 2004 with "fs91upd" MCP - Project Magenta - Build # 480 FSUIPC 3.999z WideFS 6989 PFC.dll 2:41 After configuring the options and FSUIPC interface / PFC.dll as directed in the manuals, the "stick shaker" is functioning normally. The "Stab Trim" no longer performs the action above reported. Using the "rocker switches", the operation is normal. But he is inoperative during the action of the "P / A", and contacted the trim of the aircraft FSFS2004 works normally. When disconnecting the P / A system adopts the attitude displayed in the "stab trim indicator". I did not notice changes when alternating the option “DisconnTrimForAP”. Using the "rocker switches", the operation is normal. I appreciate any guidance on how I can find out what did not notice what is missing or is set to the "Stab Trim" becomes operational. Thank you for your attention and good will. Kind regards, Maury Maia Pontifical Catholic University of Rio Grande Do Sul Faculty of Aeronautical Sciences Laboratory

Mr. Pete, Sorry for the delay in responding. I apologize if I requested information that is restricted due to the reasons given, but fortunately the response are available in official documentation and pages of traditional suppliers to the area of simulation. According to this documentation, "MCP / FCU Codes / MCP / FCU Interface (defined by ELAN Informatique)", was missing after being sent the address of the character offset (chr) ascii null (0x0). Through a terminal program, sending commands in hex ​​format, got success. But the implementation of serial communication is recent in ProSim and this option only accepts entries in the format "chr", thus making it impossible, in my knowledge, the inclusion of "ASCII" chr null (0x0) after the offset. At this time the option of using PFC.dll in conjunction with the "FSUIPC" can not be implemented because not located the possibility of changing the settings of the serial port implemented by ProSim (115200 N, 8.0) whereas protocol sets in (19200, N, 8,1). I tried to contact the staff of the Forum ProSim, but he is down for maintenance. As soon as possible, I will present the situation and the suggestion to allow adjustment with the serial com and the option to enter the Gateway via option "Generic Serial" also in Hexa. Regarding options to connect via "FSUIPC" posted a picture below that shows the "seven options". I believe that the former is, in my case the correct one. Thank you for your attention and assistance when you get more results, go back and reactive the topic. Kind regards, Maury Maia Pontifical Catholic University of Rio Grande Do Sul Faculty of Aeronautical Sciences Laboratory

Mr. Pete, I'm studying the possibility to install in a PFC 737NG Jet Trainer (Jet Line) old, who uses a serial interface, the software Prosim 737. I found that there are two possibilities: - Use the serial interface and the option of Prosim driver "Generic COM port". Studying the PFC test, I noticed that the program conveys a word "ascii", and for example, lighting a flag in the "mcp" the PFC. I confirmed the fact monitoring the serial CPU. But if I send the same word via serial, can not the same result. idem via Prosim. Then there is the other option: - Use the serial interface together with the driver Prosim "FSUIPC support". In this situation, could use PFC.DLL to receive data via serial and designate the offsets in FSUIPC ProSim737 System? Because I still did not realize this research? There are seven options settings for "FSUIPC support", which is the best if you can say? If possible, how should I configure the options and Prosim "FSUIPC". Returning the first option, if you can provide this information, as is the word that is transmitted via serial? Follows a pattern established or is simply the word and maybe something kind word + "new line"? The address information is available in the scripts "TCL" test program of PFC. As I do not know the language "TCL" I could not see how the information is transmitted to the MCP, for example. Via FSUIPC there is a possibility of communicating directly or via serial communication would be the best option? In the latter case what can I be doing wrong, because if the PFC sends a TEST information because the same information conveyed otherwise (specific software to read and write in with) does not have the same result? Thank for suggestions or information that might enlighten me and guide. Thank you for your attention. Kind regards, Maury Maia Pontifical Catholic University of Rio Grande Do Sul Faculty of Aeronautical Sciences Laboratory