Traffic collision avoidance system Puns

Hey gang! Hoping someone can help me with an answer to this...

I have a 2019 A4 with Audi Pre-sense.

Totally my fault but today I, unfortunately, ran into the back of someone while I was fiddling with the MMI. We were in heavy traffic and I rolled forward and hit the other car at about 10km/h

My question is - Should this have been possible with Audi pre-sense enabled?

I've been spending the greater portion of a week making an autopilot system which I want to share.

https://github.com/fixerid/sb-projects/wiki/Navigation-Autopilot-with-Collision-Avoidance-System-(NavCas)

https://github.com/fixerid/sb-projects

I'll take any feedback and hopefully it works for you. I've tested it extensively but just on my two ship designs. Also I'm a hobbyist when it comes to coding so forgive any conventional errors and it's my first time trying github.

Personal story if you're interested:

>!Since it was a journey to develop this I'd like to share a little bit. Originally I had wanted to make an autominer script with laser miners and a rangefinder designator. But to do that I needed professional yolol chips for the trig functions which require xhalium and aren't on the market. I saw a video of xhalium being 750km out and thought no way I'm gonna pilot that myself. So that project was shelved and this was started. !<

>!I tried a simple distance method and another algebraic method before figuring out this one. It was a fun struggle trying to remember calculus which pretty much was me googling and trying to understand the formulas again and figuring out how to put it all together. !<

>!But I finally got it working. I had to test it outside of the designer because of the coordinate reversal while in test mode. So I troubleshooted and worked on some things going from station to station to test until I had the kinks worked out. Then I decided to do my first real trip to the void. I thought I'd upgrade my ship with an ore scanner as well and set off. the plan was to get around 200km from origin to test out the ore scanner and some simple mining scripts. I put in coords 75000,0,100000 then partway through switched to 175000,0,100000 until i was about 90-100km from destination. !<

>!I thought this was good enough to test. So I went to the nearest asteroid to mine. The simple sweeper script worked but the ore scanner wouldn't even turn on. Then I remembered there may have been a bug when you try to place turrets outside of the designer so I tried to take the scanner and placed it on the ore collector's turret instead. Only the ore collector disappeared or was yeeted at extreme velocities. So I couldn't replace it and had to collect manually. I go to collect manu

https://www.msn.com/en-us/autos/news/a-tesla-mystery-why-didnt-auto-braking-stop-these-crashes/ar-AAPeA2O

I'm doing some research into different collision avoidance systems and most brands seem to emphasize forward collision avoidance or automatic emergency braking (AEB). What I want to know is, do any of the brands have a "swerving" system similar to what the Telsa can do, i.e. swerve to avoid a crash if braking is not feasible, or swerve if another car is about to side-swipe you, etc.

In a similar vein, can anyone point me to objective reports comparing the quality of different systems (how well each feature works to detect cars or pedestrians) and the overall comprehensiveness of the systems (how many collision avoidance features are installed)?

Thanks in advance!

Another thing thing my small monkey brain also came up with:

You need a single Basic Yolol Chip and a Flight Control Unit Advanced for this. Either use a memory chip to save a spd variable or another lever with 0 centering speed, this is for the autopilot to be set to whatever speed you want

Button= Apilot

If using Hinges with rangefinder: hinge-> rfh

If using a lamp for when something is detected -> lmp

Rangefinder Edits:

Rangefinder -> rf

All Left Rangefinders Distance -> rfdl

All Right Rangefinders Distance -> rfdr

All Top Rangefinders Distance -> rfdu

All Bottom Rangefinders Distance -> rfdd

Ship control edits:

FcuForward -> FcuF

FcuBackwards -> FcuB

FcuRightLeft -> FcuRL

FcuUpDown -> FcuUD

a=1000 c=100 :lmp=0 :spd=:FcuF

If :Apilot==1 then :rfh=1 :rf=1 else :rfh=0 :rf=0 goto1 end

h=:rfdr i=:rfdl j=:rfdu k=:rfdd :FcuB=0 :FcuRL=0 :FcuUD=0 :lmp=0

if h<5 or i<5 or j<5 or k<5 then goto2 end :FcuF=:Spd

if h!=a then goto7end if i!=a then goto8end if j!=a then goto9end

if k!=a then :FcuB=0 :FcuF=0 :FcuUD=c k=:rfdd :lmp=1 goto2endgoto2

if h!=a then :FcuB=0 :FcuF=0 :FcuRL=0-c h=:rfdr :lmp=1 goto2endgoto5

if i!=a then :FcuB=0 :FcuF=0 :FcuRL=c i=:rfdl :lmp=1 goto2endgoto5

if j!=a then :FcuB=0 :FcuF=0 :FcuUD=0-c j=:rfdu :lmp=1 goto2endgoto5

// The set desired cruise speed THEN enable autopilot

// Disable autopilot to reset speed

Doesn't matter how many rangefinders you have you just need to make sure you name the distances right.

My monkey brain will eventually redo this with just math for the different sides and not rely on if statements, but it needs to cool off, I never claimed I was smart.

something based around:

:FcuRL=(:rfdr-1000)*100 :FcuUD=(:rfdu-1000)*100

:FcuRL=(:rfdl-1000)*-100 :FcuUD=(:rfdd-1000)*-100 goto1

Maybe some code wizard can guide me in a direction for this one. :)

