Installation working but cant connect Toolkit

Discussion in 'C-Bus Wired Hardware' started by chablis97, Dec 8, 2016.

  1. chablis97

    chablis97

    Joined:
    Jul 29, 2004
    Messages:
    32
    Likes Received:
    1
    Location:
    Adelaide
    Hi all
    Have a issue, hoping someone can point me at a possible fix.
    Project Details
    Residential application, one network. DIN relays, DIN dimmers, Saturn switches, eDLTs, DLT, B&W MK2 touch screen, fan controllers, movement sensors, MRA, CNI. 47 units in total. C-Bus voltage ~27.5V
    Issue
    Everything working flawlessly for years. All still working without a problem, but suddenly cannot connect to the network via Toolkit.
    Tried connecting via a CNI, USB on touch screen and USB PCI.
    Tried two different laptops.
    Tried adding burden.
    Tried removing DIN dimmers and relays with C-Bus PSU's one at a time and temporarily adding a stand alone PSU to take its place.

    When Toolkit tries to connect, it finds CNI/PCI, but cannot Identify the C-Bus project.

    Any ideas anyone?

    Thanks
    Ron
     
    Last edited by a moderator: Dec 8, 2016
    chablis97, Dec 8, 2016
    #1
  2. chablis97

    chablis97

    Joined:
    Jul 29, 2004
    Messages:
    32
    Likes Received:
    1
    Location:
    Adelaide
    Found the problem. Fault in underground C-Bus cable between house and shed. Now just have to fix it :(
     
    chablis97, Dec 8, 2016
    #2
  3. chablis97

    UK Household Automation

    Joined:
    Aug 6, 2004
    Messages:
    105
    Likes Received:
    0
    Another CNI non-connection

    I have a E5500CN that I'm trying to add to an installation. It is rather old (Mfg:6 Nov 2003).

    Someone has helpfully tried to upgrade the firmware and .COB file and I'm not sure if the correct ones have been used.

    I'm not sure which firmware & .COB files to choose on the Lantronix site.
    The options that seem appropriate on the 'Discontinued Products' page seem to be...
    UDS-10 (v5.8.0.5)
    UDS-10B (v5.8.0.1)
    UDS-10-IAP v5.2 (Std Tunnel) / v2.11 (Modbus) / v1.0 (DF1)
    (presumably I don't want the Modbus or DF1 version?...)

    But there are various Cobox files listed too...
    CoBox-DR1 (v5.2) - presumably DIN rail mounted...
    CoBox-DR1-IAP v5.2 (Std Tunnel) / v2.11 (Modbus) / v1.0 (DF1)
    CoBox-DR1-MB v1.2

    CoBox-E1M / -T1M v1.2
    CoBox-E2 / -TR2 v4.5

    CoBox-FL v5.8.0.5 - presumably Flanged mounting
    CoBox-FL-IAP v5.2 (Std Tunnel) / v2.11 (Modbus) / v1.0 (DF1)

    and last (and possibly least?)
    CoBox-Mini100 v5.8.0.1

    Which should we select?

    And IF(!!!) the firmware is correct, Why can't I perform a network scan through the CNI?
    I can open the network and see that it is running but can't DO anything with it. I'm sure I'm missing something simple but if the firmware is wrong then I probably won't get any further without rectifying the situation.

    Thanks in advance....
     
    Last edited by a moderator: Jan 9, 2017
    UK Household Automation, Jan 9, 2017
    #3
  4. chablis97

    NickD Moderator

    Joined:
    Nov 1, 2004
    Messages:
    1,427
    Likes Received:
    64
    Location:
    Adelaide
    I can't find any of the old documentation that tells me exactly which Lantronix module is in the old CNIs. All I have found is a schematic that refers to it as a "CoBox adapter board".

    I have dug one out and the sticker on it is not exactly forthcoming with helpful information either :(

    There is a number "CO-E2-22AA-PWC-R" that looks like it might be a part number and if I google this I can find a Lantronix EOL notice that refers to it as a "CoBox Micro"

    From this I would *guess* that it's the CoBox E2 firmware that you want.

    Having said that.... if it's working at all then I wouldn't mess with the firmware... there is an application note here on configuring the old CNI using the Lantronix Device Installer... can you connect to it using that?

    Nick
     
    NickD, Jan 9, 2017
    #4
  5. chablis97

    rhamer

    Joined:
    Aug 3, 2004
    Messages:
    673
    Likes Received:
    3
    Location:
    Melbourne, Australia
    There is a post here on the forum somewhere from Ashleigh to Charlie Crackle that identifies the Lantronix device in the CNI.

    You'll have to search, but you should be able to find it.

    Having said that, I'm yet to find a compelling reason to update the firmware, and it can be a bit tricky. If that part is working, I would leave it alone.

    Cheers

    Rohan
     
    rhamer, Jan 10, 2017
    #5
  6. chablis97

    znelbok

    Joined:
    Aug 3, 2004
    Messages:
    1,151
    Likes Received:
    17
    doesn't the WebUI tell you the details? Its been a long time since I pinged the CNI with a web browser.

    From memory its a UDS10, but don't take that as gospel
     
    znelbok, Jan 11, 2017
    #6
  7. chablis97

    rhamer

    Joined:
    Aug 3, 2004
    Messages:
    673
    Likes Received:
    3
    Location:
    Melbourne, Australia
    rhamer, Jan 11, 2017
    #7
  8. chablis97

    UK Household Automation

    Joined:
    Aug 6, 2004
    Messages:
    105
    Likes Received:
    0
    Thank you, thank you.

    I note your warnings regarding 'Leave it alone', but talking to the lad who last used it I'm sure he's put the wrong FW/.COB in. The webUI doesn't seem to respond correctly so I'm approaching a position of 'nothing much to lose'.

    Best regards from Blightey
     
    UK Household Automation, Jan 11, 2017
    #8
  9. chablis97

    UK Household Automation

    Joined:
    Aug 6, 2004
    Messages:
    105
    Likes Received:
    0
    UK Household Automation, Jan 11, 2017
    #9
  10. chablis97

    NickD Moderator

    Joined:
    Nov 1, 2004
    Messages:
    1,427
    Likes Received:
    64
    Location:
    Adelaide
    Glad you got it sorted.

    Just for my own understanding... where did you change the port setting? In the CNI or in Toolkit/CGate, or both?

    Just trying to understand if the problem was that 10001 just doesn't work, or whether it was just that the port setting in the device didn't match the client.

    Nick
     
    NickD, Jan 12, 2017
    #10
  11. chablis97

    Wonkey

    Joined:
    Aug 3, 2004
    Messages:
    418
    Likes Received:
    39
    Location:
    Adelaide
    Just to reflect on bit of history pre toolkit (V2) did not support CNI's so we used lantronix re-director software to allow a physical com port to be redirected to an ethernet port, to make all the components work we needed to set the CNI's port to 14000 due to the fact the re-director software (for some reason unbeknown to me) subtracted 11000 from the port number setting.
    Hence for quite a while after V2 installers still programmed CNI's with port 14000
    Colin
     
    Wonkey, Jan 13, 2017
    #11
Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.
Similar Threads

  1. Cant connect to Colour Ctouch

  2. Dimmer alive but not working

  3. Unit showing 0.5V but working fine.

  4. Wiser connection working on iPad but not iPhone

  5. C-Bus is working, but can't connect to it

  6. Local control keys stop working but remote OK

  7. I just replace a 5500NB but it still won't connect to the CBUS

Loading...