First timer help

[stawski88]

I have two 16 channel controllers daisy chained via an Ethernet cable. I have one connected to the light o Rama wireless module. I have the hardware utility open, and another wireless module connected to my computer through the USB485B, with latest driver from ftdi. My computer says I need to connect the controller to the com port via SC485 - is this true? My computer doesn't recognize the controllers or that anything is connected. Thanks!!

[bob]

The specific mention of an SC485 in there is just an outdated piece of information accidentally leftover from days long gone.  You can use either an SC485 or a USB485; you don't need to use an SC485.

 

We've recently changed the message so that it no longer specifically says you need an SC485, but the code with this change hasn't been released to production yet.

[stawski88]

The specific mention of an SC485 in there is just an outdated piece of information accidentally leftover from days long gone.  You can use either an SC485 or a USB485; you don't need to use an SC485.

 

We've recently changed the message so that it no longer specifically says you need an SC485, but the code with this change hasn't been released to production yet.

Thanks bob --

 

I cannot connect to my controllers though.  

 

I am running Windows 7 and have installed the most recent VCP driver for the USB485B.  When I open the hardware utility I get an error message saying the COM3 was not working properly (or something along those lines - not at the computer).  I followed the troubleshooting directions that were posted regarding the USB and com port issues (device manager, etc.) and my computer recognizes the ftdi driver.  I have a type A USB to type B USB plugged from my computer into the 485B.  I also have a Cat5 from the 485 to my Ethernet port on my CPU.  I than have another Cat5 running to one of two wireless modules from the 485.

 

The second wireless module is connected to my 16 channel controller (two power cables - can't remember exact #) via Cat5.  I have another Cat5 from that controller to another controller.

 

When I open the Utility, I can manually select the Comm 3, but I cannot get my current configuration, nor does it recognize that I have anything connected to that port - simply saying I need to connect the controller to the Serial via the mentioned cable.

 

In an effort to not have to run the Cat5 into the house, I'd love to get this working properly.  Would switching to the serial connector solve this issue, or is there something else wrong?

 

Thanks!!

Edited December 1, 2014 by stawski88

[bob]

I have a type A USB to type B USB plugged from my computer into the 485B.  I also have a Cat5 from the 485 to my Ethernet port on my CPU.  I than have another Cat5 running to one of two wireless modules from the 485.

 

 

I'm sorry, I don't think I understand this. You have a USB cable running from your computer to the USB485B, and then an ethernet cable running from the USB485B back to your computer? Is that right? Why the ethernet cable back to the computer?

 

In any case, I would try this, to try to narrow down where the issue may be:

 

Bring one (and only one) of the controllers to where the wireless module is.  Unplug the wireless module from the USB485B.  Plug the controller into the USB485B.  Unplug the other ethernet cable from the USB485B (the one leading back to your computer).  Start up the Hardware Utility, and click on "Auto Configure" (don't manually select the comm port - let it try to find it).  Does it detect the comm port? Is it able to detect the controller after that?

[k6ccc]

 

I am running Windows 7 and have installed the most recent VCP driver for the USB485B.  When I open the hardware utility I get an error message saying the COM3 was not working properly (or something along those lines - not at the computer).  I followed the troubleshooting directions that were posted regarding the USB and com port issues (device manager, etc.) and my computer recognizes the ftdi driver.  I have a type A USB to type B USB plugged from my computer into the 485B.  I also have a Cat5 from the 485 to my Ethernet port on my CPU.  I than have another Cat5 running to one of two wireless modules from the 485.

 

 

There are a couple things here that make me take notice.  The first is that you say you have a Cat-5 from one port of the USB-485B to the ethernet port on your computer.  TAKE THAT OUT IMMEDIATELY!  Although they both use the common Cat-5 cable, the LOR networking is RS-485 (a serial protocol) and NOT ethernet.  Connecting the two risks damage to one or both devices.

 

The second is that you say you are loading the driver from FTDI.  Unless the wording is odd, you should not have to get the driver from FTDI.  It should load as part of the LOR installation - it's been a couple years since I've had to do that, so I may be a little rusty on the procedure, but you should not need to load a driver from FTDI.

[stawski88]

There are a couple things here that make me take notice.  The first is that you say you have a Cat-5 from one port of the USB-485B to the ethernet port on your computer.  TAKE THAT OUT IMMEDIATELY!  Although they both use the common Cat-5 cable, the LOR networking is RS-485 (a serial protocol) and NOT ethernet.  Connecting the two risks damage to one or both devices.

 

The second is that you say you are loading the driver from FTDI.  Unless the wording is odd, you should not have to get the driver from FTDI.  It should load as part of the LOR installation - it's been a couple years since I've had to do that, so I may be a little rusty on the procedure, but you should not need to load a driver from FTDI.

 

I can see why this would be a mistake.  I will remove the Cat5 from the computer and see if this resolves the issue.  The user manual I have for the USB485B says to look for updated drivers from the FTDI website.  I installed the driver that came with the LOR, but it was not the most recent version according to the FTDI website.

 

I'm sorry, I don't think I understand this. You have a USB cable running from your computer to the USB485B, and then an ethernet cable running from the USB485B back to your computer? Is that right? Why the ethernet cable back to the computer?

 

In any case, I would try this, to try to narrow down where the issue may be:

 

Bring one (and only one) of the controllers to where the wireless module is.  Unplug the wireless module from the USB485B.  Plug the controller into the USB485B.  Unplug the other ethernet cable from the USB485B (the one leading back to your computer).  Start up the Hardware Utility, and click on "Auto Configure" (don't manually select the comm port - let it try to find it).  Does it detect the comm port? Is it able to detect the controller after that?

 

I will also try this once I get back to my house.  I'll reply once I am finished.

 

Thanks!

[stawski88]

I was able to get everything communicating and running properly.

The culprit was the Cat5 going back to the computer.

Thanks for the help!