SkyView 4.0 Now Available!

[dynonsupport]

If you want it just lighter in color, just nudge each of the RRGGBB components up 10 or 20 uniformly.

So does that mean:
color0=004AB4FF  would be 014AB4FF
color1=004AB47F would be 014AB47F
color2=0058D6FF would be 0068D6FF

No, that will make the class B airspace line AND the text lighter. I believe you only want the text lighter. In that case, you only want to change color2.

Also, you want it 1068E6FF. Just changing the 58 to 68 will only increase the green in the color, which will make it a different color, not a different brightness. Making something lighter without fundamentally changing the color requires you to move all the colors up together.

The airplane color is not adjustable.

 

[jc2da]

I have a mixed bag on the map updates. I only have 30 mins so far, but I have noticed one issue. In the SFO Bravo airspace, i notice that the airspace altitudes are only shown once on the entire ring. Thus, you could be on the western side of the ring but have to scroll all the way to the eastern side of the ring to see what the altitudes are. This is true even if i zoom way in, it seemed.

Following a ring 180 deg is tricky because of underlying Class C OAK and Class D's which overlap the ring in various places.

Thus, the legibility of the screen is overall better, but the pilot awareness of airspace is less for me at least in this terminal area.

Jae

 

[preid]

If you want it just lighter in color, just nudge each of the RRGGBB components up 10 or 20 uniformly.

So does that mean:
color0=004AB4FF  would be 014AB4FF
color1=004AB47F would be 014AB47F
color2=0058D6FF would be 0068D6FF

No, that will make the class B airspace line AND the text lighter. I believe you only want the text lighter. In that case, you only want to change color2.

Also, you want it 1068E6FF. Just changing the 58 to 68 will only increase the green in the color, which will make it a different color, not a different brightness. Making something lighter without fundamentally changing the color requires you to move all the colors up together.

The airplane color is not adjustable.

Glad I asked!
Thank you!

 

[Anton]

is it possible to connect two of the EMS module to one display D1000(ver 4.0)?

 

[tobb]

Just installed the european package today, and i noticed that the airspace graphics doesn't look as the ones in the skyview user manual. I have the latest pocketfms aerodata installed.

It seems that pocketfms data is not fully supported with the 4.0 software.
Here is at screenshot of some Restricted/danger and CTR

 

[dynonsupport]

is it possible to connect two of the EMS module to one display D1000(ver 4.0)?

No, it is not.

 

[dynonsupport]

tobb: You're experiencing what one would see if 3.3 data is loaded on 4.0. You get airspace, but not all of the graphical things are up-to-date. PocketFMS is supposed to be offering 4.0 and 3.0 data for the next few cycles. I'll see if that's actually happening.

 

[Anton]

   Anton wrote Yesterday at 10:08am:
is it possible to connect two of the EMS module to one display D1000(ver 4.0)?

No, it is not.




Thanks for the reply.

Will be this option in the next updates?

 

[aerofurb]

I am now getting a 'SERVO' warning whenever our autopilot master switch is off.

Is there a way to disable that 'SERVO' warning?

Rest of v4.0 is spendid!

 

[dynonsupport]

There isn't currently. The servos are expected to have power on them whenever SkyView is powered. Know that they don't draw any current unless they're actually engaged.

 

[preid]

There isn't currently. The servos are expected to have power on them whenever SkyView is powered. Know that they don't draw any current unless they're actually engaged.

I always received an error in the form of a RED "err" on the top of the screens, for the servos when not powered on (in my case engine start with the back-up battery keeping the display live, but everything else powered off) I would want to know that the servos are not powered as I always have them powered when the engine is running. I see no reason to power them off. I would want to know however, as part of my pre-takeoff check that they are indeed powered and ready.
I support the error and see that as a great safety improvement.

 

[dynonsupport]

tobb: You're experiencing what one would see if 3.3 data is loaded on 4.0. You get airspace, but not all of the graphical things are up-to-date. PocketFMS is supposed to be offering 4.0 and 3.0 data for the next few cycles. I'll see if that's actually happening.

The 4.0 PocketFMS data wasn't live until today. You should be able to download either 3.3 and 4.0 data if you log in now to your account there now.

 

[calm]

hi,
We updated our two D1000 yesterday with the europe version 4.0 bundle. Everything went great during the installation process and new map features are available. Unfortunately, the fuel pressure widget has now a red cross through it and a "cfg?" message displayed underneath.
It's seems the kavlico fluid pressure sensor is wonky (attached pictures), maybe he needs a recalibration or something ?
Any input or help to fix it would be much appreciated !

Thanks.

 

[dabear]

You'll need to re-define the function of that sensor. You'll notice in the top picture that the function is blank, but you have the sensor and name defined.

When you go to define the function, you'll have to re set the sensor type (center column/sensor) and the Name (right column/Name). THen it should come up again.

I just saw this happen on a friends SV when he upgraded to 4.0

 

[calm]

Thanks dabear. Sounds good, I'll try that tomorrow.

 

[preid]

If you want it just lighter in color, just nudge each of the RRGGBB components up 10 or 20 uniformly.

So does that mean:
color0=004AB4FF  would be 014AB4FF
color1=004AB47F would be 014AB47F
color2=0058D6FF would be 0068D6FF

No, that will make the class B airspace line AND the text lighter. I believe you only want the text lighter. In that case, you only want to change color2.

Also, you want it 1068E6FF. Just changing the 58 to 68 will only increase the green in the color, which will make it a different color, not a different brightness. Making something lighter without fundamentally changing the color requires you to move all the colors up together.

Can someone who has modified the color attach a picture of results. I have not installed 4.0 yet so I have not been able to test but I would be interested in knowing what it would look like if I made the change. If I see that 10 is not enough than I can skip that and go right to 20, or settle that it is fine as is. I am smack in the middle of LAX B airspace so I have a whole lot of blue numbers to deal with.
thx

 

[aerofurb]

There isn't currently. The servos are expected to have power on them whenever SkyView is powered. Know that they don't draw any current unless they're actually engaged.

No problems - we'll just fly with the AP on then in future.

Thanks also for the heads up on the v4.0 Pocket FMS - best I go and download that.

 

[dynonsupport]

hi,
We updated our two D1000 yesterday with the europe version 4.0 bundle. Everything went great during the installation process and new map features are available. Unfortunately, the fuel pressure widget has now a red cross through it and a "cfg?" message displayed underneath.
It's seems the kavlico fluid pressure sensor is wonky (attached pictures), maybe he needs a recalibration or something ?
Any input or help to fix it would be much appreciated !

Thanks.

What DaBear said. The reason has to do with a slight name change in the sensor naming. In other words, the sensors definition update "broke" it because the name of the sensor type changed slightly as far as the system knows.

 

[calm]

hi,
We updated our two D1000 yesterday with the europe version 4.0 bundle. Everything went great during the installation process and new map features are available. Unfortunately, the fuel pressure widget has now a red cross through it and a "cfg?" message displayed underneath.
It's seems the kavlico fluid pressure sensor is wonky (attached pictures), maybe he needs a recalibration or something ?
Any input or help to fix it would be much appreciated !

Thanks.

What DaBear said. The reason has to do with a slight name change in the sensor naming. In other words, the sensors definition update "broke" it because the name of the sensor type changed slightly as far as the system knows.

Issue solved. Thank you !

 

[caffevictoria]

:-[ :-[
Hello, I have updated all goes well today, but this is written .... Help me