Jump to content
The simFlight Network Forums


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Scotfleiger

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling
  • Location
    Scotland, UK

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thank you the size clarification. This has solved the issue I was having.
  2. One more question. Is the a size/length limit for the .MCRO filename or the macro tags?
  3. Thanks Pete. I have checked for the correct file and macro names. For example, with the same macro in 2 different files, I changed the ipc.macro call to refer to each file. One works the other doesn't.
  4. I have been working with mouse macros with FSUIPC 5.152. It appears that only one .MCRO file can be used using LUA ipc.macro("test: button1"). Any reference to another .MCRO file is ignored (ie. ipc.macro("other: button2")). Thisappears wrong as why would be able to refer to other macro files. It also appears that .MCRO file(s) are only loaded when FSUIPC is restarted with P3D. Is there a way of forcing a .MCRO reload without restarting P3D.
  5. Hi John Those users with the VRi Combo problem who have got back to me confirm that the special build 515i provides a workable solution to their power spike issue. I recommend that the VRIDisableCMDRST switch be incorporated into the baseline. Thank you for your help.
  6. Hi John Thank you for the latest 5.15i. It works as expected with the expected VRI commands being sent (lines 265-672) and now reads all inputs from the panel. I will report back when my users have had a chance to test it. Many thanks. FSUIPC5.log
  7. Hi John The VRI Combo 2 panel normally receives a CMDRST to initialise the display. Testing using other tools (VRSIM.exe and an app I have been working on) have shown that for several users the reset and flashing of the lights is causing the disconnect of the comport. The panel does not respond to inputs or output button/knob inputs until it is connected using CMDCON. With 515h and 515i no CMDCON is logged (see FSUIPC5-515i-CMDRST-Yes.log). When everything is working, we see CMDRST (to be disabled) followed by CMDCON (up to 5 times). If the CMDCON is accepted, FSUIPC normally sends CMDFUN and CMDVER to get the panel type and firmware version (see FSUIPC5-515i-CMDRST-No.log lines 54657-54985). I agree that the panel PSU may be a cause. All the issues have been reported by new purchasers of the VRI Combo 2 panel. I still think it is related to Win10 updates but I cannot determine a common factor. Many thanks Andrew FSUIPC5-515i-CMDRST-Yes.log FSUIPC5-515i-CMDRST-No.log
  8. Thank you John for confirming the typo. The 5.15h build with the ability to prevent the CMDRST command has worked in isolating the power spike to the VRI Combo panels. However, the changes you did are stopping the subsequent CMDCON (sent up to 5 times) and the CMDFUN and CMDVER being sent. It is only the CMDRST command that needs to be switched off. Also FSUIPC may no longer be reading data from the comport when the Could you check your code and advise? UPDATE: with the switch set to yes, no inputs from the comport and panel are being received.
  9. Hi John/Pete The requested test build 5.150h is helping but the fsuipc5.ini switch keeps resetting itself negating its use. I have myself inserted the switch and set it only to find it he setting became reversed. Should it be =true or =yes?
  10. Hi Pete Thanks for the comments. I have been in contact with FDTI Support regarding the drivers for their USB-serial com port. They confirm that dated 16 Aug 2017 is the correct. Further testing by users confirms that it is the extra power draw by the panel lights that is causing a power 'spike' that is disconnecting the comport. The lights are triggered by the reset command (CMDRST sent on FSUIPC initial connection and subsequently by LINDA) or manually. Is is possible to ask for a test build of FSUIPC5 that removes the CMDRST - just has Open Port and CMDCON to connect? Andrew
  11. Hi Pete Just to update you. Turning on the additional VRI logging has revealed more evidence of the problem. The log shows FSUIPC trying to connect to the VRI Combo panel. The comport is opened and a reset command (CMDRST) sent. The users report the panel flashing as expected. FSUIPC then tries to connect using CMDCON. This is failing and the command is sent a further 4 times in an attempt to gain a connection. This should be followed by a CMDFUN command which returns the panel type. This confirmation does not appear in the log. Users also report that pressing the panel lamp button causes the USB/Serial Port connection to interrupt. The lamp also flashes when the panel is reset. Although the panels are powered by a DC transformer, it appears that the additional power draw of the lights is causing the disconnection. Once disconnected FSUIPC does not try to reestablish a connection. The Flt Sim must be restarted. This has worked fine for me and many others. I suspect that the problem may lie with a recent update to Win10 USB power management. I will investigate further. FSUIPC5.log
  12. Hi Pete Thanks for the reply. Other users with the problem have been using 5.15 so I’m not sure that is the problem. By Device ID I mean the handle returned when you first connect to a comport (I can’t remember the actual command) this is then used for all read and write to the port. I will update you if I find a solution.
  • 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.