I am looking for the specs of the wire ends for the IVu usb-tkit. I wish to make up a longer cable for reaching VAV's in the ceiling and not have my laptop on top of a ladder. Any help identifying the plugs at the cable ends will be appreciated.
I assume you're looking for the connector that plugs into the Rnet ports, not the 3 pin phoenix at the adapter itself?
Yeah, I could use one of those too. I spent a bunch of time searching for that brown Rnet connector, and never found one. I know someone like Digikey will have it, just way too many options to search through. Although, from them, I did buy a bunch of male and female variants of both the small and large Phoenix connectors, they come in handy as various adapters and splitters for testing. Like a female small to male large to plug my CCN converter for NSTV in place of an iVu dongle without undoing the screws. That kind of thing.
For what you are referring to, what I ended up doing was buying some of the micro phoenix connectors, male and female, and and extending that portion of the cord instead. Under the shrink wrap is a regular screw connector, in an emergency you could just extend the cord with bacnet wire and wirenuts. Alternatively, you could extend the USB end with a male-female USB extension.
Attached is the last order for these that I made from Mouser, the part numbers should point you in the right direction. As to Phoenix connectors, the 3.81mm spacing ones are the mini-Phoenix used for Carrier Open stuff, and the 5.08 is the larger ones used for CCN stuff. The connectors that say "invert" are female connectors.
If the pin spacing is the same, that may work on the local access connector, but it's not the proper connector. Easier to make a custom cable on a 4-pin mini Phoenix than try to source that specific connector which will also require the pins and crimper and all that jazz.
The brown plug at the top of the cable actually comes off fairly easily. Use them enough under thermostats and it will happen for you. If you want, you could use those housing connectors directly to the exposed three pins at the end of the cable, and then rig up something to extend and re-glue the brown end. But honestly, the hold on the brown plug kind of sucks anyway, if you add that much weight it will likely just fall off or bend pins on the VAV.
True, the connector itself is crap and I’m pretty sure all our techs cables are broken to some extent. They even fall apart cable wise eventuality, but thats after a decent long life.
We have a few older VAV's that stop communicating and will not connect thru the stats. When that happens I have to get in the ceiling. Happens to 1 or 2 VAV's a year. Had one do it the other day which got me thinking about a longer cable again.
Ah ok. Since you have the cable I know you have Field Assistant, so are you all comfortable with the update process for individual controllers. You may have done it already, but if not you can make sure you have the latest SAL files for you laptop and then check for updates in the driver properties page. It's curious certain ones stop communicating but not all. Where are the problem ones located geographically on your comm line? When you say older do you mean the VAV Open controllers that were gray with the light blue front? For them to not talk thru the thermostat makes me think it is a program or driver problem. If you exhaust other options and are comfortable with AppLoader, I would reload the VAVs from the RNET port on the VAV itself.
Professional Member*
MaxBurn liked this post.
Reply With Quote