the concerned
Active Member
So would they be looking into replacing the aster 15's when they have the mid life update with camm's. Also weren't the camm supposed to replace the rapier and asraam if that is still so would it be fitted to the jsf.
It would be sensible but I don't think anybody can say with authority that this would be done right now.So would they be looking into replacing the aster 15's when they have the mid life update with camm's.
Rapier definitely will be replaced, I think the need for ASRAAM is less pressing.Also weren't the camm supposed to replace the rapier and asraam if that is still so would it be fitted to the jsf.
Defence Industry Daily had an article on this in the last couple of weeks = commonality of seeker heads and on-going development.It would be sensible but I don't think anybody can say with authority that this would be done right now.
Rapier definitely will be replaced, I think the need for ASRAAM is less pressing.
Have a look at the MBDA website press backround for details:
http://www.mbda-systems.com/mediagallery/files/camm-family_background-1402652634.pdf
Every new bit of kit or software comes with a new single-purpose laptop to run it. Eventually someone will realise the need to provide more empty desk space in cabins, offices, bridges, ops rooms etc. "fitted to receive" all these bloody laptops! (Along with appropriate means to secure them for action).Integration wise, I think the Tico's just had a spare laptop plugged in to do the mission planning etc ? Not a big job at that level.
This is probably my pet project, replacing Aster 15 with CAMM.It would be sensible but I don't think anybody can say with authority that this would be done right now.
The mid life up-date point of reference was interesting; again, commonality against the, dare I say it, fleet would be a great thing to achieve.This is probably my pet project, replacing Aster 15 with CAMM.
Currently get 16 Aster 15 and 32 Aster 30. Instead, go for 40 Aster 30 and 32 CAMM.
I get the performance of CAMM is lesser than Aster 15 at least not just having pif-paf. But you've doubled the 'local' missile load and added another 8 long range shots.
Those strike length cells would be great for the likes of SM-6 too. . . . .
/fantasywishlist.
IIRC, there's some more hardware on the back end that basically interfaces between the actual fire control panel and the launcher/missile itself. Inputs stuff like gyro motion, position, etc.I did wonder about that - so, there's no provision to swap the missiles from one to another any place other than the manufacturer then? Solves that question I guess
Integration wise, I think the Tico's just had a spare laptop plugged in to do the mission planning etc ? Not a big job at that level.
Agree, it could be the best of both worlds.This is probably my pet project, replacing Aster 15 with CAMM.
Currently get 16 Aster 15 and 32 Aster 30. Instead, go for 40 Aster 30 and 32 CAMM.
I get the performance of CAMM is lesser than Aster 15 at least not just having pif-paf. But you've doubled the 'local' missile load and added another 8 long range shots.
Yeah, definitely it should have a new name. It's a new missile, with much less commonality with Aster 30 than 30 has with 15. Aster 45 - at least....Probably even Aster 30 Block 2 (I prefer Aster 45) too looking far in the future.
Ah, yes of course - you'd need some sort of interface there. I wonder (tangentially) if there's any prospect of the USN adopting anything like the universal armaments interface that the USAF has - where you code once for interface and you're done - then it's just mating and separation tests (which are greatly simplified with a VLS silo !)IIRC, there's some more hardware on the back end that basically interfaces between the actual fire control panel and the launcher/missile itself. Inputs stuff like gyro motion, position, etc.
But I certainly would believe that there are/were configurations that are essentially using fire control laptops.
It's probably the best time to achieve the most commonality as you're already doing a significant amount of work.The mid life up-date point of reference was interesting; again, commonality against the, dare I say it, fleet would be a great thing to achieve.
Budget problems exist in the short - medium term, they need savings now whereas the tail end of the Type 26 production is heading towards the mid 2020s. Cutting the Type 26s isn't a key budget concern for the current (or even next) Parliament.However, it is interesting that the Conservatives will not commit to the NATO minimum budget requirement after the next election and yet they purport to show a budget surplus in towards 2020 - given the staggered nature of the T26 buy, why would it be unreasonable to assume a fully funded Type of 13? The Royal Navy would also have been given time address manning issues.
Riga
Well there's an interface standard for both VLS and aegis.Ah, yes of course - you'd need some sort of interface there. I wonder (tangentially) if there's any prospect of the USN adopting anything like the universal armaments interface that the USAF has - where you code once for interface and you're done - then it's just mating and separation tests (which are greatly simplified with a VLS silo !)
Last T23 is supposed to retire in the mid 2030s.I...
Budget problems exist in the short - medium term, they need savings now whereas the tail end of the Type 26 production is heading towards the mid 2020s. Cutting the Type 26s isn't a key budget concern for the current (or even next) Parliament.....
Is the HMS Queen Elizabeth really only equipped with Phalanx? Nothing like RAM or ESSM launchers?3 of those are going to HMS Queen Elizabeth for her self defence fit.
Do soft kill countermeasures these days include a naval version of chaff / flares, or are you referring to some sort of radar jamming or electronic counter-measure?EDIT: Oh, and soft kill countermeasures too.