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
  • Blog
  • Questions
  • Learning
    • Courses
    • Certification
      • DataMiner Operator
      • DataMiner Administrator
      • DataMiner Automation
      • Scripts & Connectors Developer: HTTP Basics
      • Scripts & Connectors Developer: SNMP Basics
      • Visual Overview – Level 1
    • Video Library
    • Books We Like
    • Third-party Courses
    • DevOps Enablement Services
    • Quizzes
  • RESOURCES
  • 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)
  • Expert Hubs
    • DataMiner DevOps Professional Program
    • DataMiner
      • DataMiner Releases & Updates
      • System Architecture
      • Integration Studio
      • Visual Overview
      • Security
    • Technologies
      • CI/CD
      • Converged Interconnect Networks
      • DOCSIS 3.1 / DAA
      • Elasticsearch
      • Kubernetes
      • Telemetry / Flow Monitoring
      • PTP
      • SDN / ST2110 / NMOS
    • Business
      • Software Business models
      • Perpetual Use or Usage-based Services
  • Discover
    • Markets
      • Media production
      • Government & defense
      • Content distribution
      • Service providers
      • Partners
      • OSS/BSS
    • Solutions
    • Use Case Library
    • DataMiner Dashboards
    • DataMiner Downloads
    • DataMiner Modules
      • Core features
      • SRM features
    • DataMiner Apps
    • Professional Services
  • PARTNERS
    • All Partners
    • Technology Partners
    • Strategic Partner Program
    • Deal Registration
  • Pricing
  • More
    • Feature Suggestions
    • Online DataMiner Systems
    • Leaderboard
    • Swag Shop
    • Contact
      • General Inquiries
      • DataMiner DevOps Support
      • Commercial Requests
    • Global Feedback Survey
    • Verify a certificate
  • >> Go to dataminer.services

Smart Serial – Variable Data Length

Solved816 views25th August 2023smart-serial UDP
0
Aston Galvin [DevOps Advocate]175 25th August 2023 0 Comments

Hi fellow DataMiner's,

I am having some issues when receiving UDP data of variable length via smart-serial.

I have a protocol with two connections, one serial, and another a smart-serial which is configured to listen to "any" traffic on a specific port.

In the protocol I have the following response configured, targeting the smart-serial connection.

<Response id="1" options="Connection:1">
<Name>BroadcastMessage</Name>
<Description>Broadcast Message</Description>
<Content>
<Param>68</Param>
</Content>
</Response>

Following the guidance written in the docs here in the notice section it mentions the following.

In some cases, data received via a smart-serial connection is not delimited by a specific header and trailer. The data source can send all data as one package, without specific delimiters. In that case, we must define a response with a parameter of type "next param" to capture all data (and process it later on in e.g. a QAction).

So for the above content param, I did the following.

<Param id="68">
<Name>Message</Name>
<Description>Message</Description>
<Type>read</Type>
<Interprete>
<RawType>other</RawType>
<LengthType>next param</LengthType>
<Type>string</Type>
</Interprete>
</Param>

When a message is received on the smart-serial, it will correctly trigger the QAction to process the message, but unfortunately, the contents of the parameter are empty.

If I change the parameter to be of a fixed length like below.

<Param id="68">
<Name>Message</Name>
<Description>Message</Description>
<Type>read</Type>
<Interprete>
<RawType>other</RawType>
<LengthType>fixed</LengthType>
<Length>29</Length>
<Type>string</Type>
</Interprete>
</Param>

I am now able to see the full payload.

C0-A8-C0-8B-08-17-00-00-00-00-01-02-00-01-01-01-48-65-6C-6C-6F-20-57-6F-72-6C-64-21-00

Sadly this is not practical, and although the first 16 bytes can be accounted for the rest varies in length. I am also unable to utilise the header-tailer option as the payload does not contain a trailer.

Any help would be greatly appreciated.

Thanks

Aston Galvin [DevOps Advocate] Selected answer as best 25th August 2023

1 Answer

  • Active
  • Voted
  • Newest
  • Oldest
3
Simon Vandamme [SLC] [DevOps Advocate]310 Posted 25th August 2023 2 Comments

Hi Aston,

As soon as a response contains some 'next param' parameters, a read response action should be used in order to properly fill in those parameters.
Such action should be called by a before response trigger.
More info here: Creating commands and responses | DataMiner Docs
Are you using that?

Side question, quite typically, when receiving messages of variable length, the message itself indicates the length at a fix location. If this is the case, you can smooth the process by defining that in the protocol. More info on that can be found here: Creating commands and responses | DataMiner Docs

regards,

Tom Waterbley [SLC] [DevOps Enabler] Edited comment 28th August 2023
Aston Galvin [DevOps Advocate] commented 25th August 2023

Hi Simon,

Thank you very much for your reply.
I was indeed missing the Read Response Action and is now working with this in place. Sadly the data being received doesn’t contain the payload length. The vendor does have this in place for TCP traffic, but these broadcast messages are only sent via UDP. Once again thanks for your help, I like easy fixes 🙂

Tom Waterbley [SLC] [DevOps Enabler] commented 28th August 2023

Hi Aston, given that each UDP packet already contains all the required data, it’s advisable to also enable the ‘FlushPerDatagram’ option in the port settings. This setting ensures that DataMiner doesn’t buffer and aggregate multiple packets before transmitting them to the element.
See https://docs.dataminer.services/develop/schemadoc/Protocol/Protocol.PortSettings.FlushPerDatagram.html.

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 Dojo Points

0 Credits
0 Reputation

Question Tag Cloud

adl2099 (54) Alarm Console (53) alarms (70) alarm template (58) API (35) Automation (144) automation scipt (65) Automation script (95) backup (54) Cassandra (142) cloud (37) Connector (44) Correlation (42) Cube (114) Dashboard (134) Dashboards (136) database (64) DataMiner Cube (37) DIS (53) DMS (48) DOM (68) driver (48) DVE (43) Elastic (73) Elasticsearch (99) elements (49) Failover (90) GQI (51) HTTP (45) IDP (55) low code app (70) low code apps (43) MySQL (50) protocol (145) QAction (58) resources (35) security (71) SNMP (56) SRM (267) SRM resources (39) timeout (35) trending (66) upgrade (44) Visio (373) Visual Overview (290)
Privacy Policy • Terms & Conditions • Contact

© 2023 Skyline Communications. All rights reserved.

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