This started happening a couple days ago. Suddenly the car is trembling while at a full stop (In a dunkin drive thru line) and this warning came up. I had to turn my car off and then on for it to not be shaking anymore.
It was fine for several days before suddenly today, it started shaking and then just. Sputtered out. I was at a red light and noticed that hitting the gas was doing Nothing, I had to throw my hazards on so the cars behind me would pass while I turned the car off and back on. I had to stop by a house I was dogsitting for, and it was fine the rest of the way. After, I drove home and it started shaking again when I was 2 minutes away, so I pulled over and turned it off & on. Drove the last 2 minutes back, and when I was parking, it started doing the rattling and the 'check forward collision avoidance assist system' message appeared on the screen. It didn't stop shaking until I turned the car off.

WTF is this? I have 33k miles on this car and never experienced anything like this before. I have to drive 4 hours to pick up my new roommate and help him move in only 2 days, so obviously this is the worst time for this to happen. Any potential causes that can be fixed without taking it to a dealership? Obv I'll have to bring it out eventually, but wondering if I can safely pick up my friend in 2 days or not. Ugh..

Saw some articles about people getting e-mails when their collision avoidance systems go offline and it got me wondering. Do you think that in the future people will be held liable if they knowingly refuse to repair and/or disable their collision avoidance systems and then get in accidents that that system could have prevented?

Some suggestions.

You can have all the range finders turn on/off using a single field. I use RF to turn on 120 different range finders.

You can also use it on the 'range detected'.

Simple setup, you can use the same field for all the RangeFinderDistance. Or even have 'groups' if you want.

I often either go with 1 group or 4 groups.

If you have 100 range finders named RF, you can turn all 100 on/off with RF. Then set all their distance to RFD. They will all report the same 'value'. However, if any 1 of them sees something closer (than 1000) it will report that new value, e.g. 950.

so you can have 100 range finders with a single code something like

1 IF :RF THEN GOTO 2 ELSE GOTO1 END 
2 IF :RFD<999 THEN :FcuForward=0 END
3 GOTO1

Alternatively, If I am using 4 groupings, for RFTL(RangeFindersTopLeft), TR, BR(RangeFindersBottomRight), BL. Then you can if check against those 4 groups.

No need to name every single 1 a unique name.

Saw an article about some people getting e-mails about their collision avoidance systems not working properly and it got me thinking. Although these systems aren’t perfect and in fact turn themselves off in certain conditions, still, it seems to me that eventually the issue is gonna come up (if it hasn’t already) where someone has an accident that almost certainly could have been prevented by their collision avoidance system that they knew needed repair (or they knowingly compromised/disabled) themselves.

Do you think people will be held responsible for those collisions in situations where they otherwise wouldn’t have?

I had just gotten a new car, and it had a collision avoidance system called Eyesight. The next day I was driving it and the screen behind the steering wheel said "Eyesight Off" I turned the car off and back on again, but it still said "Eyesight off." I called the dealer, and he asked if anything was on the windshield. I said that there was fog on the windshield, and he said that was the reason. I used the wipers to get rid of the fog, and that worked.

However when the fog started accumulating again Eyesight turned off and I noticed that it said "no camera view," but that message disappeared after a few seconds. That messages most likely appeared during the other times when it turned off, but I didn't notice it since it vanished after a few seconds. Why would they specifically design a message to disappear by itself? It told me exactly what the problem was, but I didn't notice it at first since it disappeared before I looked at the screen. I've never seen that happen with a computer, but somehow the error message in the car would go away by itself. It would still say "Eyesight off," but it wouldn't mention the reason why.

I eventually found that there was a button on the bottom of the steering wheel which could make the message reappear, but it was just such an unintuitive setup. Why not just design it so that the message "no camera view" is displayed until either the problem is fixed, or until I specifically press a button to get rid of it? To be clear, when Eyesight wasn't working, the message "Eyesight off" would remain the entire time, but the message "no camera view" would disappear after a few seconds. Why would it tell me there's a problem with Eyesight, but make the explanation of the problem disappear after a few seconds?

Scary situation today in my 2021 EX Telluride.

I went to pick up my daughter from preschool today with my 1 month old in the car. I had just filled up the tank and was turning right onto a main road in a small town. The light at the end of the block was red, so I never picked up much speed - MAYBE 15MPH. I stepped on the brakes and there was a grinding sound/bumpy feeling. I thought maybe I ran something over or had pushed a button I shouldn’t have, or...something. I started to scan my console and steering and then I realized that I was stepping on my brakes, but nothing was happening. I started to come up on the cars in front of me and was pumping/slamming on my brakes but nothing was working. I swerved into the left turn lane to avoid hitting the car ahead and was approaching the nearest car in that lane when suddenly my brakes worked. I was shaking, but luckily only a block from my in-laws, so when the light turned green I very slowly followed traffic to make it to their place and have a safe place to park. My car started beeping at me about my blind spot warning/forward collision as I went to turn onto their street, but I was no where near another car. I pulled onto the empty road with the warnings still going off and parked in front of their house. My dash had the master warning light, collision warning light, ABS light, and my slip indicator light all on with a notice that said “Check Forward Collision Avoidance Assist System”.

I called my husband who rushed to pick up my toddler from preschool and come get us. My in-laws were out and it was getting late, so we decided to wait to call AAA until the morning and then have my car towed to the nearest dealership. I’ve only had my car since mid-December and haven’t had any issues. We had a foot of snow this past weekend and we drove in it some, but it handled perfectly. A week ago we also drove it across the state and used the cruise control a lot. I don’t know if either of those things could have an impact on this, but again, we haven’t had any issues. No scraping the bottom of the car or running anything over, etc.

The whole thing has me very shaken up. I’m thankful that I was able to avoid an accident and that I was so close to my in-laws home when it happened. I am also very very thankful that it didn’t happen to me 15 minutes before when I was coming down the freeway going 60. Above all I am thankful that both of my girls are OK. I mean, we bought this car for the safety features and many award