Results 11 to 15 of 15
Thread: Comms interface
-
03-05-2017, 09:26 PM #11
- Join Date
- May 2010
- Location
- Sydney
- Posts
- 36
Re: Comms interface
Hi Nico
I rolled back to SIOC 5.0B5 and A combined 1_Digit and RCP_L txt file works OK.
I had to modify the output for the DP but all good. I checked the Standby and all OK as well.
Looks like SIOC 5.1B2 is NG for your interface.
Cheers,
Alex B
-
03-06-2017, 10:07 AM #12
Re: Comms interface
-
03-06-2017, 06:11 PM #13
- Join Date
- May 2010
- Location
- Sydney
- Posts
- 36
Re: Comms interface
Hi Nico,
Have tried both 5.1B2 again on both PC's (Windows 10 and 7 x64) and still no good, I keep getting asynch issues with SIOC.
I have a nasty feeling a security update may be interfering with it in VS 2015 runtime patch 3... Will continue testing and rebuilding machines.
Cheers,
-
03-06-2017, 07:40 PM #14
- Join Date
- May 2010
- Location
- Sydney
- Posts
- 36
Re: Comms interface
I toook my Windows 7 machine back to basics and ran windows update. I then install the x64 version of VSC++ runti me for 2015.
I then installed SIOC 5.1B2.
I then ran the config for PSXseecon to use both the SIOC locally and PSX.
I then ran ccleaner on the registry (finding a pile of issues with .Net 1.3,,,,)
All now runs OK using the combined 1_Digits and 5_RCPl.txt files.
A quick question, have you been able to "fudge" the DATA display using dAtA on the display card? Otherwise I might see if I can add a bit to the script for the ACARS display RC...
Cheers,
Alex
-
03-07-2017, 01:35 AM #15
Re: Comms interface
Hi Alex,
I have not tried the data part.
Frequencies for Comma only.
Cheers
Nico
www.ljcockpit.com is up , orders are now open :)
Ljcockpit G600 , GTN Stack , GFC...