1553 is transformer coupled serial. The idea is, if your wing or something gets blown off, you don’t loose comms with the rest of your load out, or whatever else you have connected.
I designed a number of transformers for use with 1553 bus systems in the '80s. The data was Manchester encoded to give net zero current which stopped the transformers saturating. Raychem produced some natty cable assemblies using their heat-shrink technology and our transformers. Never found out where they ended up; it was all hush-hush!
The problem with 1553 is how the protocol works on the data layer. Its extremely limiting, having a maximum of 64 bytes per message (32 words - why they use 16-bits as their word length is beyond me). It's a master-slave architecture (bus controller / remote terminal), but the big issue I have is that the slave has no way to asynchronously send messages. All transactions are driven by the host, no exceptions. This makes it very difficult to create an efficient protocol if you have intermittent data events. Another big problem for me is the message scheduling aspect. Messages are (usually, there are exceptions) sent in a rigid on a schedule. This means the message is sent whether you have anything to say or not. This makes it more difficult to have an event driven protocol, since telling a device to do an action gets repeated every time the message is sent (and the message is usually sent many times per second). It is of course possible to work around this, but it's annoying and the protocol just wasn't built for it. 1553 is great for status driven systems, such a sensor to check airspeed or an actuator to open the landing gear (i either want it to stay open or stay closed - if it's already open and I ask to open it again, no problem). It's not great for things that revert back to their original state after the command completes, like firing a weapon (once the shot is taken, you are ready to take another. So if I ask to make a shot and it's already been fired, it'll shoot again unless I have extra logic to prevent that). Anyway, there is a reason no new designs use 1553
i am so glad the algorithm brought you to my attention, why dosen't it do more? This kind of thing is fascinating to anyone who grew up with LSI and VLSI chips powering the world around them and your presentation is mesmerizing. I once got a promo keychain from Intel that had a failed Pentium chip encased in plastic and loved the shimmering detail, wishing I could see so much closer. Now...I can!
The algorithm serves you whatever keeps you on the app longest while driving the most engagement, comments, likes, whatever else. You don't see much new content because new content does not keep you engaged with the app. It's tricky, but you can "tune" the algorithm if you are very careful with what you do. Sucks we have to do this, but it is definitely better than waiting until 2am to watch public access.
I'm going to assume the JWST uses integrated components that have been around for decades - which would mean less bugs and flaws which have been resolved
Don't underestimate industry legacy and sticking to old protocols even implemented with new ICs and languages, in a place as conservative as space. 1553 is sometimes even used in some recent satellites, and if you add to that the Webb was designed in the 2000s, it's not very strange to see used a very robust bus -then- less than 30 years old !
impressive video .What camera do you use?When you change magnification for example from 200x to 500x it seems to me like you are zooming and not changing microscope objective.How you achieve this?
Thanks! All of my videos are recoded with my cellphone, in this case a Samsung Galaxy S21 Ultra looking through my microscopes 10x eyepieces. I use a zoom transition effect on the InShot video editor on my phone when I'm editing the videos to move between the 5x, 10x, 20x, and 50x objective views.
Es una hermosa pieza tecnológica hecha totalmente de oro para una excelente conductividad térmica y electrica. Muy costoso en su tiempo y a la fecha por la cantidad de oro que se puede obtener....
something with that much gold on it, is likely still useable today. easy repair and test. always test before destroying this stuff, its not made any more and is highly valuable. down voted
1553 transceivers are still produced (ask me how I feel about that....), although DDCI has gone out of business. Alta and Holt are two vendors still making 1553 chips. This chip has no value. Any system using this chip needs to be highly reliable, and thus the circuits using these chips have already been redesigned due to obsolescence of this (and basically every other part) having gone out of production a decade ago. This is what my company does.
1553 is transformer coupled serial. The idea is, if your wing or something gets blown off, you don’t loose comms with the rest of your load out, or whatever else you have connected.
I used to work on these, they're great but nowadays you can get the
I designed a number of transformers for use with 1553 bus systems in the '80s. The data was Manchester encoded to give net zero current which stopped the transformers saturating. Raychem produced some natty cable assemblies using their heat-shrink technology and our transformers. Never found out where they ended up; it was all hush-hush!
The problem with 1553 is how the protocol works on the data layer. Its extremely limiting, having a maximum of 64 bytes per message (32 words - why they use 16-bits as their word length is beyond me).
It's a master-slave architecture (bus controller / remote terminal), but the big issue I have is that the slave has no way to asynchronously send messages. All transactions are driven by the host, no exceptions. This makes it very difficult to create an efficient protocol if you have intermittent data events.
Another big problem for me is the message scheduling aspect. Messages are (usually, there are exceptions) sent in a rigid on a schedule. This means the message is sent whether you have anything to say or not. This makes it more difficult to have an event driven protocol, since telling a device to do an action gets repeated every time the message is sent (and the message is usually sent many times per second). It is of course possible to work around this, but it's annoying and the protocol just wasn't built for it.
1553 is great for status driven systems, such a sensor to check airspeed or an actuator to open the landing gear (i either want it to stay open or stay closed - if it's already open and I ask to open it again, no problem). It's not great for things that revert back to their original state after the command completes, like firing a weapon (once the shot is taken, you are ready to take another. So if I ask to make a shot and it's already been fired, it'll shoot again unless I have extra logic to prevent that).
Anyway, there is a reason no new designs use 1553
@@alexdyke194 Much easier to do error detection / detect damage/ missing nodes.
@@alexdyke194 what is used now with similar specifications?
i am so glad the algorithm brought you to my attention, why dosen't it do more? This kind of thing is fascinating to anyone who grew up with LSI and VLSI chips powering the world around them and your presentation is mesmerizing. I once got a promo keychain from Intel that had a failed Pentium chip encased in plastic and loved the shimmering detail, wishing I could see so much closer. Now...I can!
There's a whole other world in these silicon chips. I'm happy to be able to share them here :)
@@EvilmonkeyzDesignz I'd guess you're also a Louis Rossman fan?
The algorithm serves you whatever keeps you on the app longest while driving the most engagement, comments, likes, whatever else.
You don't see much new content because new content does not keep you engaged with the app.
It's tricky, but you can "tune" the algorithm if you are very careful with what you do.
Sucks we have to do this, but it is definitely better than waiting until 2am to watch public access.
That part is beautiful.
I would love to have a series of just the chill music with the magnified video. 😊
Dig this! Thanks for your work & glad the phone makes a better editor!
Can you please make more videos de-capping ic chips? Preferably large and thin chips because I always have trouble with those.
I'm going to assume the JWST uses integrated components that have been around for decades - which would mean less bugs and flaws which have been resolved
Don't underestimate industry legacy and sticking to old protocols even implemented with new ICs and languages, in a place as conservative as space. 1553 is sometimes even used in some recent satellites, and if you add to that the Webb was designed in the 2000s, it's not very strange to see used a very robust bus -then- less than 30 years old !
impressive video .What camera do you use?When you change magnification for example from 200x to 500x it seems to me like you are zooming and not changing microscope objective.How you achieve this?
Thanks! All of my videos are recoded with my cellphone, in this case a Samsung Galaxy S21 Ultra looking through my microscopes 10x eyepieces. I use a zoom transition effect on the InShot video editor on my phone when I'm editing the videos to move between the 5x, 10x, 20x, and 50x objective views.
Es una hermosa pieza tecnológica hecha totalmente de oro para una excelente conductividad térmica y electrica. Muy costoso en su tiempo y a la fecha por la cantidad de oro que se puede obtener....
What is the background music?
@ the 4m 42s mark there is a black point in the middle... Is it burned? Maybe by a short or similar?
Probably a case of electrostatic discharge from mishandling
What microscope do you use?
The base model is the ME580 from AmScope. It comes in different packages with various add-ons 😁
Show us inside an i7!
Sounds like Phantasy Star Online music
That watermark is very very annoying…
something with that much gold on it, is likely still useable today.
easy repair and test.
always test before destroying this stuff, its not made any more and is highly valuable.
down voted
1553 transceivers are still produced (ask me how I feel about that....), although DDCI has gone out of business. Alta and Holt are two vendors still making 1553 chips.
This chip has no value. Any system using this chip needs to be highly reliable, and thus the circuits using these chips have already been redesigned due to obsolescence of this (and basically every other part) having gone out of production a decade ago. This is what my company does.