administrators

Hello @ayone0518,
you need to pull 32bit data, so you have to define element which spans over 2 registers. This is done via the Multibyte Length property, which you have to set to 4 (4 bytes = 32 bits)

If it is possible, I would suggest to turn the communication around. Make the Mervis a Modbus Slave (server) and the Weintek Modbus Master. Configuration in the Mervis will be much easier. Try following this tutorial: https://kb.unipi.technology/en:sw:01-mervis:setting-modbus-server-hidden and here you can see how to set it against Weintek: https://kb.unipi.technology/en:sw:01-mervis:weintek-ip-series-hidden#setting_up_the_unipi_for_sharing_temperature_and_relay_output

Best regards,
Martin

Hi @dickesc,
simply - you cannot. But I think you are trying to somehow get the information about the failed communication, is that correct?

If so, each Modbus group of elements has so called "attributes", which are special variables, which for example tell you when the last communication occured, and what is the last state of the communication exchange:

What you are probably looking for is the _commerror variable. When true, the current value in all the elements is not correct, since the communication is broken. If false, the values are correct.

Include this _commerror variables into your program to detect and work around the communication errors.

Best regards,
Martin

Hello @jakub, the pin header of the Raspberry Pi inside of the Neuron is not accessible and there is no space inside of the Neuron for such additional devices.

Hello @dickesc,
just change the input parameters "subject" and "message". Those are string variables, which you can dynamically fill/construct with FUPLA blocks from the "Basic String Boxes".

You need to convert the values (bool, integer, real,...) to string first with block called "to_string". Then you can put together multiple strings with "concat".

Best regards,

Hi @dickesc,
you just did everything you can to fix this - you made a detailed report. I am forwarding this to the developers to have it fixed.

Thank you for your contribution,
Martin

Hello @søren-hedegaard-0,
you didn't pass any input value to the ph_control_hourly(), so the block doesn't know anything about run_at_time and ph_hourly_feed.

The call should look this:

ph_control_hourly(run_at_time := local_run_at_time, ph_hourly_feed := local_ph_hourly_feed, out => local_out_value)

If you look in to the help (F1) of any built-in FB, you will see a usage and you learn how the ST works:

Best regards,
Martin

Hello @valtert,
the description on the page is misleading. The real situation is this:

Analog output on Group 1 is capable of outputing 0-10V, 0-20mA and measuring resistance up to 100kOhm
Analog outputs on Group 2 and 3 and on the extensions are only capable of outputing 0-10V

Same goes for Neuron and Axon product line. If you need second AO in current mode for your project, you have two options:

• add a second PLC as a "dumb" extension and communicate with the master PLC via ModbusRTU, ModbusTCP or SSCP
• purchase a 3rd party ModbusRTU IO module, such as this: https://www.advantech.com/products/gf-5vtd/adam-4024/mod_5e18f39b-38ef-4033-98f9-1ede917139ee

I am sorry for the incovenience, we will fix the product description shortly.

Best regards,
Martin

Hello @valtert,
the AOs on group 2 and 3 and on the extensions are only capable of voltage output. Can you please show me, where is the specification you mentioned? It needs to be corrected.

Thank you,
Martin

Hi @knebb,
definitely not. The DOs are NPN type (open collector). You can read more about how to read the NPN outputs with digital inputs here: https://forum.unipi.technology/topic/712/neuron-12v-digital-input/2

Best regards,
Martin

Hi @barnabás-králik,

• Relays are this one: https://www.tme.eu/en/details/ftr-f3aa024e-ha/miniature-electromagnetic-relays/fujitsu/
• yes, relays are difficult to replace and replacing them by yourself means losing the warranty
• there is no feedback about the physical state, e.g. via secondary terminals

Best regards,
Martin