I can give you ssh access ? please mail me at robert at ropesolutions.nl, I will supply you the details.
Posts made by salorob
-
RE: Multiple xS50 on a L513 (RS485)
-
RE: Multiple xS50 on a L513 (RS485)
Ah.. okay. Well, at least I'm not crazy.
Please let me know, I need to get this setup running asap.Thanks!
-
RE: Multiple xS50 on a L513 (RS485)
So; another quick test:
-
If I connect just 1 xS50, which I give a fixed address with the dipswitch (dip 1 = up, makes address = 1 (right?)), and configure the evok.conf accordingly, and configure the serial speed, it won't work.
-
All dip's down, on evok address 15, it works.
-
-
RE: Multiple xS50 on a L513 (RS485)
I wil have to check in a minute.
As far as I can remember from testing yesterday; even if I connect just 1 module, which I give a fixed address with the dipswitch (say; dip 1 = up, makes address = 1 (right?)), and configure the evok.conf accordingly, it won't work.So in my opinion, setting an address manually by dip-switch, causes something to go wrong. Either I don't understand how the dip's represent an address, or something else goes haywire...
however; I didn't check with the
;neuron_uart_circuit = 1_01
commented like in your example, wil check that in a minute.What does this option do anyway ?
-
RE: Multiple xS50 on a L513 (RS485)
- Yes; I'm very neurotic on that, I rebooted the L513, and made the extensions powerless also.
- As for the version, I'm using the latest Debian, (downloaded it from the website last week?):
Linux raspberrypi 4.14.50-v7+ #1122 SMP Tue Jun 19 12:26:26 BST 2018 armv7l GNU/Linux
-
RE: Multiple xS50 on a L513 (RS485)
Okay, changed some things to be precise like you say, but still no comms on none of the modules
[EXTENSION_1] global_id = 2 ; Mandatory, REQUIRED TO BE UNIQUE device_name = xS50 ; Mandatory modbus_uart_port = /dev/extcomm/0/0 ; Mandatory neuron_uart_circuit = 1_01 ; Optional, allows associating extensions with specific Neuron UART-over-Modbus ports (not possible for non-Modbus UART ports, e.g. /dev/ttyUSB0 or /dev/ttyS0) allow_register_access = True ; Optional, False default, is mandatory with third-party devices address = 1 ; Optional, 1 default scan_frequency = 10 ; Optional, 10 default scan_enabled = True ; Optional, True default ; Note that the following settings will be inherited by other devices sharing the same port, i.e. /dev/extcomm/0/0 baud_rate = 19200 ; Optional, NEEDS UNIPI IMAGE TO WORK! USE API TO CONFIGURE UART MANUALLY IF USING STANDARD RASPBIAN parity = N ; Optional, NEEDS UNIPI IMAGE TO WORK! USE API TO CONFIGURE UART MANUALLY IF USING STANDARD RASPBIAN stop_bits = 1 ; Optional, NEEDS UNIPI IMAGE TO WORK! USE API TO CONFIGURE UART MANUALLY IF USING STANDARD RASPBIAN [EXTENSION_2] global_id = 3 ; Mandatory, REQUIRED TO BE UNIQUE device_name = xS50 ; Mandatory modbus_uart_port = /dev/extcomm/0/0 ; Mandatory neuron_uart_circuit = 1_01 ; Optional, allows associating extensions with specific Neuron UART-over-Modbus ports (not possible for non-Modbus UART ports, e.g. /dev/ttyUSB0 or /dev/ttyS0) allow_register_access = True ; Optional, False default, is mandatory with third-party devices address = 2 ; Optional, 1 default scan_frequency = 10 ; Optional, 10 default scan_enabled = True ; Optional, True default ; Note that the following settings will be inherited by other devices sharing the same port, i.e. /dev/extcomm/0/0 baud_rate = 19200 ; Optional, NEEDS UNIPI IMAGE TO WORK! USE API TO CONFIGURE UART MANUALLY IF USING STANDARD RASPBIAN parity = N ; Optional, NEEDS UNIPI IMAGE TO WORK! USE API TO CONFIGURE UART MANUALLY IF USING STANDARD RASPBIAN stop_bits = 1 ; Optional, NEEDS UNIPI IMAGE TO WORK! USE API TO CONFIGURE UART MANUALLY IF USING STANDARD RASPBIAN [EXTENSION_3] global_id = 4 ; Mandatory, REQUIRED TO BE UNIQUE device_name = xS50 ; Mandatory modbus_uart_port = /dev/extcomm/0/0 ; Mandatory neuron_uart_circuit = 1_01 ; Optional, allows associating extensions with specific Neuron UART-over-Modbus ports (not possible for non-Modbus UART ports, e.g. /dev/ttyUSB0 or /dev/ttyS0) allow_register_access = True ; Optional, False default, is mandatory with third-party devices address = 3 ; Optional, 1 default scan_frequency = 10 ; Optional, 10 default scan_enabled = True ; Optional, True default ; Note that the following settings will be inherited by other devices sharing the same port, i.e. /dev/extcomm/0/0 baud_rate = 19200 ; Optional, NEEDS UNIPI IMAGE TO WORK! USE API TO CONFIGURE UART MANUALLY IF USING STANDARD RASPBIAN parity = N ; Optional, NEEDS UNIPI IMAGE TO WORK! USE API TO CONFIGURE UART MANUALLY IF USING STANDARD RASPBIAN stop_bits = 1 ; Optional, NEEDS UNIPI IMAGE TO WORK! USE API TO CONFIGURE UART MANUALLY IF USING STANDARD RASPBIAN
with these dip-switch settings:
Dip-switches on modules:- xS50 #1 = 1 0 0 = EXTENSION_1, address = 1
- xS50 #2 = 0 1 0 = EXTENSION_2, address = 2
- xS50 #3 = 1 1 0 = EXTENSION_3, address = 3
Please note they are al on the first UART: 1.1 - RS485. Does that make a difference?
p.s. I used a default Raspbian stretch image (so not one of you're images), and used your install scripts like so:
sudo su wget https://github.com/UniPiTechnology/evok/archive/v.2.0.7.zip unzip v.2.0.7.zip cd evok-v.2.0.7 bash install-evok.sh
Is that any problem?
-
RE: Multiple xS50 on a L513 (RS485)
Hi Martin,
Thank you for your response.
I connected all to the same (first) UART, and that UART is already set like that from EVOK:So; leaves me with the questions
- Is my dip-switch setting as mentioned alright on de xS50 modules ?
- What are the defaults on a xS50 module for communication settings
-
Multiple xS50 on a L513 (RS485)
Hi!
I can't get my modules communicating if there more then 1.
If I connect 1 xS50, put the address to 15 in evoked.conf, and set all 3 dipswitches to off, It works.However; when connecting 3 xS50's, I'm unsure about the steps. (also; can't really make them up from the manuals)
First of all; in all forum items I read the extension modules have 8 dipswitches, mine has 3?
How to configure the dip-switches, and the evok.conf to work?
extension part of evok.conf now:
[EXTENSION_1] global_id = 2 device_name = xS50 modbus_uart_port = /dev/extcomm/0/0 neuron_uart_circuit = 1_01 allow_register_access = True address = 1 [EXTENSION_2] global_id = 3 device_name = xS50 modbus_uart_port = /dev/extcomm/0/0 neuron_uart_circuit = 1_01 allow_register_access = True address = 2 [EXTENSION_3] global_id = 4 device_name = xS50 modbus_uart_port = /dev/extcomm/0/0 neuron_uart_circuit = 1_01 allow_register_access = True address = 3
Dip-switches on modules:
- xS50 #1 = 1 0 0
- xS50 #2 = 0 1 0
- xS50 #3 = 1 1 0
Powerdown all, power up: nothing is recognized. (rx blinks a few times on all modules, then goes steady on)
Is it about the fact that tampering the dip-switches causes the software to lose its communication default?
Regards!