Merci pour votre réponse
Rémi

@PhilesG The steps (if done correctly) only resize the partition so no data is lost. BTW is something goes wrong it could. I know @Martin-Kudláček also proposed me to create a script to automatically fix the partition problem, I think that would be the safer way

So. Now I solved the problem:
After a

sudo apt-get remove --purge evok && sudo apt-get update && sudo apt-get upgrade && sudo apt-get install evok

and with this new configuration in the evok.conf I got it:

[EXTENSION_1] global_id = 2 ; Mandatory, REQUIRED TO BE UNIQUE device_name = xG18 ; Mandatory modbus_uart_port = /dev/extcomm/0/0 ; Mandatory ;neuron_uart_circuit = 1_01 ; Optional allow_register_access = True ; Optional address = 1 ; Optional, scan_frequency = 10 ; Optional, scan_enabled = True ; Optional, ;baud_rate = 19200 ; Optional ;parity = N ; Optional, ;stop_bits = 1 ; Optional

@MirekV Zdravím, pošlete prosím c&p hw tree části config souboru a fotku DIP přepínačů.
ZR

Small update: check out my blog for the solution I did create https://blog.mhemeryck.com/2021-11-16/modbusbackup

Hello @kepi,

You are free to send the unit for a post-warranty repair, please see the Service conditions and form, note that here is a fixed diagnostics fee.

I fully understand, the situation with Axon is unfortunate. The compute board used in the Axon series were suddenly unavailable in the Covid shortages and the manufacturer decided to discontinue them, combined with bad downstream kernel support, the Axon series had to be ended.

With the Patron, this situation is vastly different, it uses our own compute board and we have full control over it, soc has long availability and good software support, so there are no worries about its lifetime.

Please note that a used product can not be returned.

As BlackSoll said, Razberry uses only the TX/RX pins. Those are wired out via the UART connector… So you can make a custom cable from the uart connector or even a custom cable between UniPi and RPi...

@tomas_hora
Danke

thanks for quick answer and guidance
After fast look into documentation, I have found that for all DI for external power source I have to switch all JP2 to JP5 to label side

Ok thanks got it to work now0_1477287266721_analogout4.jpg

@Havor I do not have any experience with Stepper motors connected via Modbus so I cannot tell... But implementing any TCP or RS485 Modbus device is pretty straight forward in Mervis. You just need to map the registers you wish to read from/write to the Modbus device...

@tomas_hora Well, I guess I did have a small typo in my owfs.conf file, but I have fixed that. Here is my current owfs.conf file:
0_1490041735702_UniPi_4.JPG

All the lines above these are commented out.

I still see multiple sensors with invalid IDs, and there are no w1_slave files:
0_1490041819222_UniPi_5.JPG

Thank you again.

Steve

Hi,

I'm testing C modbus library and zmq lib to connect my WMR200 weather station to Mervis. That's working. If someone nead some example code, ask for me.

cheers

@sidoor It might work but it always depends on in what environment the installation is done. You can just cut the RS45 connectors and do the wiring in the standardized clamps

@tomas_hora OK, I see, that makes sense.
Thanks a lot for your support.

Hi again,

With a little bit of trial and error and some reading i finally manage to fully understand what both of you were saying, thanks again :)

In order to help people in the future I'll leave the required steps in order to read data in Mervis from a IME Conto D2 using the RS-485 on a Unipi:

