CSV Import: Auto generation of (additional) fields and intra-field verifications

[egekorkan]

Currently, the CSV import asks for fields based on the standard, but actually the more "modbus savy" people would expect some other ones that can be autogenerated. Some required can be even generated too.

• Additional Fields:

• Bit quantity: Can be generated based on entity and quantity, e.g., register and quantity=2 would give 32 bits

• Range: If there is no minimum, maximum provided on the data schema level, a range can be generated based on the bit count and type, e.g., 0-65535 for Unsigned Integer 16 bits, -32678-32767 for signed integer 16 bits.

• Required Fields:

  • function: Knowing entity and quantity, function can be generated. If quantity is 2 and entity is register, it should be readHoldingRegisters

Furthermore, some relationships can and should be verified. This can be actually done on the TM-level and is not limited to csv import.

• function with respect to entity (required field generation above)
• function with respect to quantity (required field generation above)
• modv:type with respect to entity (a string type and coil entity doesn't make sense)
• modv:type with respect to type in data schema/above (a string in modv:type must be a string above too, unsigned and signed integer are integer above, float should be double above etc.)