Recent content by jsalak

Quick update after 3 additional flights with a secondary network error cautions. Looking at the alert data log for each flight the secondary network caution showed at 14 minutes after D1000 startup on 2 flights and 12 minutes on the third. That pattern is typically associated with a heat failure...

Just visually. It would be nice if there was a loopback test from the primary network to the secondary network on the DB-9 connector to verify the problem is not internal to the D1000.

Went to fly today and got a CAUTION message for a secondary network fault. Checking the network status page shows the D1000 display has the fault listed. Troubleshooting steps: 1. swapped D1000 DB-9 cable to other D1000 network port. Error still shows. 2. swapped D1000 DB-9 cable to two other...

You want to download RV-12 service letter 14-05-22 which tells you how to install/retrofit the canopy open warning switch. You can order the retrofit kit from Van's store, part number ES-00300 for $87.50. https://www.vansaircraft.com/service-information-and-revisions/n-14-05-22/

I suspect it is a software issue and most likely related to the battery charging part of the code. Battery voltage is reading 12.08, a bit low but not bad enough to be triggering low voltage alarms.

I don't think it is a battery problem. If the voltage was in fact low and triggered the alarm, it would remain displayed. I have had a low battery state in the past and the alarm remains on the message list until the charge state is high enough to hide the message. If you look at the time index...

Last couple of flights I have been getting a lot of audio alerts 'MESSAGE' with no accompanying text in the message list on the display. Looking at the exported alert file I find a bunch of BACKUP BATT LOW CHARGE alerts that set and immediately clear. These are a bit of a nuisance as there is...

I was plagued by System 3, System 5, and System 20 reboots for 5 months last year. They started right after I updated to 16.5.2, typical event was pulling back power on decent and the system would reboot. The reboots would usually continue to landing once they started. Sent the SV-D1000 back to...

A follow-up on various AP pitch settings, I set all of the non-glideslope pitch values to something close to the minimums and flew in some light chop to see the effects. Still doing a bit of altitude hunting with over and under shoots, however the VSI did not show any numbers higher than 300-400...

I went out today in smooth air to try some more adjustments, the Lost Motion Compensation was interesting setting it to 2 resulted in a short period pitch oscillation, 1 reduced it some, and zero stopped it. I already reduced the G-Error-Limit and G-Error-Gain with not much of an observable...

Went out and flew for a couple of hours today to check out the 16.4 SW. No improvement in the pitch control with a light chop, I was seeing 700-800 FPM in the VSI and speed changes of 10-15 knots with the pitch up and down hunting around the altitude bug. I tried some of the adjustments...

Did the 16.4.0 upgrade today and will test fly it tomorrow. Looking forward to not hearing "BANK ANGLE" anymore. Hopefully I can get a better AP tune with the new guide, the altitude hunting in any kind turbulence is getting old (hysteresis in pretty bad). Not sure why the AP allows such large...

Updated to 16.4.0 today and could not load a FF flight plan to the IFD over the SykView network. Interestingly, the IDF100 is now working on both iPads. The IDF is showing up on FF Devices and lists receiving flight plans in the capability box (same as SkyView). The other odd item is nether iPad...

Spent about an hour on trying to get two iPADs with FF and IFD100 apps to work with my SV-D1000 and IFD540. Avidyne 10.3 made some changes to the network setup and operation, so the first error I made was renaming the default IFD network to the SkyView network name. The default IFD network is an...