• Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search

    More than 1 xSxx on RS485

    Unipi Extension Modules
    5
    15
    19343
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      tomas_hora administrators @wizro_pl last edited by

      @wizro_pl and @proceau I am sorry but in some cases of the Neuron xS, there has been an issue that the firmware which we use for testing has been left there instead of reflashing to the production FW.

      If you have the USB-RS485, please use the neuron_extension_FW_tool and reflash it on your own. If not, please let us know on our email and we will reflash the unit for you if you ship it back to us.

      We are sorry for the inconveniences.

      W 1 Reply Last reply Reply Quote 0
      • W
        wizro_pl @tomas_hora last edited by

        @tomas_hora
        I didn't do it because your application is going crash after put flash button.

        Yesterday, I back to investigate and tried to flash it using fwserial without success (according to this [https://forum.unipi.technology/topic/693/multiple-xs50-on-a-l513-rs485/20](link url)).
        Also, I found out why windows application going crash because programmer do not support exception when the necessary file does not exist (!!) "E-8Di8Ro-0_P-11DiR485-1.bin"

        Here is the result from fwserial:
        root@L203-sn18:/home/pi/unipi-bin# /opt/neuron-bin/fwserial -p /dev/ttyUSB0 -PR
        Boardset: 4 E-8Di8Ro_P-11DiR485 (v1.0)
        Baseboard: 1 E-8Di8Ro (v0.2)
        Firmware: v4.9
        Modbus timeout set
        error opening firmware file "/opt/fw/E-8Di8Ro-0_P-11DiR485-1.bin"
        root@L203-sn18:/home/pi/unipi-bin#

        I've used usbconverter RS485 because I had problem with communication using buildiin RS485 in Neuron.

        I tried with "UniPian-Neuron-OS-2018-03-09.img" and also directly download from https://git.unipi.technology/UniPi/unipi-bin/fw

        There is no file "E-8Di8Ro-0_P-11DiR485-1.bin"

        Here is a search result:

        root@L203-sn18:/home/pi# find / -name "E-8Di8Ro-*.bin"
        /home/pi/unipi-bin/fwx/400-400/E-8Di8Ro-1C.bin
        /home/pi/unipi-bin/fwx/1000-2000/E-8Di8Ro-0C.bin
        /home/pi/unipi-bin/fwx/1000-2000/E-8Di8Ro-1C.bin
        /home/pi/unipi-bin/fwx/400-2000/E-8Di8Ro-1C.bin
        /home/pi/unipi-bin/fw/E-8Di8Ro-1_P-11DiR485-1.bin
        /home/pi/unipi-bin/fw/E-8Di8Ro-1C.bin
        /home/pi/unipi-bin/fw/E-8Di8Ro-1.bin
        /opt/neuron-bin/fw/E-8Di8Ro-1_P-11DiR485-1.bin
        /opt/neuron-bin/fw/E-8Di8Ro-1C.bin
        /opt/neuron-bin/fw/E-8Di8Ro-1.bin
        root@L203-sn18:/home/pi#

        file "E-8Di8Ro-1_P-11DiR485-1.bin" is not suitable.

        Martin Kudláček 1 Reply Last reply Reply Quote 0
        • Martin Kudláček
          Martin Kudláček @wizro_pl last edited by Martin Kudláček

          Hello @wizro_pl,
          please, follow these instructions:

          • download the MervisOS v1.7 image from here
          • save it to the SD card
          • put it into your PLC, start it and SSH into it (user: unipi, password: unipi.technology)
          • switch to the root user: sudo bash
          • update the packages: apt update && apt upgrade
          • reboot the unit and SSH into it again and switch to the root user
          • stop the Mervis: systemctl stop mervisrt
          • connect the extension to the RS485 port
          • run the firmware flashing: /opt/unipi-bin/fwserial -p /dev/extcomm/0/0 -PR
          • ... and post the result back here.

          Thank you for your patience,
          Martin

          W 1 Reply Last reply Reply Quote 0
          • T
            TomasKnot last edited by TomasKnot

            Hello @Martin-Kudláček @wizro_pl,

            As an addendum, if the above doesn't work, please use these commands before the last step:

            sudo bash
            cd /opt/unipi-bin/fw
            ln -s E-8Di8Ro-1_P-11DiR485-1.bin E-8Di8Ro-0_P-11DiR485-1.bin
            ln -s E-8Di8Ro-1_P-11DiR485-1.rw E-8Di8Ro-0_P-11DiR485-1.rw
            

            and then run the flashing command again, i.e.:

            sudo bash
            /opt/unipi-bin/fwserial -p /dev/extcomm/0/0 -PR
            

            It looks like this is one of the first extension boards we've sent out, and so has an older firmware with a slightly different name, apologies.

            1 Reply Last reply Reply Quote 0
            • W
              wizro_pl @Martin Kudláček last edited by wizro_pl

              @martin-kudláček said in More than 1 xSxx on RS485:

              put it into your PLC, start it and SSH into it (user: unipi, password: unipi.technology)

              How to enable SSH ? (probably by defualt is diable)\

              @TomasKnot I did change ealier and got "invalid address" or something like that.

              W 1 Reply Last reply Reply Quote 0
              • W
                wizro_pl @wizro_pl last edited by

                ok, I enabled sshd

                I did update & upgrade, reboot.

                Here is your feedback

                root@L203-sn18:/var/home/unipi# systemctl stop mervisrt
                root@L203-sn18:/var/home/unipi# /opt/unipi-bin/fwserial -p /dev/extcomm/0/0 -PR
                Boardset:     4 E-8Di8Ro_P-11DiR485            (v1.0)
                Baseboard:    1 E-8Di8Ro                       (v0.2)
                Firmware: v4.9
                Modbus timeout set
                Program mode setting failed: Illegal data address
                root@L203-sn18:/var/home/unipi# cd /opt/unipi-bin/fw
                bash: cd: /opt/unipi-bin/fw: No such file or directory
                root@L203-sn18:/var/home/unipi# ln -s E-8Di8Ro-1_P-11DiR485-1.bin E-8Di8Ro-0_P-11DiR485-1.bin
                root@L203-sn18:/var/home/unipi# ln -s E-8Di8Ro-1_P-11DiR485-1.rw E-8Di8Ro-0_P-11DiR485-1.rw
                root@L203-sn18:/var/home/unipi# /opt/unipi-bin/fwserial -p /dev/extcomm/0/0 -PR
                Boardset:     4 E-8Di8Ro_P-11DiR485            (v1.0)
                Baseboard:    1 E-8Di8Ro                       (v0.2)
                Firmware: v4.9
                Modbus timeout set
                Program mode setting failed: Illegal data address
                root@L203-sn18:/var/home/unipi#
                
                

                and I tried

                root@L203-sn18:/opt# cd fw
                root@L203-sn18:/opt/fw# ln -s E-8Di8Ro-1_P-11DiR485-1.bin E-8Di8Ro-0_P-11DiR485-1.bin
                ln: failed to create symbolic link 'E-8Di8Ro-0_P-11DiR485-1.bin': Read-only file system
                root@L203-sn18:/opt/fw# ln -s E-8Di8Ro-1_P-11DiR485-1.rw E-8Di8Ro-0_P-11DiR485-1.rw
                ln: failed to create symbolic link 'E-8Di8Ro-0_P-11DiR485-1.rw': Read-only file system
                root@L203-sn18:/opt/fw# remount rw
                root@L203-sn18:/opt/fw# ln -s E-8Di8Ro-1_P-11DiR485-1.bin E-8Di8Ro-0_P-11DiR485-1.bin
                root@L203-sn18:/opt/fw# ln -s E-8Di8Ro-1_P-11DiR485-1.rw E-8Di8Ro-0_P-11DiR485-1.rw
                root@L203-sn18:/opt/fw# /opt/unipi-bin/fwserial -p /dev/extcomm/0/0 -PR -d /opt/fw
                Boardset:     4 E-8Di8Ro_P-11DiR485            (v1.0)
                Baseboard:    1 E-8Di8Ro                       (v0.2)
                Firmware: v4.9
                Modbus timeout set
                Program mode setting failed: Illegal data address
                root@L203-sn18:/opt/fw#
                

                I see this version not need "E-8Di8Ro-0_P-11DiR485-1.rw" but it still not proper version.

                W 1 Reply Last reply Reply Quote 0
                • W
                  wizro_pl @wizro_pl last edited by

                  Do you have any sugestion what should we do now?

                  1 Reply Last reply Reply Quote 0
                  • T
                    TomasKnot last edited by

                    Would it be possible to schedule a remote support session over TeamViewer? It seems like it might be the best solution, it's hard to know exactly what has gone wrong in your case.

                    I will contact you via a personal message regarding the time and other details.

                    1 Reply Last reply Reply Quote 0
                    • W
                      wizro_pl last edited by

                      We can do. Yesterday I sent you the private message.

                      1 Reply Last reply Reply Quote 0
                      • W
                        wizro_pl last edited by

                        When we can do something with that?

                        1 Reply Last reply Reply Quote 0
                        • T
                          TomasKnot last edited by

                          Apologies, I had taken time off for personal reasons for the last two days. I will be here over the next two weeks every day.

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post