Besides - iBusRR.exe - and - IBusRR.ini - I need - MSCOMM32.OCX - .
Is there any other files required to run iBusRR ?
When you download iBuscomM.zip there´s a whole bunch of files coming with it . Are any of these needed or not?
cheers
Besides - iBusRR.exe - and - IBusRR.ini - I need - MSCOMM32.OCX - .
Is there any other files required to run iBusRR ?
When you download iBuscomM.zip there´s a whole bunch of files coming with it . Are any of these needed or not?
cheers
I´m working on a skin to use the window/trunk/sunroof open command and I´m also gonna use it through a shuttle xpress (works great in a bimmer, the color matches....), here´s a question :
can you use 1 button for open AND close command?
Let´s say I press the front passenger window button and it opens it and once it´s opened the next time I press the same button it´s gonna close it.
seems to me that´s it´s a toughy unless someone has a workaround.
It looks like it´s impossible for the iBus to tell RR what the state of the windows are so RR can send the appropriate command... right ?
Any ideas?
we haven't found yet how to query the car for the status of the windows, so the only way for now would be to use a variable in your skin
The files coming with ibuscomm are the VB6 run-time files. You'll need them for iBusRR also
@Warfiels : working like a charm !!! :rock:
just 2 things, the rear passenger window doesn't want to get down, probably a typo in the .ini file or something... gonna check it out.
also, everything works fine except that between each time I press a button I have to wait 2-5 seconds before I can succesfully get something happeningagain, even when I just used one of the RR button and then use the actual window swith of the car.
Is there a time between each command that you can set up in the .ini file or anywhere else?
cheers
EDIT: after doing some research I came along this ¨trick¨: if you remove the ¨01¨ at the end of the codes for the windows you shouldn´t have to wait in between using commands OR console buttons. Has it been verified as working?
Why are you guys hunting for these ibus window commands in the dark all the time?
WiniBus gives you a plain text translation of the ibus commands on the fly, makes it really easy to understand the ibus command syntax
So grab youself a copy of WiniBus app, plug in the ibus interface, and start typing in ibus codes.
WinBus will tell you what the code means. On your PC, not on your car.
Easy, simple, safe, and very very informative.
PS: you need to know some German!
The GM sends out window/door status info at regular intervals
typical msg:
00 05 BF 7A 51 20 B1
GM --> GLO 7Ah_TürKlappen offen: Fahrertür Kofferraum ZV: Innenlicht ein
Bytes 51 and 20 contain bit-mapped info on what door etc is open
Guys,
as some of you might know, I'm using a different solution for the BMW which integrates with the original factory Nav/Sound/Monitor (CarX), but "we" are always interested in new projects; at the moment some people e.g. are working on an integration of cPos into the original BMW equipment.
However, if you need some translations between German<->English, just post your questions here, I'm willing to help.
If there's some interest, I can check this thread regularly (daily), so ...
cu
dagezum
A little help from you i bus experts.. Check out this thread. We are in the middle of getting the DICE HD radio to work via ibus minus the BMW.. this way we have a stable HD Radio solution for everyone..
http://www.mp3car.com/vbulletin/hardware-development/93791-someone-here-has-be-be-able-to-crack-this-hdradio-for-the-car.html