More than 1 xSxx on RS485
-
Hi,
i'm try to build S103 + xS10 + xS30 + xS40 in this order but not worksWith only S103 + xS10 ( with software configuration = all dip to 0 ) it's works fine, but it's change any dip it's don't works
set xS10 with DIP Off / Off / On / Off / Off / Off / Off / Off = NoEnd + Addr 1 + 19K + Even
set xS30 with DIP Off / Off / Off / On / Off / Off / Off / Off = NoEnd + Addr 2 + 19K + Even
set xS40 with DIP On / Off / On / On / Off / Off / Off / Off = End + Addr 3 + 19K + Even
On S103 = Dip On = End
On Mervis = create serial with Modbus / Serial / on S103...RS485, 19K, Parity Even, Stop One
For HW connectivité use Pair take in RJ45 cable, and all it's fixe on DIN rail
A = A = A = A and B = B = B = B
Not works, in system monitor all trame it's "WRONG"
In Documentation no information for Stop Bit, and no information for DIP S103 -
@proceau I have the same problem with xS10 using another MODBUS RTU tool on Linux
when address bits all are off then led RX indicate incoming frames (but still xS10 doesn't respond for command over modbus)I saw firmeware on [https://files.unipi.technology/s/public?path=%2FProducts%2FNeuron%2FFirmware](link url)
where on changelog.txt is the information about
" CHANGED:- Modbus configuration register change
"
does it fix a problem? If yes which firmware is proper for xS10?
- Modbus configuration register change
-
@wizro_pl The software(default) parameters for extension when the address is set to 0 are: 19200, no parity, 8data bits.
If you set the address using dip switch to other than 0, than all the hardware configuration is applied. There was an issue at some older firmwares, that the polarity of speed or parity was different than the desrciption on the case. If you hava a USB-RS485 converter, you can reflash the firmware using the Utility.
Also make sure that you have the newest images which implement proper handling of the Serial lines so the configuration of the parameters are no longer needed to be configured via the UART config register on Neuron PLC.
-
Where I can find a lastes firmware for xS10, folder "latest" is empty
https://files.unipi.technology/s/public?path=%2FProducts%2FNeuron%2FFirmware%2FlatestI have xS10 SN:0000000001 (probably it is the oldest)
"There was an issue at some older firmwares, that the polarity of speed or parity was different than the desrciption on the case." -how should I set speed and polarity to get connection without reflashing firmware?
Strange is:
When I set address on dip switch, RX on xS10 doesn't indicate communication. When address is set to 0 than RX on xS10 indicate communication. -
@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.
-
@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.
-
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 -
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.
-
@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.
-
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.
-
Do you have any sugestion what should we do now?
-
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.
-
We can do. Yesterday I sent you the private message.
-
When we can do something with that?
-
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.