So I fitted the eBay sourced kit in about 30 mins today, using decent crimps and soldering wire extensions with shrink wrap.
Bought the orange wire from the forum shop.
Wired mine direct to the battery and to the earth point near the FBH. I ran out of black insulation tape so used red for now until I put cable trunking in. The control box has black tack to keep it still plus a decent zip tie.
Tested and works. Job done. (2nd remote on its way too)
1998 Defender 110 TUM HS FFR Hard Top XD WOLF
2016 Discovery 4 HSE
1982 Series 3 2.25 Petrol Hard top- Oscar, as featured in Classic Land Rover Magazine for 7 months
19th Jan 2021 5:29 pm
RRUK Site Supporter
Member Since: 16 Aug 2005
Location: UK
Posts: 681
Tested this morning and it all works OK (so far).
Great stuff1998 Defender 110 TUM HS FFR Hard Top XD WOLF
2016 Discovery 4 HSE
1982 Series 3 2.25 Petrol Hard top- Oscar, as featured in Classic Land Rover Magazine for 7 months
20th Jan 2021 9:33 am
ballast
Member Since: 13 Apr 2007
Location: South Midlands
Posts: 185
20th Jan 2021 12:18 pm
munst
Member Since: 16 Sep 2020
Location: GLOS
Posts: 155
The inevitable has happened this morning, went out to take the bin out this morning and the FBH on the disco was running... hadn't told it to!
Checked the module and it was in the tripped (on) state. The remote is in the upper glove box so I'm confident it hasn't been pressed by accident. Now I have to start the long and probably impossible task of finding out which of my neighbours has a 433mhz remote. Next door have a remote garage door that used to set our doorbell off so I think I'll start there
20th Jan 2021 12:23 pm
Pete K
Member Since: 15 Jan 2016
Location: GL
Posts: 10735
I don't know exactly how these work, but are you sure you didn't "leave it on" / forgot to turn it off, on the previous morning ?
I guess you have a plausible cause though
20th Jan 2021 12:38 pm
munst
Member Since: 16 Sep 2020
Location: GLOS
Posts: 155
I had been out the night before to lockup and it wasn't running then, also dont think it had been running long as temp gauge was only about 30% and the wing and bonnet were still cold.
As I understand these 433mhz remotes have a standard protocol and each remote has a supposedly unique ID code which is stored in the module so they only trip when they receive that ID. You can re-pair these modules so might try that if it keeps happening.
20th Jan 2021 12:44 pm
ballast
Member Since: 13 Apr 2007
Location: South Midlands
Posts: 185
Pete K is right. You have to switch them off (see earlier in this thread), otherwise they'll fire back up at some point. The remote control appears to over-ride the car instruction and it remains in its last state. So after you've driven it, you need to press B to switch it off. Had the same thing on mine.
20th Jan 2021 2:48 pm
munst
Member Since: 16 Sep 2020
Location: GLOS
Posts: 155
Yes I am aware of the CANBUS/WBUS relationship. The car had been sat for several days without interference.
I'll get another key on order anyway so I have a spare and I'll pair it with that one if it happens again.
20th Jan 2021 8:30 pm
Mikescotland
Member Since: 27 Apr 2021
Location: Glasgow
Posts: 7
Guys
What happens with this module when you have webasto running via remote command and you turn the engine on at the time when webasto is running? Does it lock out the webasto or anything else happens?
I'm building slightly more complicated logic for this as I have no idea regarding the question above. The additional logic would switch off the module after the key in the ignition has been sensed. But I'm not sure if this is necessary?
27th Apr 2021 12:07 am
Pete K
Member Since: 15 Jan 2016
Location: GL
Posts: 10735
I would leave out that additional logic.
It would cause the heater to go into a cool down cycle and then, have to ramp up again, wasting minutes of heating
27th Apr 2021 11:41 am
Mikescotland
Member Since: 27 Apr 2021
Location: Glasgow
Posts: 7
Fair point. I still don't know what happens if the remote switch still gives on signal and you turn on the engine in the same time...
The logic is also supposed to reset the remote receiver to off state to avoid the situation when remote is ON all the time (unless you press off button) resulting webasto firing up randomly when the drive ended (some people described this problem here).
If it doesn't cause any problems to turn engine on when remote webasto is keeping the FBH on (two same signals, one from the remote and one from the car), i would just have a logic to reset the remote receiver to Off state, leaving the timer to finish its time on. But, as I said, I don't know what happens when both, remote and the car, give the ON signal.
27th Apr 2021 12:12 pm
PROFSR G
Member Since: 06 Mar 2017
Location: Lost
Posts: 5063
Mikescotland wrote:
Guys
What happens with this module when you have webasto running via remote command and you turn the engine on at the time when webasto is running? Does it lock out the webasto or anything else happens?
I'm building slightly more complicated logic for this as I have no idea regarding the question above. The additional logic would switch off the module after the key in the ignition has been sensed. But I'm not sure if this is necessary?
As I understand it if the remote start has activated the FBH prior to engine start, there is no interference from LR settings when the engine is started. Since the start command was signalled by you via the remote module, equally the stop command must also be signalled by the remote.
However, now that you have a remote start fitted your first question might be does your FBH still have the capability to self start as LR intended?
Or, has the remote module you fitted corrupted the original LR programming leaving you with only the remote start option?
Member Since: 30 Dec 2009
Location: Melton Mowbray, Leics
Posts: 181
Well worth having a watch of this.
Although they use the webasto timer/controller, the signals given to the FBH are the same and use the W-bus connection in the same way the remote control boards do.
As you can see, if the heater is running when the can-bus wakes up faults are logged, and (I think) if this happens 3 times in a row the webasto locks out, requiring unlocking by use of the webasto software / cable.
For info - the can-bus wakes up as soon as you unlock the car or open a door - nothing to do with the key in the ignition. When I use my FBH controller/remote connected to the w-bus, I make sure I switch it off first and let the FBH fully shut down before unlocking the car, otherwise I get faults logged. It takes about 2 mins for the FBH to complete it's shutdown/cooldown procedure, so I just set a timer on my watch for this to make sure I give it enough time.
27th Apr 2021 1:50 pm
PROFSR G
Member Since: 06 Mar 2017
Location: Lost
Posts: 5063
So it's safe to assume that any or all remote modules fitted have the problem of either corrupting the Webasto programming, or causing faults being logged by the vehicle preventing auto start?
If so, I wonder how many members using aftermarket remotes are aware they need to shut down at least 2 minutes before going near the car. Or, that their FBH has already had the fuel type programming corrupted preventing auto start by the car?yµ (idµ - eAµ) ψ=mψ
27th Apr 2021 2:58 pm
itguy
Member Since: 30 Dec 2009
Location: Melton Mowbray, Leics
Posts: 181
I think it is fair to surmise that any controller that activates the FBH via w-bus while the CAN bus connections are still connected (and then activated by the car) will log faults in the FBH.
These faults aren't serious really, they just confuse the CAN bus control in the FBH because it can't understand how it already running when the CAN hasn't told it to - so it is just doing the sensible thing and logging a fault saying that it can see the heater is hot/running when it has not been asked to (by CAN).
The corrupting issue is totally separate from everything I have seen and experienced. The particular controller I used where this happened was sending a 'clear faults' command via w-bus to the FBH every time it was used to send a 'start' command to it too. This is (in my view), (a) dangerous, as if the FBH has genuine faults it may not show up and (b) is problematic as different webasto FBH use different commands (and hex codes) to clear faults.
My best guess on this issue is that the controller I tried originally was set to clear faults on a different type of webasto FBH than the one in the D3, thus corrupting it. I got in to a very technical conversation with the designer of that controller and we both came to this conclusion.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
