This is mine*.IPS are scriptfiles and can be edited. My jbbf.ips has the following function:
SCREEN s_steuern()
[...]
ftextout("< F4 > Zusatzwasserpumpe / Wasserventil" ,10,5,0,1);
ftextout("< F5 > Bi-Stabiles Relais kurz aktivieren" ,12,5,0,1);
ftextout("< F6 > Heckklappe öffnen" ,14,5,0,1);
[...]
This is the required function!
ftextout("< F6 > Open trunk lid" ,14,5,0,1);
As changes have to be compiled, currently it's not an idea to update a *.ips source file.
Attached my jbbf70.ipo object file.
Morning,This is mine
![]()
There is a movie "the fault is in our stars" and here the fault is in the two slashes...
I will remove them and hopefully it will work
Assumed it's only a technical issue in INPA, it wouldn't affect the roof operation. Windows may be ok according to ISTA.But the problem is why it is not reading the state of the windows and showing not taought....
As written, wrong idea/nonsense.I deleted the two slashes and nothing happened....

Good DayAttached my jbbf70.ipo object file.














Great news, hope you are well again.Good Day
Sorry I was sick and could not work on the car...
What I did is taking the JBBF files from the attachment and past it to the SGDAT folder, even the CTM files....
When I choose, Body, JBBF and error appears but finally status showing Running not busy
| German | English |
| |
|---|---|---|---|
| Taster Dach schließen betätigt | Button open roof (the right one on the console) | ||
| Taster Dach öffnen betätigt | Button close roof (the left one on the console) | ||
| Fehler am Taster | button fault | ||
| aus | => no | ||
| an | => yes |
Not sure.What about windows status? Are they match with ISTA and show no blocker?

I thought we found the source of issue!!!
as of today:
Honestly, I still have no idea what's wrong with your car!
Took this from your first post. That is a critical issue, that stops the roof WHILE moving. Maybe it got fixed in a professional way in between. If not, a fault code should be present....error like not latching then A6A5 code appears everytime I try to open or close the roof.
Thank you very much, but that is not planned due to several reasons.If you have a plan to visit Madinah or Alula, you are so welcome, just let me know and PM me.
Yes, that's the final step of the rams.For the rear module, when it lowered, there are also two hooks on both sides, but without pressure or by releasing the pressure and manually lower the rear module, the frame leave small gap, so does it need the ram to be pressurized to lower them into place then both hooks lock it in place?
No, definitely not....is there a motor to acivate the hooks on both sides?
Yes, both way it was working and pressurize the lines.I remember a positive test result on the last 8 pages, but I don't trust it.
Yes, when check relays state with INPA or ISTA, and press the button, no change in the relays states.At the moment, this is the only component not working correctly as it doesn't start or get's started by the CTM.
No fault code, but let me check again with INPA.Question:
Currently there is no roof related fault code available at all after deleting all former fault codes before?
SO, the ram lower the frame, then activate the hooks. Soft closing is last stepYes, that's the final step of the rams.
No, definitely not.
Yes, but when it was stuck in the middle, a workshop override and raise and lower the windows, the front driver and side one..Lost window registrations AFAIK never happen WHILE the roof is moving. This can only be a problem BEFORE starting the move process (preconditions), not WHILE.
To be honest, that is not correct.
Same in the opposite order:And what about when opening the roof?