Meadville Space Center
Welcome, Guest. Please login or register.
October 25, 2020, 07:15:10 AM

Login with username, password and session length
Search:     Advanced search
Welcome to the new Meadville Space Center forums!
25068 Posts in 2094 Topics by 2266 Members
Latest Member: twa517
* Home Help Search Login Register
+  Meadville Space Center
|-+  Project Apollo - NASSP
| |-+  Project Apollo - NASSP Development
| | |-+  Programming (Moderators: movieman, dseagrav, Swatch, lassombra)
| | | |-+  LM status...
« previous next »
Pages: 1 ... 26 27 [28] 29 30 ... 67 Print
Author Topic: LM status...  (Read 160622 times)
NoName
Project Team Member
Hero Member
****
Posts: 795


View Profile
« Reply #405 on: March 20, 2012, 02:20:48 PM »

Ok, I stop working on it then.

Do you need the bitmap urgently? I could put it on top of my list and commit it before I commit all the other new LM bitmaps.
Well no, as I was about ready to commit myself the range tape meter. I had done the tapemeter (in feet only , I did not implement the transittion to NM) and the digits to print out the range in ,000 increments.  Can you confirm that you worked on a fully moving tapemeter that responds to RR radar values? or just the bitmaps? I've got the whole thing working but did not commit. I you just worked on the bitmap, then I'll keep the display logic code.

I'm only working on the bitmaps. I'm a very bad coder Sorry So I'm glad there is you and all the other coders here Thumbs Up

The bitmap currently contains, or more specifically will contain everything: the black tape from 0 to 120k feet and up to 400 nm on the left, as well as the white +/- 700 fps tape on the right. It's going to be a very long/high bitmap. Just tell me in case it should look different.
Logged
vrouleau
Project Team Member
Full Member
****
Posts: 153


View Profile Email
« Reply #406 on: March 20, 2012, 02:44:02 PM »

Ca n you send me your bitmaps. If you did manage do to the large range, I'll see if I can you it instead of printing every digits individually.
Logged
NoName
Project Team Member
Hero Member
****
Posts: 795


View Profile
« Reply #407 on: March 20, 2012, 02:50:24 PM »

Ca n you send me your bitmaps. If you did manage do to the large range, I'll see if I can you it instead of printing every digits individually.


Of course. But I still have to add the nautical miles. Shouldn't take too long. I'll commit it soon...
Logged
NoName
Project Team Member
Hero Member
****
Posts: 795


View Profile
« Reply #408 on: March 20, 2012, 06:39:57 PM »

Does anybody know the limit of the fps scale? And isn't it two different tapes? Currently both scales are in one bitmap.
« Last Edit: March 20, 2012, 07:02:16 PM by Moonwalker » Logged
NoName
Project Team Member
Hero Member
****
Posts: 795


View Profile
« Reply #409 on: March 20, 2012, 07:01:53 PM »

So now I am at the 120k feet mark. The bitmap is 84x8040 pixel at the moment. The next number would be 121k but due to the transition to NM I guess the next number is 20 NM right? If the look of the scale does not change, now each small mark means one NM more, i.e. 10 NM more each tenth mark. So the bitmap doesn't become too big I think. In terms of mega byte it's just about 2 currently, uncompressed (24 bit). Anyway, it's going to become the longest bitmap for a gauge I have ever seen so far ROTFL
Logged
NoName
Project Team Member
Hero Member
****
Posts: 795


View Profile
« Reply #410 on: March 20, 2012, 07:34:35 PM »

So there we are. The ALT scale measures 44x6370 pixel = from 0 to 120k feet and then from 20 NM up to 400 NM.

The ALT RATE scale measures 44x5610 pixel = from -700 to +700 FPS.

Just let me know if the ALT RATE scale (-700 to +700 FPS) is correct, and if the two scales should be in one bitmap or two separate different bitmaps.
Logged
vrouleau
Project Team Member
Full Member
****
Posts: 153


