EISY will not connect to Serial PLM 2413s

[tokenworker]

New EISY user 

I'm upgrading from 994 to EISY 
The existing PLM is working with my old 994 - PLM info/status 3c.48.85 v9E / connected

But when I connect it with a correctly wired FDTI USB cabled (pins 1 orange RX, 7Black GND, 8 yellow TX) - the eisy  PLM info/status 0.0.0 V0 / Not connected

I'm wondering if the problems I had upgrading the packages on my EISY has messaged up the OS.  I had to use SSH commands to update the packages so now I'm trying to use SSH to see the FDTI chip in the USB-Serial cable.

 

Using Putty - SSH, I see the FDTI adapter is recognized by the EISY:
ugen0.2: <FTDI USB-RS232 Cable> at usbus0
uftdi0: <FTDI USB-RS232 Cable, class 0/0, rev 2.00/6.00, addr 3> on usbus0, 
But I see the FDTI USB-RS232 UART is disconnected:
ugen0.2: <FTDI FT232R USB UART> at usbus0 (disconnected)

Should the FDTI FT232R USB UART at usbus0 be disconnected?  I've not played around enough with this system to know - nor do I really know much about this OS.  Any help is appreciated.

 

Below is the SSH session 

[admin@eisy ~]$ dmesg | grep -i usb
xhci0: <XHCI (generic) USB 3.0 controller> mem 0x6001100000-0x600110ffff at devi                       ce 20.0 on pci0
usbus0 on xhci0
usbus0: 5.0Gbps Super Speed USB v3.0
ugen0.1: <Intel XHCI root HUB> at usbus0
uhub0 on usbus0
uhub0: <Intel XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
ugen0.2: <FTDI FT232R USB UART> at usbus0
Root mount waiting for: usbus0 CAM
ugen0.3: <vendor 0x8087 product 0x0026> at usbus0
uftdi0: <FTDI FT232R USB UART, class 0/0, rev 2.00/6.00, addr 1> on usbus0
ubt0: <vendor 0x8087 product 0x0026, class 224/1, rev 2.01/0.02, addr 2> on usbu                       s0
ugen0.2: <FTDI FT232R USB UART> at usbus0 (disconnected)
ugen0.2: <FTDI USB-RS232 Cable> at usbus0
uftdi0: <FTDI USB-RS232 Cable, class 0/0, rev 2.00/6.00, addr 3> on usbus0
[admin@eisy ~]$
 

 

 

Edited Monday at 04:16 PM by tokenworker
correct plm model number

[paulbates]

I had problems connecting to my PLM when I first set my eisy up. I had to unplug/replug the PLM, wait 10 seconds, and then unplug/replug the eisy a couple of times. Then it connected and it has been fine since

[tokenworker]

I

I power cycled the EISY and PLM and moved the USB FDTI Serial cable adapter to the back USB Port of the EISY.

Now when I execute same command, I don't see "disconnected" so I'm guessing the USB ports on the EISY only check for devices during power up?  (at least I don’t see disconnected).  However, When I query the PLM using Tools->PLM status I see “0.0.0 v0 / Not Connected” 

I'm tempted to buy new PLM but this PLM still seems to communicate with my 944 box Tools->PLM status I see “3c.48.85 V9E / Connected”   So it appears the PLM is still OK.     What should I try next?  I could hook up a scope to the TX serial lines - to see if the FDTI chip is sending data or if the PLM is trying to do the same.  Thoughts?

 

Here is the 

 

[admin@eisy ~]$ dmesg | grep -i usb

xhci0: <XHCI (generic) USB 3.0 controller> mem 0x6001100000-0x600110ffff at device 20.0 on pci0

usbus0 on xhci0

usbus0: 5.0Gbps Super Speed USB v3.0

ugen0.1: <Intel XHCI root HUB> at usbus0

uhub0 on usbus0

uhub0: <Intel XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0

Root mount waiting for: usbus0 CAM

ugen0.2: <FTDI USB-RS232 Cable> at usbus0

ugen0.3: <vendor 0x8087 product 0x0026> at usbus0

uftdi0: <FTDI USB-RS232 Cable, class 0/0, rev 2.00/6.00, addr 1> on usbus0

ubt0: <vendor 0x8087 product 0x0026, class 224/1, rev 2.01/0.02, addr 2> on usbus0

Edited yesterday at 12:52 AM by tokenworker

[tokenworker]

Update - Problem Resolved.  I had two issues.

1.) The EISY seems to require a reboot - or better yet, power cycle - to recognize the USB FDTI Serial cable AND connect a serial port.  During my early attempts to connect the PLM to the EISY,  I was not power cycling after inserting the USB Serial PLM cable - and it looked like the EISY was seeing via SSH "dmesg | grep -i usb" commands but there was a message about being disconnected.  See below session with disconnected in red
 

2.) I had a DIY FDTI Serial PLM cable.  I tried to save some money, but I spent a lot more of my time and probably should have just purchased the cable from the start.  

Thanks to UD tech support for confirming my EISY was operating correctly.  Now I need to complete the migration process.  Its all downhill from here, right?  What could go wrong

 
I believe if the (disconnected) message shows in response to this command, power cycle the EISY to get it to properly set up the FDTI device and open the UART (com/serial) port.

[admin@eisy ~]$ dmesg | grep -i usb
xhci0: <XHCI (generic) USB 3.0 controller> mem 0x6001100000-0x600110ffff at devi                       ce 20.0 on pci0
usbus0 on xhci0
usbus0: 5.0Gbps Super Speed USB v3.0
ugen0.1: <Intel XHCI root HUB> at usbus0
uhub0 on usbus0
uhub0: <Intel XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0
ugen0.2: <FTDI FT232R USB UART> at usbus0
Root mount waiting for: usbus0 CAM
ugen0.3: <vendor 0x8087 product 0x0026> at usbus0
uftdi0: <FTDI FT232R USB UART, class 0/0, rev 2.00/6.00, addr 1> on usbus0
ubt0: <vendor 0x8087 product 0x0026, class 224/1, rev 2.01/0.02, addr 2> on usbu                       s0
ugen0.2: <FTDI FT232R USB UART> at usbus0 (disconnected)
ugen0.2: <FTDI USB-RS232 Cable> at usbus0
uftdi0: <FTDI USB-RS232 Cable, class 0/0, rev 2.00/6.00, addr 3> on usbus0
[admin@eisy ~]$
 

Edited yesterday at 01:47 PM by tokenworker