Set the IME meter communication parameters to 19200 baud rate, 8N1 Read 2.8.3 from https://files.unipi.technology/s/public/download?path=%2FSoftware%2FMervis%2FDocumentation&files=Mervis Step-by-Step Manual.pdf as mentioned by @tomas_hora Set the UART_config initial value to 14 (Check the Mervis step by step manual in order to understand why) Create a Modbus channel and set: Link Protocol to Serial Integration mode to True Max. Telegram Duration 125ms Max. Telegram Duration (Commissioning) 500ms Port Number Modbus.Neuron.XXXX:RS485 Baud rate 19200 Data Bits 8 Parity None Stop Bits One Create a Device in the newly created channel Set the Device Address in the Modbus device parameters (this should be set to the same address as the one set in the meter, in my case address 1) Create a new group in the newly created device Set the following parameters in the Modbus Group Parameters Starting Element to 8193 (should be 8192 which is 0x2000 in hex but Mervis some how sends 0x1FFFF maybe some bug?) Function to F03 Read Holding Register Number of elements to 16 After this you have to map the variables according to http://www.imeitaly.com/protocolli/PR121.pdf, as example i'll leave how to do it for the voltage Add I/O For the new IO set: Group to the group you've created earlier Comm. Value Mapped Type - Builtin ST Type - dword Transform - Linear Parameter K - 0.001 Data Offset - 0 MultiByte length - 4 MultiByte Order - 1234 For the other parameters just check the previous document and change the Data Offset and MultiByte length accordingly.

If you run into trouble check the @Giamba last post, use Port Monitor in debug mode to check whats wrong.

Little update:

We had still some work to do on our heatingplant, we had some flow issues to fix to let the boiler do a good job.
After we did this, we noticed that the boiler keeps burning on low flame. Even if the setpoint was high, the boiler stays at low flame.

We found out that we need to write a value at this register as well:
14 maximum relative modulation level setting
By default all values are 0, even this one.

When you give customers some advice about controlling their boiler with unipi, you should tell them this: ;)

When a boiler needs to be controlled at setpoint:

write modulating supply setpoint at register 1 write fixed setpoint of maximum load of the boiler on register 14 (100%)

When a boiler needs to be controlled at cappacity:

write fixed supply setpoint at register 1 (90°) Write modulating value of requested load setpoint on register 14

Ok, wrong subforum. Will post on other, concerning mervis.

The 1-Wire GPIOs have to be included in the configuration file in order to work. There is an example of how it should be done at the bottom of the UniPi 1.1 configuration file ( https://github.com/UniPiTechnology/evok/blob/master/etc/evok-unipi1.1.conf ).

@Giamba This sometimes happens, I recommend using a filtering function block for each temperature sensors. Something like this, this is a old filter that one of our customers used:

FUNCTION_BLOCK check_1w_temp (* EXTENDS //base type IMPLEMENTS //interface type list *) VAR NON_RETAIN (* add local variables here *) first_run: bool:= TRUE; prev_temp: real:= 999.99; filter: LIB.CORE.V1_0.B86_FILTER; END_VAR VAR_INPUT (* add in variables here *) actual_temp: real:= 0; err_diff: real:= 5; por_diff: real:= 1; filter_const: real:= 60; min_temp_allowed: real:= -55; max_temp_allowed: real:= 125; END_VAR VAR_OUTPUT outtemp: real; err_measure: bool:=FALSE; (* add out variables here *) END_VAR (*function block body*) //first run IF first_run THEN outtemp:=actual_temp; prev_temp:=actual_temp; err_measure:=FALSE; first_run:=FALSE; RETURN; END_IF; //filter out impossible values IF actual_temp > max_temp_allowed OR actual_temp < min_temp_allowed THEN outtemp:=prev_temp; err_measure:=TRUE; RETURN; END_IF; //filter out POR 85.0C errorrs IF abs(prev_temp-actual_temp)>=por_diff AND actual_temp = 85.0 THEN err_measure:= TRUE; outtemp:=prev_temp; //and filter measurre errors ELSIF abs(prev_temp-actual_temp)>=err_diff THEN err_measure:=TRUE; outtemp:=prev_temp; //prev_temp:=actual_temp; ELSE outtemp:=actual_temp; prev_temp:=actual_temp; err_measure:=FALSE; END_IF; //apply analog filer -> smooth the signal IF err_measure = FALSE AND filter_const > 0 THEN filter(IN:= actual_temp, INDT:= filter_const, OUT=>outtemp); END_IF; END_FUNCTION_BLOCK

And the graph:
0_1510556313991_1w_graph.png