Posted: Monday Feb 19th, 2007 12:45 pm |
|
1st Post |
palmlodge
Member
Joined: | Thursday Dec 14th, 2006 |
Location: | United Kingdom |
Posts: | 507 |
Status: |
Offline
|
back to top
|
Another on my list of Comfort isues !
All started about a month ago - I have an on and off response associated with the zone change for the light sensor, Been fine for about 2 years.
The problem appears that the light module/zone is being triggered - and the lights go on and off repeatedly around the dusk/dawn times. couple of x10 modules clicking away furiously and cbus lights on and off.
I've changed the photocell 3 times, the resistor 3 times, and now a new LSM module with a new resistor.
When the zone does change, the light led on the lsm doesnt appear to change tho
???!!
Last edited on Sunday Apr 1st, 2007 02:33 am by
|
Posted: Monday Feb 19th, 2007 01:52 pm |
|
2nd Post |
palmlodge
Member
Joined: | Thursday Dec 14th, 2006 |
Location: | United Kingdom |
Posts: | 507 |
Status: |
Offline
|
back to top
|
Been playing with the rotary sensitivity settings for a few days - all that does is vary the time is happens.
Here's an extract from the homeseer log. Do you think the LSM is not getting enough juice from Comfort ?? What sort of voltage/ampage should it be recieving to work correctly ?
2/19/2007 2:42:54 PM
Input Activation: LightSensor Off
2/19/2007 2:42:55 PM
Counter Changed Name:CBUSOutSideLight Zone:83 No:23 Value:255
2/19/2007 2:42:55 PM
Counter Changed Name:CBUSStairLEDs Zone:97 No:38 Value:255
2/19/2007 2:42:55 PM
Counter Changed Name:CBUSDiningRoomB2 Zone:88 No:28 Value:255
2/19/2007 2:42:55 PM
Counter Changed Name:CBUSEntryDLTB7 Zone:89 No:29 Value:255
2/19/2007 2:42:55 PM
Counter Changed Name:LoungeLampB Zone:]10 No:52 Value:255
2/19/2007 2:42:55 PM
Input Activation: LightSensor On
2/19/2007 2:42:56 PM
Counter Changed Name:CBUSLoungeDLTB6 Zone:98 No:39 Value:255
2/19/2007 2:42:56 PM
Counter Changed Name:CBUSLoungeDLTB6 Zone:98 No:39 Value:255
2/19/2007 2:42:56 PM
Counter Changed Name:CBUSLoungeDLTB6 Zone:98 No:39 Value:255
2/19/2007 2:42:56 PM
Counter Changed Name:CBUSOutSideLight Zone:83 No:23 Value:0
2/19/2007 2:42:56 PM
Counter Changed Name:CBUSStairLEDs Zone:97 No:38 Value:0
2/19/2007 2:42:56 PM
Counter Changed Name:CBUSDiningRoomB2 Zone:88 No:28 Value:0
2/19/2007 2:42:56 PM
pjcComfort2
2/19/2007 2:42:56 PM
Changed Name:LoungeLampB Zone:]10 No:52 Value:0
2/19/2007 2:42:56 PM
Counter Changed Name:CBUSLoungeDLTB6 Zone:98 No:39 Value:0
2/19/2007 2:42:56 PM
Counter Changed Name:CBUSLoungeDLTB6 Zone:98 No:39 Value:0
2/19/2007 2:42:56 PM
Counter Changed Name:CBUSLoungeDLTB6 Zone:98 No:39 Value:0
2/19/2007 2:43:04 PM
Input Activation: LightSensor Off
2/19/2007 2:43:05 PM
Counter Changed Name:CBUSOutSideLight Zone:83 No:23 Value:255
2/19/2007 2:43:05 PM
Counter Changed Name:CBUSStairLEDs Zone:97 No:38 Value:255
2/19/2007 2:43:05 PM
Counter Changed Name:CBUSDiningRoomB2 Zone:88 No:28 Value:255
2/19/2007 2:43:05 PM
Counter Changed Name:CBUSEntryDLTB7 Zone:89 No:29 Value:255
2/19/2007 2:43:05 PM
Counter Changed Name:LoungeLampB Zone:]10 No:52 Value:255
2/19/2007 2:43:05 PM
Input Activation: LightSensor On
2/19/2007 2:43:06 PM
Counter Changed Name:CBUSLoungeDLTB6 Zone:98 No:39 Value:255
2/19/2007 2:43:06 PM
Counter Changed Name:CBUSLoungeDLTB6 Zone:98 No:39 Value:255
2/19/2007 2:43:06 PM
Counter Changed Name:CBUSLoungeDLTB6 Zone:98 No:39 Value:255
2/19/2007 2:43:06 PM
Counter Changed Name:CBUSOutSideLight Zone:83 No:23 Value:0
2/19/2007 2:43:06 PM
Counter Changed Name:CBUSStairLEDs Zone:97 No:38 Value:0
2/19/2007 2:43:06 PM
Counter Changed Name:CBUSDiningRoomB2 Zone:88 No:28 Value:0
2/19/2007 2:43:06 PM
Counter Changed Name:CBUSEntryDLTB7 Zone:89 No:29 Value:0
2/19/2007 2:43:06 PM
Counter Changed Name:LoungeLampB Zone:]10 No:52 Value:0
2/19/2007 2:43:06 PM
Counter Changed Name:CBUSLoungeDLTB6 Zone:98 No:39 Value:0
2/19/2007 2:43:06 PM
Counter Changed Name:CBUSLoungeDLTB6 Zone:98 No:39 Value:0
2/19/2007 2:43:06 PM
Counter Changed Name:CBUSLoungeDLTB6 Zone:98 No:39 Value:0
2/19/2007 2:43:14 PM
Input Activation: LightSensor Off
2/19/2007 2:43:15 PM
Counter Changed Name:CBUSOutSideLight Zone:83 No:23 Value:255
2/19/2007 2:43:15 PM
Counter Changed Name:CBUSStairLEDs Zone:97 No:38 Value:255
2/19/2007 2:43:15 PM
Counter Changed Name:CBUSDiningRoomB2 Zone:88 No:28 Value:255
2/19/2007 2:43:15 PM
Counter Changed Name:CBUSEntryDLTB7 Zone:89 No:29 Value:255
2/19/2007 2:43:15 PM
Counter Changed Name:LoungeLampB Zone:]10 No:52 Value:255
2/19/2007 2:43:15 PM
Counter Changed Name:CBUSLoungeDLTB6 Zone:98 No:39 Value:255
2/19/2007 2:43:15 PM
Counter Changed Name:CBUSLoungeDLTB6 Zone:98 No:39 Value:255
2/19/2007 2:43:15 PM
Counter Changed Name:CBUSLoungeDLTB6 Zone:98 No:39 Value:255
2/19/2007 2:45:25 PM
Input Activation: LightSensor On
2/19/2007 2:45:25 PM
Counter Changed Name:CBUSOutSideLight Zone:83 No:23 Value:0
2/19/2007 2:45:25 PM
Counter Changed Name:CBUSStairLEDs Zone:97 No:38 Value:0
2/19/2007 2:45:25 PM
Counter Changed Name:CBUSDiningRoomB2 Zone:88 No:28 Value:0
2/19/2007 2:45:26 PM
Counter Changed Name:CBUSEntryDLTB7 Zone:89 No:29 Value:0
2/19/2007 2:45:26 PM
Counter Changed Name:LoungeLampB Zone:]10 No:52 Value:0
2/19/2007 2:45:26 PM
Counter Changed Name:CBUSLoungeDLTB6 Zone:98 No:39 Value:0
2/19/2007 2:45:26 PM
Counter Changed Name:CBUSLoungeDLTB6 Zone:98 No:39 Value:0
2/19/2007 2:45:26 PM
Counter Changed Name:CBUSLoungeDLTB6 Zone:98 No:39 Value:0
2/19/2007 2:45:34 PM
Input Activation: LightSensor Off
2/19/2007 2:45:35 PM
Counter Changed Name:CBUSOutSideLight Zone:83 No:23 Value:255
2/19/2007 2:45:35 PM
Counter Changed Name:CBUSStairLEDs Zone:97 No:38 Value:255
2/19/2007 2:45:35 PM
Counter Changed Name:CBUSDiningRoomB2 Zone:88 No:28 Value:255
2/19/2007 2:45:35 PM
Counter Changed Name:CBUSEntryDLTB7 Zone:89 No:29 Value:255
2/19/2007 2:45:35 PM
Counter Changed Name:LoungeLampB Zone:]10 No:52 Value:255
2/19/2007 2:45:35 PM
Input Activation: LightSensor On
2/19/2007 2:45:36 PM
Counter Changed Name:CBUSLoungeDLTB6 Zone:98 No:39 Value:255
2/19/2007 2:45:36 PM
Counter Changed Name:CBUSLoungeDLTB6 Zone:98 No:39 Value:255
2/19/2007 2:45:36 PM
Counter Changed Name:CBUSLoungeDLTB6 Zone:98 No:39 Value:255
2/19/2007 2:45:36 PM
Counter Changed Name:CBUSOutSideLight Zone:83 No:23 Value:0
2/19/2007 2:45:36 PM
Counter Changed Name:CBUSStairLEDs Zone:97 No:38 Value:0
2/19/2007 2:45:36 PM
Counter Changed Name:CBUSDiningRoomB2 Zone:88 No:28 Value:0
2/19/2007 2:45:36 PM
Counter Changed Name:CBUSEntryDLTB7 Zone:89 No:29 Value:0
2/19/2007 2:45:36 PM
Counter Changed Name:LoungeLampB Zone:]10 No:52 Value:0
2/19/2007 2:45:36 PM
Counter Changed Name:CBUSLoungeDLTB6 Zone:98 No:39 Value:0
2/19/2007 2:45:36 PM
Counter Changed Name:CBUSLoungeDLTB6 Zone:98 No:39 Value:0
2/19/2007 2:45:36 PM
Counter Changed Name:CBUSLoungeDLTB6 Zone:98 No:39 Value:0 Last edited on Thursday Mar 1st, 2007 07:08 am by
|
Posted: Monday Feb 19th, 2007 05:39 pm |
|
3rd Post |
ndh
Comfort Installers
back to top
|
Hi,
Any chance there is a new / stray source of light hitting the LDR?
There is normally plenty of hysterisis to avoid shunting like this.
Are you using the correct zone type?
How soon after installing the G2 main board did this occur?
Might be related to the pillars / isolation thing? (There are a lot of these light sensors out there and if you have tried 2 ...)
A temporary solution may be to add a (10 min?) timer to the first trigger.
Nigel
|
Posted: Monday Feb 19th, 2007 07:23 pm |
|
4th Post |
palmlodge
Member
Joined: | Thursday Dec 14th, 2006 |
Location: | United Kingdom |
Posts: | 507 |
Status: |
Offline
|
back to top
|
Hi,
Any chance there is a new / stray source of light hitting the LDR?
To isolate this it has been tried in the same place it's been for the past few years, and and now more hidden in the soffits where the air vents provide plenty of light. When the lights are going on off on off, the led on the LSM01 appears to stay solid.
There is normally plenty of hysterisis to avoid shunting like this.
Thats what I understood. It appears to be ignoring it.
Are you using the correct zone type?
Cytech have my config (see below) - it's just set to a SwitchNC[24]
How soon after installing the G2 main board did this occur?
All this weirdness started happening mid Dec. I had the G2 board for quite a while before that.
Might be related to the pillars / isolation thing? (There are a lot of these light sensors out there and if you have tried 2 ...)
It's mounted on the MDF support board that everything hangs off as I need more Comfort enclosure space ! No metal involved.
A temporary solution may be to add a (10 min?) timer to the first trigger.
I did this back in Jan (with a 30 min check) - at which point the system went potty and started arming to Away mode when we were inside the house !! It had a mind of its own. Cytech have had my config for this for 5 weeks and I've been chasing for an update - but nothing so far.
Nigel
Last edited on Sunday Apr 1st, 2007 02:34 am by
|
Posted: Tuesday Feb 20th, 2007 08:40 am |
|
5th Post |
slychiu
Administrator
Joined: | Saturday Apr 29th, 2006 |
Location: | Singapore |
Posts: | 5493 |
Status: |
Offline
|
back to top
|
The many changes in state for the LSM should be due to variations in light levels around dusk. Using a timer to delay the activation of the LSM responses is the correct way to handle this, but you encountered another problem with the system arming by itself to Away Mode when the timer was implemented
The cause of this automatic arming phenomenon has now been identified, see http://www.comfortforums.com/forum36/427.html
It is due to a bug in Comfigurator which actiavtes tge wrong response in the Timer, pointing to an Away Arm Response. This willbe fixed in the next software release
I have send you privately a workaround which does not have this behaviour
Check it out and see if the arming problem occurs now
regarfds
|
Posted: Tuesday Feb 20th, 2007 08:56 am |
|
6th Post |
palmlodge
Member
Joined: | Thursday Dec 14th, 2006 |
Location: | United Kingdom |
Posts: | 507 |
Status: |
Offline
|
back to top
|
Thanks for the resolution to finding the bug Chiu.
The timer was a temporary workaround - this is not the expected behaviour for the LSM01 - has been working as expected for the past 5 years (with Comfort 1 and 2)
|
Posted: Wednesday Feb 21st, 2007 07:09 am |
|
7th Post |
palmlodge
Member
Joined: | Thursday Dec 14th, 2006 |
Location: | United Kingdom |
Posts: | 507 |
Status: |
Offline
|
back to top
|
Now, we need to figure out what is happening with the lsm01.
Again, possible voltage issue ? Im running out of ideas. and having to manually turn on llights - eurgh ! :-)
|
Posted: Wednesday Feb 21st, 2007 09:24 am |
|
8th Post |
on4cet
Member
Joined: | Sunday Dec 17th, 2006 |
Location: | Belgium |
Posts: | 23 |
Status: |
Offline
|
back to top
|
Have you checked the variable resistor (potentiometer) on its behaviour ? Is it giving a quite constant resistance value (off course within a quite short time at daytime) ?
Although you mention that the LED doesn't change, maybe the output driver on the lsm01 behaves erraticly ? Or, if a relay is mounted, the relay ?
Kind regards,
Bart
|
Posted: Wednesday Feb 21st, 2007 03:35 pm |
|
9th Post |
palmlodge
Member
Joined: | Thursday Dec 14th, 2006 |
Location: | United Kingdom |
Posts: | 507 |
Status: |
Offline
|
back to top
|
I've been sent a new LSM - same behaviour. Generally around dawn and dusk (although can vary slightly)
Plugged directly into a zone input - no relays.
Last edited on Wednesday Feb 21st, 2007 03:35 pm by palmlodge
|
Posted: Friday Feb 23rd, 2007 11:30 am |
|
10th Post |
ident
Administrator
Joined: | Wednesday Aug 9th, 2006 |
Location: | Singapore |
Posts: | 3493 |
Status: |
Offline
|
back to top
|
We have verified with a LSM01 that what you report does happen
At around dusk, the LSM does switch on and off several times due to varying light levels. The variation in light level may not be perceptible but it registers with the sensor.
You can increase the sensitivity time of the zone type used for the LSM. In Zone Types, select the Normally Closed or Open Switch, and set sensitivity to the maximum value of 850 ms. This requires a longer pulse to activate the input to sense ON
However you will have to apply a timer to get this to work properly, like what you did earlier which should work well. There was a Comfigurator bug which activated an arming response, but I gave you a workaround which you can use.
The ON and OFF Responses will start a timer (for 10 minutes), at the end of which check the LSM Input and switch the lights if the input is still in the same state
This should also prevent multiple switching when a cloud passes by arounf dusk or dawn
We will include the advice to use the timer in the LSM manual and include a sample Response
|
Posted: Wednesday Feb 28th, 2007 07:36 am |
|
11th Post |
palmlodge
Member
Joined: | Thursday Dec 14th, 2006 |
Location: | United Kingdom |
Posts: | 507 |
Status: |
Offline
|
back to top
|
A timer is not going to solve this.
A timer is fine for when you want to start activating devices at dawn/dusk - bt if you have other logic which checks for the current state of the light sensor, there is a large window where this all fails.
ie if you have door zones that check for light levels to activate exterior lights, these wont work for that period.
Again this HAD been working fine for over 5 years with no timers !
|
Posted: Wednesday Feb 28th, 2007 08:12 am |
|
12th Post |
ident
Administrator
Joined: | Wednesday Aug 9th, 2006 |
Location: | Singapore |
Posts: | 3493 |
Status: |
Offline
|
back to top
|
I dont see why a timer would not work if you have other logic which checks for the current state of the light sensor
It is only during the dusk or dawn, ie when the light level is at the theshold setting that the sensor will report either on or off. It will not fail, as the sensor will be either on or off when you check it which is not wrong as the light level could be either way.
It does not matter at all if the sensor changes state over the course of a few minutes at this time because I assume you only would check the sensor at a specific time
if you are constantly checking the sensor state to do your logic and you need a consistent state, you can also use a timer in a similar way to set a flag, and just check the flag. If I am not understanding your application perhaps you could supply more information
I dont have any idea why it did not have any transitons for 5 years, as the LSM has not been changed during that time. Perhaps the sensor you use is now more sensitive than before. Our tests here show that we do get this fluctuation
Coments from other users who can shed light would be welcome
|
Posted: Wednesday Feb 28th, 2007 09:05 am |
|
13th Post |
on4cet
Member
Joined: | Sunday Dec 17th, 2006 |
Location: | Belgium |
Posts: | 23 |
Status: |
Offline
|
back to top
|
Just trying to help a hand, i thought of the hysteresis which is mentioned in the LSMmanual. I will put the extract here :
----->
6. Place the light sensor where the ambient light DAYLIGHT
conditions are brighter than the required threshold VR1light level. The LED should be OFF. If not, adjust
VR1 clockwise (CW) until the LED turns on. Note
the position of the trimmer wiper. Now Adjust the
trimmer so that it is between the two positions. The switching point is subject to hysteresis,
i.e. when the LED turns on, the light level has to go some way below the point at which it
turned on, in order to turn off. This is so that at the threshold light level, the output does not
oscillate between on and off.
<-----
When looking at this, it shouldn't oscillate between on & off that much, and thinking of my own installation, can't remember seeing the input change ...
I think there must be something else, because, looking at the text of the lsm manual :
When it goes dark, the LED goes ON, but according to the manual, the light has to be a lot brighter than the switching point at which the led turned ON, in order to put it OFF
Could it be something with the VR1 trimmer ? Dust in it ?
Kind regards,
Bart
PS. I find it strange that the light level changes at 2.4x or 2.5x PM ?? I live in Belgium, which only differs 1 hr with the UK, and at these days, my lsm changes state at about 7.45 AM and 18.15 PM (approx.) Something to investigate ???
|
Posted: Wednesday Feb 28th, 2007 02:12 pm |
|
14th Post |
Pgordon
Member
back to top
|
I had an "original" LSM01 which, once I got it adjusted "just right" didn't seem to oscillate much around the dawn/dusk switching points. I recall the LSM zone switching "cleanly" at the changeover point, and doing so within about 20 minutes of the "official" sunrise/sunset times for my location. I Was very happy with this performance! Then unfortunately, some local wildlife eat my sensor, and I replaced the LDR and the internal resistor with alternatives from CPC. The internal resistor is a 20K one I believe.
The performance characteristic is now sligtly different.. - I *am* still progressively fine-tuning it though, so I may yet get better results. What I have noticed however, is that I still don't have the switching point quite right, and the adjustment of the trimmer is in a different range (presumably this is linked to the value of the resistor?) - previously, the perfect trimmer position was about 25% from the leftmost stop position, This time round I started from that position and have been gradually moving back to the leftmost stop position and observing the result. As stated above, it's getting better, but still not spot on, and I need to go a little further back. - Trouble is, I'm already almost right back to the leftmost stop position on the trimmer, and there's not much more adjustment possible in the direction I need to go.. (I have maybe 5% more range to play with - hopefully that will be enough).
I am also noticing that it does seem to oscillate more around the switching point, and will switch on a dull afternoon if a dark cloud goes by for example. I don't think it did this as much previously.
My LDR is positioned such that it is not affected by passing car headlights, street lights, and so on. I agree that the hysterisis thing needs a bit of attention. I have not yet tried the zone sensitivty setting recently suggested, so I'll implement that very soon. I don't have any great objection to using a timer to eliminate the hysterisis around the switching point, but I have a great objection to this arming the system incorrectly due to a bug! - so that's not an option until that issue is rectified....
I see Gareth's point about the other logic though... - many many other responses may just check the LSM zone status to determine actions, - the LSM zone status may be wrong not only around the dusk/dawn switching points, but also (in my case at least) on a dull day... - Granted this *could* be worked around by expanding the logic (using flags etc), and if starting from scratch this would be sensible to do anyway. However, this may be a real PITA to adjust lots of pre-existing responses to now check a flag rather than the zone status directly...
Of course, if Comfort had a RTC, and could reference the time in responses (and even knew when sunrise/sunset was) might help quite a bit!!! (but that's for another thread methinks!)
HTH
Paul G.
|
Posted: Wednesday Feb 28th, 2007 02:42 pm |
|
15th Post |
on4cet
Member
Joined: | Sunday Dec 17th, 2006 |
Location: | Belgium |
Posts: | 23 |
Status: |
Offline
|
back to top
|
Paul,
If the resistor value of the LDR is different, you need to replace the shunted resistor too ... I thought I even had to mount one of 50KOhm ...
If light level goes down, resistance gets higher ... With that in mind, adjust that resistor ...
Kind regards,
Bart
|
Posted: Wednesday Feb 28th, 2007 02:46 pm |
|
16th Post |
Pgordon
Member
back to top
|
Hi Bart,
Whilst I don't pretend to actually "understand" the relationship between the LDR, the internal resistor, and the trimmer, I was made aware of the need to match the value of the internal resistor to that of the LDR... the 20K value was recommended as the "right" match for the particular LDR that I ordered from CPC...
Paul G.
|
Posted: Wednesday Feb 28th, 2007 07:35 pm |
|
17th Post |
on4cet
Member
Joined: | Sunday Dec 17th, 2006 |
Location: | Belgium |
Posts: | 23 |
Status: |
Offline
|
back to top
|
Hi Paul,
It may seem strange, but I had to mount a 50 K resistor, although my LDR measured about 20K at normal light conditions ...
And I thought I read somewhere that the resistor should be equal to the LDR (at normal light conditions) when talking about the resistance, so, normally I had to put a 20K resistor in, just like you, but couldn't get the LED on at dusk, so just went to 50K and all went fine ...
I'm sure you'll work this out Paul !
Kind regards,
Bart
|
Posted: Thursday Mar 1st, 2007 07:21 am |
|
18th Post |
ident
Administrator
Joined: | Wednesday Aug 9th, 2006 |
Location: | Singapore |
Posts: | 3493 |
Status: |
Offline
|
back to top
|
Here is some insight as to the sensor and the resistor that is needed
The resistor value should be roughly matched to the sensor that is used. To do this you should measure the resistance of the sensor ( Light dependent Resistor) at about the time where the threhsold is set (normally dusk or dawn). Hence if the LDR resistance is 50K use the nearest resistor value (47K or 51K)
The effect of the series resistor is important for sensitivity. The larger the value of the reisistance relative to the LDR, the less sensitive the sensor will be, and vice versa
This could be an important factor as users may be using different sensors and resistors supplied by CHC
If the sensor is too sensitive, then small changes in light level will cause large changes in voltage relative to the threshold and the hysteresis. The fixed hysteresis would have little effect
hence a solution to oversensitivity would be too use a larger value of series resistor, which would allow the hysteresis to have a greater effect
This could account for different experiences of users regarding multiple switching around the threshold conditions
Pointing the sensor away from direct light is also important
The LSM manual will be updated to include more guidance
The LDR that we supply can be found in Farnell part number 7482280
Last edited on Sunday Apr 1st, 2007 02:35 am by ident
|
Posted: Thursday Mar 1st, 2007 03:16 pm |
|
19th Post |
palmlodge
Member
Joined: | Thursday Dec 14th, 2006 |
Location: | United Kingdom |
Posts: | 507 |
Status: |
Offline
|
back to top
|
ident
Thats certainly not the photocell that Comfort Uk are dishing out. This may explain the issues.
Could you recommend some part numbers for a 20k, 22k, and 50k resistor from farnell ?
I'll order those and give that a go.
|
Posted: Thursday Mar 1st, 2007 05:27 pm |
|
20th Post |
Comfort Home Controls
Member
Joined: | Tuesday Dec 5th, 2006 |
Location: | United Kingdom |
Posts: | 2 |
Status: |
Offline
|
back to top
|
Hi Gareth
The LSM01 we sent out to you has the Cytech/Farnell LDR and not the CPC version we have been using as a replacement (which incidentally, works fine for last few years with everyone elses systems).
I had advised you to default the system to prove if the problem was due to the ccl file, how did that go?
Also, the alluminium conversion brackets for G1 to G2 DO NOT cause any bridging of the 0v to the PCB track, they are isolated from the PCB tracking and should not cause a problem.
Andrew Roberts
Comfort Home Controls
http://www.home-control.co.uk
|
Current time is 10:19 am | Page: 1 2 |
|