It was pretty dry, technical and specific. Plus it had the complication of some speakers being difficult to understand. But it is clear that Elaphe is very serious and diligent about making their motors and control systems safe, well tested, and fault tolerant. My only questions are concerning Elaphe's interaction with Aptera, and the integration and implementation of control and safety systems in the upcoming Aptera. We know that there will be ABS braking, traction control, as well as tie-ins for future Open Pilot ADAS vehicle control. And I am also curious about torque vectoring, and electronic vehicle control, because Elaphe has done extensive engineering and testing in those areas, but Aptera's 3 wheel design would introduce new variables in vehicle dynamics and control. Thanks Steve for posting the Elaphe video.
I suspect that FWD and AWD will have considerably different algorithms for almost all driving functions. In some ways FWD might seem more simple but you lose the precision control of the rear wheel with just a disc brake. In AWD you have very precise control of the rear wheel and can also measure the torque on that wheel. It is great to see that Elaphe is following the risk / test process described in the video. The Aptera will really be a control by wire vehicle and the computations must all work together or there could be serious injury. Safety and backup control systems are incredibly important. (Say you are driving at highway speeds and for some reason the right motor fails. Unless the motor goes into a braking mode, the impact initially would be minor but the VCU needs to sense that the right motor is no longer able to provide braking power and will have to apply more pressure to the right disc brake than to the left. This definitely should display an alert on the console but will the vehicle be able to be operated with one motor inactive or do you need to have it put on a flatbed and repaired before being able to drive?) Very glad that Elaphe and Aptera are considering all these conditions and so many more.)
Thanks for posting this on the forum.This content will resonate with the engineers, system engineers, program/project managers, testers, and logistics people on the forum as it is what they do daily on R&D Projects. I think it has GREAT value as it shows what is behind the curtain in a development efforts. Hopefully, this will provide a better understanding of the effort it takes to develop a product. This is only one component of a whole system. Also, hopefully, it will inform those forum members that say, “Oh it is only a simple/easy change” There are no simple changes. (Little effort, low cost, easy) And this didn’t even address the logistics changes that need to be made with appropriate lead times to support a feature change or development of a new feature.
This webinar reminds me very much to the Functional Safety and Cyber Security trainings I got in my company. Overall responsible is the manufactorer (OEM), but this responsibility is forwarded by contract to each supplier. It is absolutely requiered in Europe, new cars can't go into market without fulfilling these ISOs. I think, it is mandatory from Juli 2024.
Not exactly riveting information for a few of us. For those of you that have trouble with these accents there is the "CC" box at the bottom of the active screen for "Closed Caption" which often helps me. It is refreshing to hear about "Requirements Definitions" of a project before active physical endeavors are begun.
Some of you who had problems understanding That's because the world of engineering does not discriminate. It is up to what countries stress education in fields others than BS Masters and PhD in useless fields where English is spoken clearly with fabricated words.
My channel (and soon primary hst101rox channel) and the Aptera webinar repository on the Internet Archive and Mega cloud drive alternate repository has had this webinar up since March 28th
@@johnmalcom9159 Search would find the video i do this without any monetization across all my channels. I didn't post immediately to primary Aptera repository channel that has more subs, because didn't know if Elaphe would cause a copyright strike but knew they didn't care once Club uploaded it.
To my knowledge, there hasn't been a new car made (mass produced) that does not have at least a micro controller that monitors and controls fuel / air mixture and a ton of other things. Software is behind all of it though it is more firmware than software. Most new cars today have more computing power than the space shuttle had but so does your mobile phone in most cases.
@@ddessert6 No car had computer chips until at least the 1980's. The first cars I drove were 1960's models and everything in the car was analog - carburetor, transmission, ignition system, fuel system. Yes they had basic electrical components but not a single computer chip. It is possible to make cars this way but you can't optimize efficiency in the same way as you don't have the benefit of mass airflow sensors, precise fuel metering, spark control etc. Everything was a compromise. You had vacuum advance to retard the ignition timing etc, but those systems were not very reliable. If you had a vacuum leak that messed everything up. If you want to see how this stuff works go and watch videos on a channel called Vice Grip Garage. The owner of that channel Derek finds these old cars from the 60's and 70's and gets them running again and explains how all the systems work as he does it.
@@aftonline yes, I know there were cars that didn't have chips in them. I had cars from the 70s. In 1995 the US government pushed for better emissions and micro controllers were used to control fuel mixture and ignition timing to start with. I actually designed some systems in the 80s that could do this.
@@777trader8 take the PLC out of any vehicle built after 1994 and it won't run unless you setup the engine like we had in the 70s. My point was that we have had micro controllers PLCs in our vehicles for many years now. If someone is opposed to computers in their vehicle, don't get an EV, get a bike.
It was pretty dry, technical and specific. Plus it had the complication of some speakers being difficult to understand. But it is clear that Elaphe is very serious and diligent about making their motors and control systems safe, well tested, and fault tolerant. My only questions are concerning Elaphe's interaction with Aptera, and the integration and implementation of control and safety systems in the upcoming Aptera. We know that there will be ABS braking, traction control, as well as tie-ins for future Open Pilot ADAS vehicle control. And I am also curious about torque vectoring, and electronic vehicle control, because Elaphe has done extensive engineering and testing in those areas, but Aptera's 3 wheel design would introduce new variables in vehicle dynamics and control. Thanks Steve for posting the Elaphe video.
I suspect that FWD and AWD will have considerably different algorithms for almost all driving functions. In some ways FWD might seem more simple but you lose the precision control of the rear wheel with just a disc brake. In AWD you have very precise control of the rear wheel and can also measure the torque on that wheel. It is great to see that Elaphe is following the risk / test process described in the video. The Aptera will really be a control by wire vehicle and the computations must all work together or there could be serious injury. Safety and backup control systems are incredibly important. (Say you are driving at highway speeds and for some reason the right motor fails. Unless the motor goes into a braking mode, the impact initially would be minor but the VCU needs to sense that the right motor is no longer able to provide braking power and will have to apply more pressure to the right disc brake than to the left. This definitely should display an alert on the console but will the vehicle be able to be operated with one motor inactive or do you need to have it put on a flatbed and repaired before being able to drive?) Very glad that Elaphe and Aptera are considering all these conditions and so many more.)
Dry, technical, and specific is exactly what I want out of a safety briefing from engineers. :)
Thanks for posting this on the forum.This content will resonate with the engineers, system engineers, program/project managers, testers, and logistics people on the forum as it is what they do daily on R&D Projects. I think it has GREAT value as it shows what is behind the curtain in a development efforts. Hopefully, this will provide a better understanding of the effort it takes to develop a product. This is only one component of a whole system. Also, hopefully, it will inform those forum members that say, “Oh it is only a simple/easy change” There are no simple changes. (Little effort, low cost, easy) And this didn’t even address the logistics changes that need to be made with appropriate lead times to support a feature change or development of a new feature.
DoD / NASA style fault analysis. Good stuff.
A difficult job to cover all safety scenarios for sure! Thank you for posting this Elaphe Webinar Steve.
This webinar reminds me very much to the Functional Safety and Cyber Security trainings I got in my company. Overall responsible is the manufactorer (OEM), but this responsibility is forwarded by contract to each supplier. It is absolutely requiered in Europe, new cars can't go into market without fulfilling these ISOs. I think, it is mandatory from Juli 2024.
Not exactly riveting information for a few of us. For those of you that have trouble with these accents there is the "CC" box at the bottom of the active screen for "Closed Caption" which often helps me.
It is refreshing to hear about "Requirements Definitions" of a project before active physical endeavors are begun.
Some of you who had problems understanding That's because the world of engineering does not discriminate. It is up to what countries stress education in fields others than BS Masters and PhD in useless fields where English is spoken clearly with fabricated words.
I could hardly understand a word they said. Perhaps you could do a recap/overview video?
Turn on captions.
My channel (and soon primary hst101rox channel) and the Aptera webinar repository on the Internet Archive and Mega cloud drive alternate repository has had this webinar up since March 28th
And your point? That means your 10 subscribers got to see it 😉
@@johnmalcom9159 Search would find the video i do this without any monetization across all my channels. I didn't post immediately to primary Aptera repository channel that has more subs, because didn't know if Elaphe would cause a copyright strike but knew they didn't care once Club uploaded it.
Does their software have a back door in their software?
If you select the CC option on TH-cam you can read what they are saying. It is much easier to read and hear what they are saying.
All controlled by the software, maybe someone needs to a car without software.
That'd be a Model T.
To my knowledge, there hasn't been a new car made (mass produced) that does not have at least a micro controller that monitors and controls fuel / air mixture and a ton of other things. Software is behind all of it though it is more firmware than software. Most new cars today have more computing power than the space shuttle had but so does your mobile phone in most cases.
@@ddessert6 No car had computer chips until at least the 1980's. The first cars I drove were 1960's models and everything in the car was analog - carburetor, transmission, ignition system, fuel system. Yes they had basic electrical components but not a single computer chip. It is possible to make cars this way but you can't optimize efficiency in the same way as you don't have the benefit of mass airflow sensors, precise fuel metering, spark control etc. Everything was a compromise. You had vacuum advance to retard the ignition timing etc, but those systems were not very reliable. If you had a vacuum leak that messed everything up. If you want to see how this stuff works go and watch videos on a channel called Vice Grip Garage. The owner of that channel Derek finds these old cars from the 60's and 70's and gets them running again and explains how all the systems work as he does it.
@@aftonline yes, I know there were cars that didn't have chips in them. I had cars from the 70s. In 1995 the US government pushed for better emissions and micro controllers were used to control fuel mixture and ignition timing to start with. I actually designed some systems in the 80s that could do this.
@@777trader8 take the PLC out of any vehicle built after 1994 and it won't run unless you setup the engine like we had in the 70s. My point was that we have had micro controllers PLCs in our vehicles for many years now. If someone is opposed to computers in their vehicle, don't get an EV, get a bike.