I suppose that's my next thing on the list!Īny advice would be greatly appreciated. I haven't checked the trailer socket yet. It almost seems like the rear fogs are being interlocked against coming on. It says turns off the cold check and the check control but you still get. I dont have navcoder, but I do have MSV-2.
#NAVCODER COLD CHECK SOFTWARE#
Is there some sort of interlock that disables the rear fogs when a trailer lighting connector is plugged in? I've towed recently and am wondering if there could be a connection. Software likely NavCoder or BMW Scanner 1.4.0 can typical read the BT What I. with NavCoder when checking car for faults or just plain playing with INPA. I cant see any issues in the LCM configuration. The indicator light on the cluster comes on as normal, but the lights just dont come on at the back end of the car. I've checked absolutely everything to do with the lamps and the LCM. That works fine and proves that the LCM can turn the lights on, if it wants to! I have LED rear light clusters fitted, I know that there isn't a connection problem to the lamp units as I can configure the fog lights to come on 'dim' with the tail lights. MySerial.Has anyone come across this problem before? It appears that my rear fog lights have simply stopped working. SoftwareSerial mySerial(7, 8) // 7 is Rx, 8 is Tx From experience Navcoder doesnt, so you just set both values. Im pretty sure if you set this to yes, most systems will also disable the cold test. Bike cranked fine, and sputtered, but wouldnt. Its been parked in the garage for about 6 weeks (between the cold weather and lots of stuff going on, shes been pretty neglected). In the LCM there is a setting for bixeon lights. I suspect I can guess the answer to this question, but Ill pose it anyway. Have you an FTDI cable for software serial? However, the balast doesnt do this so you need to turn off cold testing of the dipped beam.
#NAVCODER COLD CHECK CODE#
If I was using the code structure I suggested I would use IF (serial.available > 0) rather than WHILE so that the code doesn't sit reading characters at the slow baud rate (and sorry for getting my baud rates mixed up - a nice slow 9600 is best). I'm not sure what was going on in my original sketch when using this code, but in the new sketch, it works a treat. I am experiencing rough idle when the engine is cold.
#NAVCODER COLD CHECK SERIAL#
I just took your advice and wrote a new sketch using the serial code that I posted above. This would then become the function I called readIbus(). I am thinking of disabling the cold bulb check, but should i. I was wondering what is the difference between hot and cold bulb check, and which one is safe to disable. I would write a short sketch that just reads that and prints the buffer contents from time to time. Guys, I have just ordered a I-BUS interface and will get NAVCODER to code LCM to get rid of that light flicker issue i have. But if I drive in urban area, accelerating slowly or going uphill and maintaining the speed, I hear some wastegate rattle (actually a lot if Ive Terrys suggested values on menu10 and 12).
At idle and WGP 100 my vacuum is 27' and drops as I drop wastegateposition value. How do you know it's not working? You haven't shown where the variables are declared so I can't say if you have an error there. Im doing WG vacuum value checks because of wastegate rattle. if you're using NCS by modifying FSWPSW files, it helps to have a translator, or use Revtor's NCSdummy that has an integrated german-to-english translator. I have experience doing so with both programs E39 and E53.
That serial code looks like it should work. NCSexpert and NavCoder will both accomplish this on LCM3 and LCM4.
0 kommentar(er)
