PDA

View Full Version : Mitsi Vrf 6600 fault code



moondawn
01-02-2012, 07:00 PM
hi all, have 3 systems which are hooked to one g50 controller. i have 6600 fault codes appearing on the g50 bringing the g50 into fault.

i have 1 6600 fault on one condensor 1 on another condensor and 4 on another condensor so all three vrfs are faulting with this.

i know 6600 to be multiple address problems

up to now i have took data from the g50 group settings and took data from refrigerant monitor on the g50 all checking out okay apart from a wall mounted unit add 011 has a controller 11. this is not on the g50 so have now imputed it.

on the outdoor condensors checked dsw dips switches for the outdoor to cycle through and tell me all the fan coils on the system all the remotes and bcs.

having got this data i can not notice any duplicate addresses, so now decided to verify the address by going round to each fan coil and noting them down. ie address number port number remote controller number.
I tried as fitted drawings but they are all to pot.

if after doing this and they all set correctly no duplicates which i feel it will turn out to be what would be the next step?

cheers

icemanpaj
01-02-2012, 08:00 PM
Isn't the G50 showing which unit has the error in Malfunction Monitor. eg, unit 001-6600 (detected at 001)
It's just that I've been having these 6600 + 6607 a lot at work after taking over a new site and the G50's that I have tell me which unit address is the problem, then I just go hunting for the other unit.

stufus
01-02-2012, 08:00 PM
First up are the systems addressed consecutively ,No overlaps on address'
The fault should read out as "6600 - 001 ,101 etc.
You could have a ghost address on a controller , as in the controller was assigned to a different address at some stage and the original address is still stored in it , it can be deleted most of the time but on occasion I have had to change the controller .
The other big one for causing this is interference or noise on the transmission line .
Try a virgin reset on each system and reboot the g-50
Cheers
Stu

moondawn
01-02-2012, 08:32 PM
hi ice man yeah on the g50 it identifys which ones are faulting 6600 for example i am getting the following

system 1
004-6600

System 2
013-6600

System 3
021-6600
022-6600
026-6600
027-6600

unfortunalty i do not have a drawing to hand with all the addresses so will have to verify the address are right at the units. from the information i have looked at i cant see anything out the ordinary.

Stufus - hiya mate, i thought ghost addresses were more 6607 fault codes but defo think that this could be the possibility.
is there a way to interogate the systems remote controllers say by plugging in a par 27 or using a par 27 thats already coneected to the m-net to look for ghost addresess??

the systems are as follows i cant see anything wrong here but worth posting so that it can be confirmed it looks right
SYSTEM 1
OC51
Bc 52
IFC 1,2,3,4,5,6,7,8,9
RC 101,102,103,104,107,108,109.

SYSTEM 2
OC60
BC61
IFC 10,11,12,13,14,15,16,17,18,19.
RC 111,115,116,118

SYSTEM 3
OC 71
BC 72
IFC 20,21,22,23,24,25,26,27.
RC 121,122,125,126.

TO ADD I FOUND ADDRESS 11 Has a wall controller addressed 11 at the controller. this was not entered in the g50 it now has been. this alone would not cause the problems we having though and address 11 is not a 6600 fault on the history.
System 3 should that be lowest indoor 20 = 50 is 70? i have 71. is this wrong?

