There not cheap try Carrier.

 

If it is really CMnet we are talking about you could do a generic 485 adapter to the CMnet port I do believe.

 

Or you could buy it directly from the manufacturer and wire it directly to the RNET terminals.

http://www.silabs.com/products/interface/usbtouart/Pages/default.aspx

kontrol out

 

I think the SE6104 is still access port...the SE6104a is RNET...

 

Per the technical instructions it uses the RNET connection. I don't have one in front of me but see the attached image.

kontrol out

 

You're right...

I still get the S6104, SE6104, and the SE6104a all mixed up. Thanks man.

 

You could probably use any USB/Serial to RS485 converter. The ALC cable that connects to the local access connector only uses 3 (RNET+/RNET-/GND) connections, you could wire the converter to the RNET terminal blocks instead of the local access port, I have not tried this but I don't see why it wouldn't work.

kontrol out

 

This is an old thread, but I did this today and it worked just fine. Surprised me actually.

Make sure you hook up all 3 wires.... GND, +, and -

Remember, I said it worked, not that it was pretty....

My phone turned it on the side. Apologies felas...

 

My first question would be, if you had one what would you do with it? You need the 5 pin Rnet connector that mates with an APT or the newer style USB-L kit. Do you have the database and WebCtrl loaded and running on your laptop as a server? Without those, the connector will do you no good.

 

I concur.

 

You can "suck the program" out even when using WC4.1, but you do it while connected to the module using your laptop as a server.

How about this, connect wirelessly with your laptop or even "suck it out" onto your server? Either way, if you don't have a connection to WebClrl, I'm not aware of a way to do it.

 

It sounds like you guys may know something that I haven't heard yet. I have seen WC5.2 Beta and I spend a whole 2 minutes on it to update a licence for a customer. We actually had a seminar on it and I got called out to the field and missed it. You've got my curiousity peaked now...

 

WebCTRL 5.2 has a program you can install called field assistant. With that program you can suck program file, view file and driver out of module. I have not seen it yet but have seen the video on it that is on the dealer side of ALC site.

Also OEM customers can give out a key code to ALC dealers so they can add OEM units to the user files. It is up to the OEM customer on weather or not they give it to you.

I hope it is out in the next week or so. It is supposed to be.

If you have access to dealer site I recommend downloading the videos and watching them.

 

I wasn't aware field assistant would be able to pull out equipment files. Way I understood it was it is a (more flexible) replacement for apploader?

 

Does anyone have the pinout for the 3 pin connector on the USB-L to the 8 pin mini-din on an LGE?

 

TL;DR
I made my own USB Local Access programming cable for the Automated Logic LGE, and you can too.
Local Access port pinout: 1 transmit, 2 receive, shell ground. Signaling is TTL.

Full Story
I needed to change the IP addresses on a couple Automated Logic LGEs at my facility, but couldn't find the pinout (or any information, really) for the 8-pin mini-DIN Local Access port. I read through this thread and a couple others, and saw other people were looking for the pinout too, so I want to share what I learned, even though it's a very old post.

Based on what I read here, I had a hunch the signaling was TTL and not RS-485. I got a USB-TTL adapter from Allied Electronics (TTL-232R-5V) and a mini-DIN 8 cable to hack into a breakout. I plugged each into a breadboard with pin headers so I could use jumper wires to figure the pinout. The TTL cable appears as a virtual COM port in Windows, and I used SiteBuilder 6.1 with the baud rate set to 38400. I tried examining the LGE circuit board traces to deduce a pinout for the Local Access port, but nothing was obvious to me. In the absence of any other information, I guessed pin 1 for transmit, pin 2 for receive, the connector shell for signal ground, and.....that was it. That's the pinout. SiteBuilder loaded the module status without issue. I tried changing the IP address, and it too worked without issue. Success! I love when a plan comes together.

For all I know, this could be common knowledge to true HVAC professionals (of which I am not), but I at least wanted to post what I've learned in case it helps someone in the future looking for the same information I was.

Cheers,
C#2

 

I used to but I can't find it.

If it's a legacy CMnet exec6 module just use the white USB dongle and connect the three pins to the CMnet port of the module, make a cable with some spare comm wire. Be sure to have the ARCnet jumper in the legacy/MSTP position and match the baud rate.

 

