michaelfish wrote:Let us know if you find a solution (and what the solution is) for RS-422 to work with PCs and the EVI-D70. I worked on it for over a week and even purchased an RS-422 board for the computer. No luck so I ended up purchasing the Sony RM-BR300 remote. It was expensive but solved all problems and works like a dream.
@michaelfish,
I did figure it out last night! I still have all the stuff here until today so I decided to solve the problem now.
Actually I was facing a number of problems. Some I should have known ("duh" type problems) and others were difficult. Here is my dissertation/work log to figure this out. If I was more systematic in my troubleshooting and read more documentation I could have figured it out much quicker I believe.[INDENT]
1) Dip Switch: There is a 4 position dip switch on the bottom of the camera that determines the communication type. Switch #3 is the communication type (232 or 422). Be sure to set it to 422 :p (duh!) Oh, don't forget to power cycle the camera or the change won't take effect.
2) Drivers: Getting the right drivers for the USB to RS422 adapter for WinXP and Win7. I didn't know who the manufacturer was on the adapter. There were no ID marks or anything on the adapter itself. I actually Googled "USB to RS422" and found one that looked just like the one I had. It turned out to be from
Startech. From their website I was able to get the right drivers, and the pin-out documentation which was a big help.
3) Bad Couplers: The cables that I received from HQ in Riverton had these RJ45 couplers that were then attached to a short length of CAT5e then to the green alligator-jaw connectors. This was to enable essentially any length of control cable to be "created" with the appropriate length of a patch cord. Problem here? The LAN couplers had intermittent connection problems AND one of the daisy chain cables also had a bad RJ45 clip on it. My solution (I am making these myself next time) will to be eliminate the couplers and use an RJ45 female jack and wire that to the CAT5e...a solid and reliable connection.
4) Adapters Going "Offline": The USB to RS422 adapters would need to be reset after a failed test. Meaning, while I was reconfiguring and moving stuff around and doing, "does this work?" tests, the adapters would go "offline" so to speak. I would have to unplug and re-insert to reset them. I didn't know this and this was cause for more headaches and time spent trying solutions that may have worked because the adapter was "offline".
5) Different Pin Configs:The D-Sub 9-Pin to RJ45 adapters were different pin configurations. I actually received two USB to RS422 adapters (long story here). They both had D-Sub 9-Pin to RJ45 converters attached to them and turns out they were different pin configurations! One is an RS232 to RJ45 adapter after ohm-ing out the device. I assumed that they were both for RS422...oops! :rolleyes:
6) Wiring Protocol: This next problem was more my lack of experience with RS422 communication protocols than it was an actual problem, but once the first problem occurred I began to question the pinouts and wiring. After much trial and error I couldn't get any movement. Then based on what I knew of RS232 protocols and a whim, I decided to connect TxD+ to RxD-, TxD- to RxD+, RxD+ to TxD-, and RxD- to TxD+ (rather than what is normally done). This was only from the
controller to the VISCA connection on the
first camera and
BAM! the camera took off. Though, I still couldn't get the second camera in the daisy chain to work.
I Googled some info on this and I discovered that the "controller", depending on the controller, needs to be wired differently. I got a Sony schematic/diagram showing how an RM-B300 controller needs to be wired to the VISCA chain. I wired the RS422 adapter according to this. Now the 1st camera stopped responding, aaargh.

So I put the configuration back to where the 1st camera was working, then rewired the other according to the diagram from Sony. And that did the trick! All cameras are now recognized and functioning.
[/INDENT]All in all it was a good learning experience. Probably more to hone my troubleshooting skills than anything else.
I hope this helps someone else that is trying to get this to work.
If you have questions, need ideas, or diagrams let me know. I may not be able to help every situation but doing this I know I can answer some questions.
Jim B.
ID: Jimbo3san