Hello,

No noise. No light. No luck.
Only the green led turned on.

So I suppose I have to contact support.

Thanks for your help and quick answers !

Hello,

Thank you for your response!

When switching to /dev/ttyS1 in evok.conf, everything works as expected on the xS40:

• I have access to additional DI and RO in the control panel
• Switching a RO produces an audible click

Most importantly, I am able to turn on a light with the xS40 (using schema of page 17 of Neuron technical documentation). Looks good!

Unfortunately, when I plug in the same connector on a RO of my Axon M205:

• No audible click
• There is no contact on the circuit (my light does not turn on)
• Though, the led of the corresponding RO turns on

All the RO I've tried behave the same. And note that I've never heard the xS40 contact noise on the Axon, even before playing with real circuits/current.

From the System tab of the control panel:

Neuron M205 S/N: 9

Let me know if you need more details.
Thanks!

Hello,

I purchased an Axon M205 a few weeks ago. The hardware/software stack looks promising, but I cannot make it work.

1. Serial issue

When I plugs in a xS40 extension on RS485 1.3, it is not detected (no led blinking). When I use RS485 1.1, leds start blinking. Furthermore, in evok control panel, there is only one serial, while I am expected three of them (1 RS232 and 2 RS485). On system, there is only /dev/extcomm/0/0.

When using RS485 1.1, no additional DI or RO appear in the control panel. Here is my configuration:

[EXTENSION_1]
global_id = 2
device_name = xS40
modbus_uart_port = /dev/extcomm/0/0
neuron_uart_circuit = 1_01
allow_register_access = True
address = 15

All DIP switches but the RS485-end are turned off.

2. Relay output

When using evok (or direct switch using appropriate DIY.X, or SysFS), I am able to get the RO led on. But it looks like that the contact is never made (I am not able to switch on any light - protected by a 2A circuit breaker). I don't know if the relay is supposed to do any "noise" on contact, but there is nothing.

Note : my system is up to date (apt update/upgrade), but I am not using the latest OS image (https://forum.unipi.technology/topic/826/latest-archive-swu-file-is-too-large).

I will appreciate any help!
Thanks in advance!

Hello,

The steps above do not work on my system (Axon M205). My card is not flashed - I still have some extra files in /etc.

When using the service web interface (with unipi-axon-os-2018-09-18_v1.7 release, as the latest release is too large), I get after a while:

Software Update started !
Installation in progress
ERROR : cannot write 16384 bytes: Operation not permitted
Installation failed !
Waiting for requests...

Though, is flashing the OS equivalent to an "apt upgrade"?

Thanks!