View Profile Email
« Reply #411 on: March 20, 2012, 07:59:13 PM »

I'm test then out tomorrow in the code. I'll let you know it orbiter handles it. If not, I' ll revert to my current method.
for the rate, it is better to keep it one bitmap

Update: Did you commit? I did an update and did not get anything.
« Last Edit: March 21, 2012, 05:59:32 AM by vrouleau » Logged
NoName
Project Team Member
Hero Member
****
Posts: 795


View Profile
« Reply #412 on: March 21, 2012, 12:07:54 PM »

Sorry for the delay.

I'm having trouble checking out the latest CVS files. CVS aborts every few minutes. I'll let you know as soon as it works and when I committed the new bitmap.
Logged
NoName
Project Team Member
Hero Member
****
Posts: 795


View Profile
« Reply #413 on: March 21, 2012, 02:56:02 PM »

I still can't checkout, i.e. get all the latest project files. CVS crashes here and there with different messages. Even when I delete the folder and try it again with a clean checkout.
Logged
NoName
Project Team Member
Hero Member
****
Posts: 795


View Profile
« Reply #414 on: March 21, 2012, 04:39:11 PM »

Finally it worked. But now one of my RAMs obviously died. But that's a different matter...

So, the new bitmap is available now ("lm_range_rate_indicator_scales").

Remember to put the "lem_range_rate_indicator" bitmap on top, if you haven't done so already.

Hope it will work.
Logged
vrouleau
Project Team Member
Full Member
****
Posts: 153


View Profile Email
« Reply #415 on: March 23, 2012, 09:34:01 PM »

I did a commit on the radar tape logic. The range tape and rate tape now moves based on RR data only. The "ALT/RNG MON" switch must be in UP position. I added persistency on tape position to add smooth scrolling on large changes, that I will add later later.

I believe there is an error in the range bitmap. 120000 feet = 20NM, so the scale should go to 30 NM from 120,000 , not 20NM. I can fix that.
Logged
NoName
Project Team Member
Hero Member
****
Posts: 795


View Profile
« Reply #416 on: March 23, 2012, 11:24:29 PM »

I did a commit on the radar tape logic. The range tape and rate tape now moves based on RR data only. The "ALT/RNG MON" switch must be in UP position. I added persistency on tape position to add smooth scrolling on large changes, that I will add later later.

Great news. I will check it out this weekend.

I believe there is an error in the range bitmap. 120000 feet = 20NM, so the scale should go to 30 NM from 120,000 , not 20NM. I can fix that.

Ah, yes. If it starts at 120,000 feet than the first line means 21 NM, the second one 22 NM and so on, which means that the first mark should be 30 NM.

I can fix it also if you want. I have to change it anyway since I keep all the original files up to date in different folders. Uncompressed, compressed, and all the templates. If not compressed, NASSP would have 400mb of panel graphics by the way.
Logged
vrouleau
Project Team Member
Full Member
****
Posts: 153


View Profile Email
« Reply #417 on: March 24, 2012, 05:28:37 AM »

Ok fix it. Once you commit, it will change an offset in the code. I will correct it them
Logged
dseagrav
Moderator
Hero Member
****
Posts: 1118


View Profile
« Reply #418 on: March 24, 2012, 12:57:45 PM »

When you guys are done fixing that let me know so I can finish debugging the positioner.
Logged
retro
Full Member
***
Posts: 76


View Profile
« Reply #419 on: March 24, 2012, 09:44:03 PM »

Found out the max rates on the range alt tape fps is + -700 fps.
that's vertical vel max Display.confirmed! lol
« Last Edit: March 24, 2012, 10:37:10 PM by retro » Logged
Pages: 1 ... 26 27 [28] 29 30 ... 67 Print 
« previous next »
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.10 | SMF © 2006-2009, Simple Machines LLC Valid XHTML 1.0! Valid CSS!