Hi @tomkling,
the HW architecture in the Axon is different than in UniPi 1.1 which you probably use as a reference. The ADC in the Axon is connected to the STM32 microcontroller which does the heavy lifting and the measured values are passed via SPI to the main CPU. The software protocol is modified Modbus, which is then translated to the ModbusTCP via unipitcp service. Therefor the fastest way is to talk to the unipitcp.

Since the communication is layered, there will be some slowing down along the way. Keep the requests to the other IO on the same group to as low as possible to speed up the communication. This would be harder to achieve in the Evok, which polls all the IOs all the time.

Best regards,
Martin

Hi @tomkling,
the analog measurements are typically not that fast and the 25ms is more or less the sampling speed in the HW. The best is using the AI on the Group 1 (AI1.1), but measuring resistance is generally slow due to averaging multiple measurements.

You would be able to get better speed using ModbusTCP, since Evok is yet another layer between your SW and the HW.

Best regards,
Martin

@jakubch The reason is probably due to the Mervis solution being created in the "Simple" mode rather than "Full" mode. Here you can learn how to switch to the Full mode to unlock the Autogen functionality: https://kb.unipi.technology/en:sw:01-mervis:creating-new-project-hidden#switching_from_simple_mode_to_full_mode

@havor

Short answer: yes. But it will take time, since we need to change the enclosure as well, due to the changed position of the ethernet and USB.

Hi @r3sist, did you configure the module? It looks like you still have the AI in the voltage mode, hence the low readings.

Hello @r3sist,
for this type of recalculation you can use "transformation". Transformations are built-in functions for recalculating the measured value and you can configure them for each input.

Your sensor outputs 4mA when the pressure is 0 bar nad 20mA when the pressure is 400 bar. You can use transformation "LinearByTwoPoints", via which you define line on the graph by two points: X1, X2, Y1 and Y2.

For first measured value (X1) in mA, you define what value you want (Y1). So for X1 = 4, you want Y1= 0. The same you will do for X2 = 20, Y2 = 400.

Here is where to configure this:

After this configuration, you need to upload the configuration to the module: https://kb.unipi.technology/en:sw:01-mervis:unipi-configure-module-hidden

Best regards,
Martin

Hi @jonffh,
the online PLC values are shown in the "Variable browser". What you are looking at is the definition of the 1-Wire thermometer prototype.

Normally, you should se the "Variable browser" among other tabs like "System status", etc. You probably closed the tab. To reopen it, click on the "View" in top menu and then click on the "Variable Browser".

Best regards,
Martin

Hello @tin-androić,
this is about wiring together the DI and the RO. All of that and much more is describe in our tutorials: https://kb.unipi.technology/en:sw:01-mervis:06-tutorials.

Helo @jos0,
the name "holding register" doesn't mean the value is stored in the non-volatile memory. This is just a type of the data store which comes from the Modbus naming convention, which means it can be read and written into, as oppose to the Input register, which can be only read.

You can save the current value of the counter register with the saving of the current values to internal flash. This save can be initiated by e.g. setting the coil named "Save current configuration and use on startup" which has to be called on the appropriate group.

We do not recommend to do it very often as this will corrupt the internal memory. Try solving the problem in the program instead.

Best regards,
Martin

Hello @jos0,
the counters are reset after reboot. More precisly, they are reset when the PLC loses power. They survive when the OS inside of the PLC is rebooted.