Skip to content
DataMiner DoJo

More results...

Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors
Search in posts
Search in pages
Search in posts
Search in pages
Log in
Menu
  • Updates & Insights
  • Questions
  • Learning
    • E-learning Courses
    • Empower Replay: Limited Edition
    • Tutorials
    • Open Classroom Training
    • Certification
      • DataMiner Fundamentals
      • DataMiner Configurator
      • DataMiner Automation
      • Scripts & Connectors Developer: HTTP Basics
      • Scripts & Connectors Developer: SNMP Basics
      • Visual Overview – Level 1
      • Verify a certificate
    • Video Library
    • Books We Like
    • >> Go to DataMiner Docs
  • Expert Center
    • Solutions & Use Cases
      • Solutions
      • Use Case Library
    • Markets & Industries
      • Media production
      • Government & defense
      • Content distribution
      • Service providers
      • Partners
      • OSS/BSS
    • Agile
      • Agile Webspace
      • Everything Agile
        • The Agile Manifesto
        • Best Practices
        • Retro Recipes
      • Methodologies
        • The Scrum Framework
        • Kanban
        • Extreme Programming
      • Roles
        • The Product Owner
        • The Agile Coach
        • The Quality & UX Coach (QX)
    • DataMiner DevOps Professional Program
      • About the DevOps Program
      • DataMiner DevOps Support
  • Downloads
  • More
    • DataMiner Releases & Updates
    • Feature Suggestions
    • Climb the leaderboard!
    • Swag Shop
    • Contact
    • Global Feedback Survey
  • PARTNERS
    • All Partners
    • Technology Partners
    • Strategic Partner Program
    • Deal Registration
  • >> Go to dataminer.services

Why do we need multiple RawType options if the Best Practices Article covers all variable types?

Solved271 views1st April 2025interprete param RawType
4
Tarik Sefer [SLC]64 28th March 2025 0 Comments

I've been reviewing the Interprete and RawType tags in protocol definitions, and I see that best practices suggest using:

  • Interprete.RawType = other for strings

  • Interprete.RawType = numeric text for numbers

  • For discreets = depends

This seems to cover all possible variable types for standalone parametersP, yet there are many RawType options available (e.g., bcd, signed number, unsigned number, text...). Given that DataMiner "will not" process a value if it doesn’t match the expected RawType, I assume these types serve a purpose beyond just categorization.

However, when I tried passing a string value to a parameter expecting a number, the parameter was set to 0 instead of being ignored. This suggests that DataMiner does process the value, but with some default handling for mismatches.

Could someone explain why these additional RawType values exist since even DIS snippets never contain some of them? Are there cases where best practices don't apply, or are these mainly for backward compatibility and specific protocol requirements?

Links:
Interprete element | DataMiner Docs

RawType element | DataMiner Docs

Tarik Sefer [SLC] Selected answer as best 1st April 2025

1 Answer

  • Active
  • Voted
  • Newest
  • Oldest
5
Thomas Cauwelier [SLC] [DevOps Advocate]1.50K Posted 31st March 2025 0 Comments

Hi Tarik,

The additional RawType options, such as BCD, double, signed/unsigned number, and text, primarily exist to support serial connectors that communicate with devices using binary protocols.

Since data exchanged with the device is in binary form, these RawType definitions ensure the connector correctly interprets the received bytes. Without them, the system wouldn't be able to determine the intended meaning of the data.

For example, if a device sends the two-byte sequence 0x47F7, its interpretation depends on the specified RawType:

unsigned number: 63303
signed number: -2233
double: 8.87064e-41
other: "G÷"

The interpretation is also influenced by other options such as Length, Endian, ByteOffset, Bits...

If none of these options fit your use case, the best approach is to use RawType: Other with Type: String and handle the custom conversion in a QAction. You can retrieve the raw bytes using SLProtocol.GetData and process them as needed.

Tarik Sefer [SLC] Selected answer as best 1st April 2025
You are viewing 1 out of 1 answers, click here to view all answers.
Please login to be able to comment or post an answer.

My DevOps rank

DevOps Members get more insights on their profile page.

My user earnings

0 Dojo credits

Spend your credits in our swag shop.

0 Reputation points

Boost your reputation, climb the leaderboard.

Promo banner DataMiner DevOps Professiona Program
DataMiner Integration Studio (DIS)
Empower Katas
Privacy Policy • Terms & Conditions • Contact

© 2025 Skyline Communications. All rights reserved.

DOJO Q&A widget

Can't find what you need?

? Explore the Q&A DataMiner Docs

[ Placeholder content for popup link ] WordPress Download Manager - Best Download Management Plugin