remilton

Done!

The 2024 pre-order let me choose Drive H: for my install.

Here is what I did. No need for any more reinforcement as there is no more pressure on the sockets.

Thanks for the help Charlie!

I had been suffering for quite a while as many others have with a faulty RJ-45 port on my Honeycomb Alpha Yoke. Being that my yoke is out of warranty, and I did not want to wait weeks for Honeycomb repair service, I decided to tackle it myself. I’ll attempt to provide steps for those who my wish to perform this fix on their yoke. PLEASE DO NOT ATTEMP THIS REPAIR UNLESS YOU HAVE EXPERIENCE WORKING ON SUCH THINGS. I ASSUME NO RESPONSIBILITY FOR DAMAGE TO YOUR YOKE. I apologize for there not being more photos, but I did not have my phone With me in the shop. First things first. Unplug your yoke’s USB cable. Next, remove the rj-45 cable from the base unit. Turn yoke base over on its top and remove the 9 Philips head screws (4 on each edge). Turn yoke back over and remove the top of case The front 2 screws may not have fallen out so if needed poke them out or they may interfere when removing the front switch plate. Remove the four screws holding the LED panel and then move the LED panel out of the way. Being careful not to damage the wires or connectors, disconnect the connector going to the switch array on one side and the ignition switch on the other side. Now we get to the scary part. The switch panel can be moved away from the yoke body and slid up the yoke shaft without further disassembly. If you are uncomfortable with this step stop now. The bottom of the front panel has a groove that fits onto the bottom plate of the case. I was able to tip the top of the front panel away from the case. It is a bit of a tight fit but going slow and being careful, I was able to pull the panel up the yoke shaft and away from the case. This first photo shows the location of the female rj-45 connector circuit board. Remove the 2 screws holding the board. Then trace back the cable from the board to the main board and carefully unplug the cable connector from the main board. Now you can slide the cable toward the front of the case to provide slack for the next step. Board After slackening the cable, you can wiggle the connector and board out of the case being careful not to damage the cable and now turn the board over. The next photo shows the bottom of the ethernet board after the repair. Before the repair most of the solder joints were shallow and cracked all the way around. After I wetted the joints with lead solder, I sucked them clean the applied a heavier than normal amount of lead solder to strengthen the connections. Only the 8 pins of the rj-45 plug should need servicing. Now, just reverse the steps and reassemble your repaired yoke Here is a photo of the tip I used in my Hakko soldering iron. The solder connections were very small.

Thanks, looks really good. Now running my digital feet over to Flightsim.to!

How did that work out?

I am afraid that many software products may eventually go the way of the music industry and the ebook industry. Digital music and digital books continue to get cheaper and cheaper as the intrinsic value of digital products, which is $0, is realized. This will drive new creative ways to monetize the websites that deliver the digital material. I have recently read a blog about how market pressures may soon force Microsoft to offer windows for free. After all, Linux and Mac operating systems are essentially free.

It would be a very boring forum indeed if only glowing supportive comments were permitted.

Sorry is I offended anyone. I have no intent to "rage" on anything. I just personally don't see any technical advantage to switch to W8. I am sure W8 is a fine operating system on it's own merits, especially as a tablet operating system. I appreciate the O.P. giving us a report on it's use with FSX and I apologize if I stepped on his thread.

If W8 is a prime example of the future, I will stay with W7 until it is no longer supported.

Thanks for the tip George, unfortunately it does not fix my problem. The pc's are networked correctly and simconnect is installed correctly, The simconnect just quit working one day. I have a few more things to try, but the list is getting short. Thanks again. -Ron

IPv6 is no harder to use than IPv4 and Plan G gives the choice of IPv6 or IPv4 or WideFS. Just look under options - fs connections. Any way IPv6 has stopped working again and IPv4 still won't work, so I am getting fed up with simconnect. I have re-run simconnect.msi on the client, reinstalled Accelration and the SDK SPv1a on the server with no luck. I just wish AS2012 would use WideFS and I could be done with Simconnect.

Just to add to the mystery, (or possibly clarify it?), I have determined that Plan G which is using IPv4 is actually connecting to simconnect. What this means is that IPv6 is working and IPv4 which AS2012 uses is not. Perhaps that is a clue, but I am still at a loss.

Well, I had Simconnect working just fine. AS2012 and PlanG were both running on my Client and life was good. So, I did not run the client for about a month and when I attempted to run it again, suddenly Simconnect will no longer connect. I did some quick investigation and checking simconnect.xml on the server and simconnect.cfg on the client every thing look fine. I checked my server IP and discovered my IPv4 had changed, so I quickly edited the .xml and the .cfg and thought every thing would be fine. Wrong! I still cannot connect. Any ideas? Here are my Simconnect files: simconnect.xml p<?xml version="1.0" encoding="Windows-1252"?> <SimBase.Document Type="SimConnect" version="1,0"> <Descr>SimConnect</Descr> <Filename>SimConnect.xml</Filename> <SimConnect.Comm> <Disabled>False</Disabled> <Protocol>IPv6</Protocol> <Scope>link-local</Scope> <MaxClients>64</MaxClients> <Address>fe80::35a3:b41:6f3c:8e16</Address> <Port>4506</Port> </SimConnect.Comm> <SimConnect.Comm> <Disabled>False</Disabled> <Protocol>IPv4</Protocol> <Scope>global</Scope> <Address>192.168.1.114</Address> <MaxClients>64</MaxClients> <Port>500</Port> <MaxRecvSize>4096</MaxRecvSize> <DisableNagle>False</DisableNagle> </SimConnect.Comm> <SimConnect.Comm> <Disabled>False</Disabled> <Protocol>Auto</Protocol> <Scope>local</Scope> </SimConnect.Comm> </SimBase.Document> simconnect.cfg [simConnect] Protocol=IPv4 Address=192.168.1.114 Port=500 MaxReceiveSize=4096 DisableNagle=0