stufus
01-02-2012, 09:02 PM
Don't follow you on the last line.
But the system address' are fine as they are
Yes you can interrogate the system with a par 27 it's easy enough ,it's page 51-54 in the manual I think.
Double check the rotary switches on the back of the controllers people often leave them halfway between digits.
https://rapidshare.com/#!download|654|2601380314|sh_city_multi_y_r2.pdf|2432
A (https://rapidshare.com/#!download|654|2601380314|sh_city_multi_y_r2.pdf|2432) lot of the time I dont assign the controllers to the G50 because it can cause these problems,doesn't affect operation.
Cheers
Stu

moondawn
01-02-2012, 09:12 PM
hi stufus cheers, i thought with addressing units its the lowest indoor fan coil unit on that system then add 50 that gives you the outdoor condesnor number. on the 3rd system lowest indoor is 20 =50 should that not be 70
whereas its set to 71?

will have a look and see if can check through them gives me a next plan of attack. i know from history that these systems have had this problem for a long time on this site its not like its just happened so gonna check through every fan coil i can to elimate multiple addresses even though it does not look likely!

icemanpaj
01-02-2012, 09:17 PM
Yeah I think a walk around is in order. As you said just to eliminate any possibilities.. And then a SW2/2 / Virgin restart. just to start from scratch and know what's what.

stufus
01-02-2012, 09:24 PM
Now I get you .
Depends on who's doing it some people count the BC as a digit as well.
Outdoor address (51) plus no of indoors on system (9) plus BC (1) = 61 and so on but in reality as long as you don't overlap you're good to go.
Cheers
Stu

moondawn
01-02-2012, 09:38 PM
okay cheers guys will update as i go along.

stufus
01-02-2012, 09:42 PM
Oh yeah almost forgot,
COYB !! Go on the Toffees
Cheers
Stu

moondawn
01-02-2012, 09:48 PM
stu thats really not helping. we having a bad time at the moment. really bad but funnily enough we still top!!!!!!

stufus
01-02-2012, 09:52 PM
Consistently average will do us.
Your lot are fooked at the back without Kompany
Cheers
Stu

JoeAT50A
02-02-2012, 03:41 AM
Hi moondawn,

There are a lot of groupings in your system.

Please make sure to have outdoor unit SW2-1 "ON" position for all three systems.
SW2-2 ON >> virgin fresh start/reset>>
Reconfigure all the groups at G-50A manually and carefully on grouping.
You could able to check the registrations of IFCs at your remote via engineering mode. (Filter button +Lover double arrow button)

SYSTEM 1
OC51
Bc 52
IFC 1,2,3,4,5,6,7,8,9
RC 101,102,103,104,107,108,109.
Group1 101 >>01 : Group2 102 >>02: Group3 103>>03:
Group4 104 >>04, 05 and 06
Group5 107 >>07 : Group6 108 >> 08: Group7 109>>09 and 10

SYSTEM 2
OC60
BC61
IFC 10,11,12,13,14,15,16,17,18,19.
RC 111,115,116,118
Group8 111 >>11,12,13,14 : Group9 115 >>15: Group10 116>>16,17:
Group11 118>>18,19 and 20:

SYSTEM 3
OC 71 (*no problem with 71 instead of 70)
BC 72
IFC 20,21,22,23,24,25,26,27.
RC 121,122,125,126.
Group12 121 >>21:
Group13 122>>22,23 and 24:
Group14 125>>25:
Group15 126>>26 and 27:

6600 error is strange for me, should be most likely 6607 some time 6603.

stufus
02-02-2012, 09:35 PM
That's all well and good Joe@50A ,but just because a controller is not assigned to a unit address does not mean that unit is controlled by the previous lower controller address.
It is possible to have units connected with no controller and use the G50 only.
6607 and 6603 are transmission send/receive errors.
6600 is multiple address errors ,One or more IC,BC,OC,RC with the same address.
Cheers
Stu

moondawn
02-02-2012, 10:42 PM
hi joe thanks for your reply. as i understand it i feel stufus is correct in for instance if i have address 1, 2, 3, 4.
if i only have 1 controller assigned to address 1 then it will not have command of unit 2 which could be in a totally different area to address unit 1.

defo cleared up that 0c 71 is fine which is good as i thought that did not seem right.

cheers

JoeAT50A
03-02-2012, 02:33 AM
Hi Moondawn,

SW2-1 OFF >> Grouping done via outdoor micro processor via manual registration from remote controller.

SW2-1 ON >> Grouping cum registration done via G-50.

SW 2-2 ON + with SW 2-1 ON (virgin reset) >> Grouping decided based on G-50A configuration
SW 2-2 ON + with SW 2-1 OFF (virgin reset) >> Grouping decided based on manual registration from remote controllers.

We want you to have let G-50A handle everthing, please do not group or register manually again from remote controller via engineer mode.

marc5180
03-02-2012, 07:58 PM
Hi, i went over to site today to give Lee a hand.

As Lee said theres so many duplicate address errors.

I connected my monitoring tool and checked through connected info and could find nothing duplicated. No RC, BC box or addresses were duplicated.
We then checked every indoor unit to find what was linked to it by using the par27 and going into the engineers mode.....again nothing duplicated.

I expected to find a duplicate RC address somewhere but nothing.

On the outdoor SW2-1 was on.

This is definatly a strange one.

stufus
03-02-2012, 11:06 PM
The monitoring tool will not detect a ghost address because it is not permanently present in the control logic .
Delete all controllers from the systems both physically and electronically.
By physically ,I mean disconnect the cables,
Reset the system and add the controllers one at a time ,resetting each time ,until it alarms again.
As i said above you may have to replace a few controllers.
Mitsubishi will tell you this is not possible ,send the controllers back to them and they will go quite!!!!
Cheers
Stu

stufus
03-02-2012, 11:18 PM
Almost forgot..
Register on the Mitsu website and download the G50 update and install it.
Could be some twat was chopping and changing and the G50 gave up trying to keep up.
Cheers
Stu

marc5180
04-02-2012, 06:29 PM
Thanks for the advice Stufus.

Bit of an update, we were back at site today witht he hope of carrying out a VR, however we were unable to do this because 2 indoor units had no fuse spares with access for us to switch off.
Hopefully this will be fixed in the next few days.

I connected the laptop earlier checking adress settings and port settings etc and when i went to click on OC 51 the laptop brought an error up saying unable to find BC 52.
Once on the monitoring screen all the info for system 51 outdoor and indoor was there but it didnt even show the BC box or any sensors or LEVs etc.

Then i clicked on error history page for address 71 and
there were several duplicate addresses as shown in the picture below ( sorry about the quality) but once i clicked off and back on, they were gone again.

We intend on carrying out a VR but the only problem with disconnecting the controllers is the fault doesnt happen all the time. Sometimes it might not happen for a few days so it would be a nightmare having to call back to site every few days to check if the system has faulted and if not then put 1 controller on at a time but is this the only way?

install monkey
04-02-2012, 06:58 PM
couldnt you just drop the ring main for the indoors-saves getting the ladders out?

Thanks for the advice Stufus.

Bit of an update, we were back at site today witht he hope of carrying out a VR, however we were unable to do this because 2 indoor units had no fuse spares with access for us to switch off.
Hopefully this will be fixed in the next few days.

I connected the laptop earlier checking adress settings and port settings etc and when i went to click on OC 51 the laptop brought an error up saying unable to find BC 52.
Once on the monitoring screen all the info for system 51 outdoor and indoor was there but it didnt even show the BC box or any sensors or LEVs etc.

Then i clicked on error history page for address 71 and
there were several duplicate addresses as shown in the picture below ( sorry about the quality) but once i clicked off and back on, they were gone again.

We intend on carrying out a VR but the only problem with disconnecting the controllers is the fault doesnt happen all the time. Sometimes it might not happen for a few days so it would be a nightmare having to call back to site every few days to check if the system has faulted and if not then put 1 controller on at a time but is this the only way?

stufus
04-02-2012, 07:13 PM
You don't have to power down the indoors to perform a reset or disconnect them as they are feed on the 30v trans circuit.
But looking at that screen shot ,I'd be leaning towards interference on the trans circuit.
A serious pain to pin down , gonna have to check connections on all units ,with shield continuous throughout but only terminated at the outdoor.
All the usual suspects h/v cables , light fittings ,lifts.
You could try putting a small value resistor across the m-net terminals to deaden the interference.
But thats the direction I'd be heading in.
Cheers
Stu

marc5180
04-02-2012, 07:22 PM
couldnt you just drop the ring main for the indoors-saves getting the ladders out?

If only it was that easy mate. There not on a ring main but are spread out over 3 floors and 6 boards and 2 of the units we can't find the mcbs in any of the panels because there not labelled very well.

stufus
04-02-2012, 07:25 PM
Roughly how long is the trans line on each system and how big is the trans cable.
Cheers
Stu

If only it was that easy mate. There not on a ring main but are spread out over 3 floors and 6 boards and 2 of the units we can't find the mcbs in any of the panels because there not labelled very well.

marc5180
04-02-2012, 07:29 PM
You don't have to switch power off to perform a reset? I always thought you did. Not sure why though because as you say the 240v has nothing to do with the mnet line.

We've never come across interference before on a transmission line at least not to this extent.

Can you use an oscilloscope or something to listen for noise and would this help in this instance do you think?

stufus
04-02-2012, 07:48 PM
You only need to power down the control circuit which is the 30v ,so outdoor only will do the trick .
If you know how to use an oscillithingy yes I suppose you could,I've not got a clue never used one.
I have had problems before and after exhausting all avenues put them down to noise ,a complete sweep of all trans connections and in some cases replacing the cable (undersized)has sorted it out.
The length of the run plays a part for obvious reasons , signal boosters/amps are available but never had to use one.
Cheers
Stu

marc5180
09-02-2012, 07:14 PM
An update to the thread.

We now have access to each indoor and today carried out a Vigin Restart.
As soon as we powered everything back up the 6600 fault appeared within a few mins.

We deleted the remote controller adresses from the G50a and the remote controllers themselves and disconnected the controller cables like you said Stufus.

After leaving it for 30 mins, went back and found the 6600 fault had appeared again.

Next we disconnected the centralized controller from TB7 on all the outoor condensers with the hope of running each outdoor independently thinking this may narrow down on which system we have the fault.

Only problem is with TB7 disconnected we got a 6607 error which causes the indoors to knock off.

Not to sure if a dip switch may need changing or even CN41 needs moving if there is no centralized control???

In the end i connected TB7 back in to the master outdoor but it would only let me run that 1 outdoor and 9 indoors without throwing a fault up so i've left it like that overnight hoping when i return in the morning i should know if that system has the 6600 fault or not.

One thing we did notice is the sheathing on the outdoors are connected but none of the indoor or BC box sheath are connected to the sheathing point.
It should be though shouldn't it?

stufus
09-02-2012, 09:18 PM
The shield does not have to be terminated at each indoor as the terminal is a blank ,doesn't connect to any thing ,it's only for linking the shield cable ,as long as the shield is continuous and well connected at the outdoor.
Check your PM Marc
Cheers
Stu