I guess something I would really like to know is short comings of WebCTRL, and any problems that people have run into with ALC products in general?
Greetings..
Just finished up a BSE in Mechanical Engineering and started working for an ALC dealer. I did not ever study anything specific to HVAC (aside from a couple thermodynamic courses) so I have much to learn. I was just wondering if anyone/someone/everyone could send me some useful thoughts/ideas regarding ALC products. I do not need links sent to me as learning tutorials, I was just hoping to gather ALC specific information as I am going to try the technical sales avenue of ALC. That being said, I have watched a months worth of training videos, as well as WebCTRL tutorials so I am pretty well versed in the basics.
Any advice, or wise ass comments, would be great. I am flying to Georgia for the ALC training program next month, so if anyone could throw some good bars in the area - that would also be of great help.
Thanks.
I guess something I would really like to know is short comings of WebCTRL, and any problems that people have run into with ALC products in general?
If you are a visual learner like I am you will love working on the system, there is very little command line work that needs to be done manual commands aside.
As I understand it there is a support forum for ALC reps filled with good info. I can't get in there myself but you should be able to, just get in there and start reading.
Some training or background on BACnet would be a huge benefit, most of mine was through trial and error plus research on my own time. As that's the backbone of the system some knowledge here goes a long way. Next would be some modbus training too.
I don't like to run into an old CMnet segement too much but hopefully there aren't a lot left, and god forbid you actually run into a supervision front end. They are vastly different and much more complicated than what exists now.
If you see Kevin or Laurin tell them Scott from Liebert says hi.
Max,
I appreciate the knowledge. I have been doing as much digging/research on anything that I believe is related to the systems I am working with as I can. In my undergrad I spend a lot of time with automation controls, so I try to compare what I have done with PLC's to much of what is being doing using ALC controls/controllers.
I agree with you 100% on the ModBus training, this is something that I know very little about and have not been able to find a whole lot that I can make sense of. I am trying to go on as many service calls as possible (with a 'veteran of the ring') in order to grasp this concept better.
Once again, thanks.
If you are interested in the nuts and bolts of modbus, you can always read the protocol specification document. It's actually a fairly easy read since it's only 51 pages long.
It can be downloaded for free here: Modbus Protocol
Be aware of the BACnet MSTP limitation with ALC and third party BACnet devices that have more then 200 objects. I end up using other software to discover and document third party BACnet devices before I integrate them into a WebCTRL front end.
There are also issues of schedules in WebCTRL GUI not updating when changed by third party BACnet front ends. The schedule in the controller will update but the changes will not be displayed in WebCTRL. I have not been able to see if over any extended period of time WebCTRL gives a parameter mismatch and request and upload or download, one day when I have some more time.
Just be aware that WebCTRL can be a great BACnet AWS for multiple vendors controllers but there are some "gotchas", don't go into a potential customer and promise them the world with integration before you have really done your background work. Talk to your top technical/program guys and ask them if it can be done or even better to a test and verify interoperability before you sell it. ACL has a ton of third party drivers as well as MODbus, LON and BACnet, so if it something off the wall check on the support site they might have a driver.
The ALC lighting controls is pretty new and acceptable for commercial/industrial lighting but their dimming capabilities are nonexistent at this stage. Good to sell a packaged job with HVAC but I don't think it would stand up against a dedicated lighting system one for one.
Now get out there and sell.
kontrol out
"Good" - Jocko
"Open is as open does." - Forrest Gump
"Can't we all just get a Lon?" - Garry Jack
"BACnet: integration or interrogation?" - The Janitor
"Interoperability? You can't handle interoperability!" - Nathan R. Jessup
“What’s that? Aaa… open protocols? Don’t talk about…. open protocols? Are you kidding me? Open protocols? I just hope we can hardwire an interface!” - Jim Mora Watch it here!
KP-
I hope you do not mind if I bounce questions regarding some of these things off of you once in awhile..it seems you are are the 'Zen-Master' of DDC in this forum; so I could see a benefit in that. I was on a service call yesterday where a customer wanted to know if there was any way that they could change a setpoint in a zone, and have it be reset to the original schedule, without the use of a RS-Plus sensor. I thought that there would be a way to do this in the logic, but realized that if that change was made it would, in essence, 'embed' this value (in the sense that it would not reset when the schedule changed). I do not know how well I described my scenario, but was wondering if you knew any tricks around this (beside telling him to switch from a basic to a plus!!).
Also, I have concluded that without the cooperation of the third party you are attempting to integrate with, that this process is a REAL headache.
Not true on a couple of points: I am no zen master, I leave that stuff for Phil and the boys. TPI can be a PTA without the right tools, but with a little knowledge and the right tools it is actually fun!
The schedule/setpoint could be done with a switch block between two analog variables being latched if there is a change that is reset by the schedule and a not block?
kontrol out
"Good" - Jocko
"Open is as open does." - Forrest Gump
"Can't we all just get a Lon?" - Garry Jack
"BACnet: integration or interrogation?" - The Janitor
"Interoperability? You can't handle interoperability!" - Nathan R. Jessup
“What’s that? Aaa… open protocols? Don’t talk about…. open protocols? Are you kidding me? Open protocols? I just hope we can hardwire an interface!” - Jim Mora Watch it here!
The problem with me and TPI is that I am not really able to 'get my hands dirty' with this type of stuff right now. This is the reason I try to latch on to the service calls so that I can get out there and see the applications of all the stuff that I am watching on these videos (hah).
Once you get access to the ALC website, use the discussion forums and don't be afraid to ask questions. Several guys on there are very knowledgable and are usually very helpful. No question is stupid - we all have to start somewhere ( I am still learning!)
I have had a heck of a time just wrapping my arms around all of the different lingo and acronyms that are associated with this business.
The ALC dealer site has been a nice place to take in some literature and see some problems that other ALC dealers have experienced.