The reason I'm trying to do this is so I can change the IP address of this controller. It is not a legacy unit, it's just a unit that doesn't have a standard Rnet port on it. I was not able to successfully change the IP address via the CMnet connection, I was hoping to be able to make a cable using the mini-din 8 pin connector so I can update the IP address using either Site Builder or PuTTy. Any other suggestions? Running WebCtrl 4.1

 

I think the part number you need then is the USB-K. The USB-L is RS485 but the USB-K is a TTL signaling level which you need for execB modules.

Do you still have the ability to communicate with the module? Over a network crossover cable maybe? The new 6.xx.xx drivers have the ability to do IP changes through WebCTRL.

 

I have webctrl 6.0, I created a new site in site builder with the new IP address. I then formatted the LGE, powered it down and back on. When it was on, the new address took effect. It appears to have worked! Thanks for the tip about the 6.0 drivers.

Scott

 

That's great you got that to work. I've only gotten the chance to use that a couple times, mostly we get the call after IT changed the IP scheme in a building and now maintenance can't see anything...

 

Scott,

Please provide a few more details on what you did. I need to change the IP on an LGE as well. You were direct connected using the CMnet port?

 

Is the module legacy Exec6 or newer ExecB BACnet?

 

I'm fairly certain ExecB

 

Any word on this Scotski79? How did you connect to the LGE? I have the RS-485 converter that I use to direct connect to LGR via RNet, and an adapter to connect to the 8-pin. Will this work, or do I need the TTL version as MaxBurn had mentioned? I'm using WC 6.0.

 

Moegilla, it must have been a fluke, or I am not sure if the actual IP address changed in my earlier post. I did end up getting a USB-K cable...you log into sitebuilder, change the configuration to match your port, 38400, etc...then you can download the new IP address to the controller. After that, I had to log into webctrl and download the new configuration to the LGE. I will test the IP connection again. I'll try the Ethernet cable again tomorrow using 6.0 to see if that actually worked or if it was a fluke.

 

Yes you can do it without the USB-K, will also need to make changes to the database if you want it to maintain communications to WebCTRL.

kontrol out

 

Its not how it looks, sometimes its did it accomplish the goal.

I work later than most the guys on-site and today was firing up a new unit that absolutely 'had' to be running today, though it could have waited weeks. Everything is all set, all equipment startup is done...yet somehow the humidifier dispersion tube drain is missing a plug and pissing water everywhere. Everyone is gone by the time I spot it, MC's crap is all locked up cannot just snag a 1" plug staring at me. Scavenge the mech room for a solution and then text a photo to the MC informing them their unit wasn't ready but we got'r'done anyway. Even a little thread seal for the bolt to go with the random reducers I found...lol. Another 50kcfm of temp & RH controlled OA coming up. How long did the humidifier startup guy run this again??

and to the fitters out there, if controls don't work for me...I'm available.

 

Looks like we need a wall of shameful pride.

:cheers:

 

There is no shame in getting it done with stupid deadlines and contractors willing to fix what's lost in the shuffle.

Shameful pride..would agree. Though its not shameful IMO, its get'r'done within acceptable limits.

 

Naw, just merging the wall of shame and the wall of pride from the HTalk website into one imaginary place that shows the accomplishment of doing the right thing, but in the ugliest way possible.

I was local support for an integrator who was out of state. I have ZERO ALC experience. He was so impressed he showed all the guys in his shop that picture because it actually worked!

 

Unfortunately you didn't have to go through that. Remove the cable that's on the Rnet buss and land there, it's electrically the same as Local Access terminal. Avoid the +12 line and generally don't even need ground to make serial menu changes. Need a RS485 converter and putty.

Remember to turn Dip switch 1 back off or things attached to Rnet/S2 won't work.

 

Remove the cable that's on the Rnet buss and land there, it's electrically the same as Local Access terminal.

Remember to turn Dip switch 1 back off or things attached to Rnet/S2 won't work.

I appreciate the tip!

I have a related question here:

https://hvac-talk.com/vbb/showthread.php?2205293-ALC-cannot-discover-routers&p=25679021#post25679021

Just keeping the thread on topic....