Post a reply to the thread: ALC System replacement top 5 reasons
You may choose an icon for your message from this list
Please enter the name by which you would like to log-in and be known on this site.
Please enter a password for your user account. Note that passwords are case-sensitive.
Please enter a valid email address for yourself.
Will turn www.example.com into [URL]http://www.example.com[/URL].
Not reading everything here but yes, a CMnet system is a really good canidate for total replacement. Mind the modules that can be upgraded though, some can. Best reason for going with another vendor would be if you had no dealer support, can't easily and quickly get replacement or new hardware or technical answers sinks the whole thing.
Originally Posted by kontrolphreak X, I decided not to feed the troll. kontrol out I'm with ya, I'm just wanting to see the fur fly!
X, I decided not to feed the troll. kontrol out
Originally Posted by fixitman We can thank ALC for demonstrating to us why that's not such a great idea. I'm not following you on this one. So what wasn't a good idea?
It was a UNI32. Haven't tried it for a couple of years. I think a have it still floating around and an old S card. Will attempt again one day. kontrol out
Originally Posted by kontrolphreak BACnet/MSTP? I thought the old controllers (other then U-Cards) were either BACnet/ARC156 or CMnet. I have tried to add a controller configured to CMnet 38.4Kbs to a BACnet 38.4Kbs MSTP network and it crashed the whole network, so I assumed that CMnet is not MSTP. The 2MB LGE can be MSTP (ARC156/MSTP printed right on the controller) but the rest of the older controllers have ARC156/CMnet printed on the board. kontrol out. What control did you have an issue with? I can't think of one until your back to exec 4.
Originally Posted by control$ The old S,M,UNI,LGR,LGE all support MS/TP. The exec 4 Devices do not, but hell bacnet wasn't invented at that time. BACnet/MSTP? I thought the old controllers (other then U-Cards) were either BACnet/ARC156 or CMnet. I have tried to add a controller configured to CMnet 38.4Kbs to a BACnet 38.4Kbs MSTP network and it crashed the whole network, so I assumed that CMnet is not MSTP. The 2MB LGE can be MSTP (ARC156/MSTP printed right on the controller) but the rest of the older controllers have ARC156/CMnet printed on the board. kontrol out.
Originally Posted by Turnipblood ALC dealers cannot cross territories on installations BUT they can do other work (parts, engineering, etc) I have been told so that might be an option.. Well...we have done a few sites that is in other dealers area's. One site requested someone other than them. They contacted our office and we worked it out with that "other" dealer for their new addition. For another customer ,we flew a guy to Florida (not in our state). Also ALC has a module called equipment portal ( http://www.automatedlogic.com/files/.../cseqprtl.pdf/ ) that can communicate over mostly anything. They are about the same price as a ZN551. That might be an option also. Right now the only thing that the EQ-PRTL can talk is Modbus and LON.
Originally Posted by kontrolphreak Only issue is that older generation (S/UNI/M/LGR) only do ARC156 or CMnet. Yes on current generation (SE/ZN/ME/LGR) you can set them up as MSTP, but this is no help for the OP. Also doing this MSTP/ARC156 conversion after the initial install would entail taking all the controllers off the network, set jumpers at each controller (those VAV boxes will be fun), change the network type in Sitebuilder then reconnect all the controllers. I don't feel that many if any non-ALC technician/programmers could accomplish this without some hiccups. If we get this moved to Pro I could add some more "issues", but not happening out here. kontrol out Originally Posted by fixitman There was once a lot of bragging among BACnet advocates - aimed at Lon - about how BACnet packets could be transported via various and sundry network protocols. We can thank ALC for demonstrating to us why that's not such a great idea. ???!
There was once a lot of bragging among BACnet advocates - aimed at Lon - about how BACnet packets could be transported via various and sundry network protocols. We can thank ALC for demonstrating to us why that's not such a great idea.
ALC legacy conversions to WebCRTL can get slightly glitchy sometimes especially when you want to edit the logic. I do know that running a BACnet/MSTP device on a BACnet/ARC156 network will drag the comm down. ALC is proud of their stuff price-wise but I have modules that have not seen daylight in 18 years and never had a problem with a majority of them until a UNI goes down and then you lose a whole wing. Also replacing UNI 59's with UNI32's eases the problem a little but not much. ALC dealers cannot cross territories on installations BUT they can do other work (parts, engineering, etc) I have been told so that might be an option. Also ALC has a module called equipment portal ( http://www.automatedlogic.com/files/.../cseqprtl.pdf/ ) that can communicate over mostly anything. They are about the same price as a ZN551. That might be an option also.
Thanks for the reply Atticus. 1, The customer pays for the entire control system. I'm not saying they should be able to write the code that runs the program itself. That is intelectual property. I'm saying they should be able to change setpoints, alter PIDs and view any point on the system. They paid for that. 2, If I buy a smart phone, I expect to be able to program my own brother's or friend's number and personal infor into it without having to pay tech support $$$/hr to do it for me. This is not changing the internal programming, simply makking it easier for me to use. My 2 cents.
Originally Posted by dracula Xarralu, Are the new ALC module drivers packaged with WC5.2 or 5.5 or 5.6? They came out with these drivers after 5.5 came out, so I am going to assume that they will come out with 5.6 Have you tried using them with WC3.0 or WC4.1spB systems? No I personally haven't, but according to the ALC dealer site it's backwards compatible. (See Screenshot below) Attachment 319631 I still have clients with older systems that don't have the funds to upgrade yet due to the tight economy, and are trying to keep there controls going until they can afford to start upgrading. I noticed mention of a P10 module, what about the old 88h drivers? Old stuff is still kickin'. I've had so many sites say if it still works, why replace it. I fore warn them that if it does finally go out there is no direct replacement, so just get ready. I wonder if the newer BACnet control specs hitting the street that exclude any BACnet product line that "locks" out BACnet points, and controllers, from being accessed by the owner or "owner's selected representative" are starting to have an impact at the manufacturers "C-Level" decision makers. ALC has made a very smart strategic move with these changes. Yea, it's been a long time coming and I'm glad they finally let ALC branded equipment loose. They have had it for quite some time with their OEM versions but for some reason ALC dealer equipment is last on the list to get let go of.
Good to hear about the ALC equipment being truly BACnet MS/TP compatible now (with the proper drivers loaded). That is a very positive development in my opinion.
The old S,M,UNI,LGR,LGE all support MS/TP. The exec 4 Devices do not, but hell bacnet wasn't invented at that time.
New Drivers for WebCTRL ALC Modules? Xarralu, Are the new ALC module drivers packaged with WC5.2 or 5.5 or 5.6? Have you tried using them with WC3.0 or WC4.1spB systems? I still have clients with older systems that don't have the funds to upgrade yet due to the tight economy, and are trying to keep there controls going until they can afford to start upgrading. I noticed mention of a P10 module, what about the old 88h drivers? I wonder if the newer BACnet control specs hitting the street that exclude any BACnet product line that "locks" out BACnet points, and controllers, from being accessed by the owner or "owner's selected representative" are starting to have an impact at the manufacturers "C-Level" decision makers. ALC has made a very smart strategic move with these changes.
New Drivers for WebCTRL ALC Modules?
No. I haven't heard anything about it coming down the pipeline yet
Originally Posted by xarralu Attachment 319181Attachment 319191Attachment 319201Since everyone wants proof. I have connected an ALC ZN 551 directly to a JCI-NAE via MS/TP by (oh my gosh!) moving a jumper to MS/TP on the ZN. It's running at 38.4 and was able to discover it in the NAE. It's been a long time coming, but they finally did it. To see an ALC module talking directly to a NAE via MS/TP is...awesome Welcome to the 21st Century! This is one if not the biggest improvements ALC has made with their controllers since they made them MSTP configurable, no more *****ing about no programs in AMR, no more *****ing that ALC controllers were not third party BACnet peer-to-peer controllers (other then LGR). And with the improvements they have made in their software I would say they are the leaders of the pack in the BACnet world. kontrol out
Have the finally made the stpt microblock BACnet? kontrol out
Yeah. Just saw the result. First game I every went to was NZ v Aus in 88 and we drew them then too! First time in like for ever that they hadn't beat us. Charged the field at the end as a grade 10 schoolboy and said hey to the Aussies! When I saw your post I hadn't seen the result and was hoping beyond hope for the win, but I'll take the draw. kontrol out
Forum Rules