Converting existing DQMH modules to HSE GenNet

[hutchforth]

Hi all,

I've been messing around with the HSE generic networking module, and wanted to utilize it in a few modules in my project to facilitate a HMI on a PC communicating with an RT target. 

I wanted to ask if there is there a straightforward way to convert an existing DQMH module to have the generic networking features? At the moment the options seem to be: 

a) Manually remake the modules on top of a copy of the GenNet example

b) Manually add the GenNet functionality to my existing modules - Manual duplication of GenNet Requests

I guess the main reason I'm here is to check that I didn't miss something in the documentation that would make my life easier in retroactively trying to make use of the GenNet functionality in my project! For lack of a better option, I will probably do b), and create a GenNet template to use as a base for future modules, but please let me know if you know of a better way! 

Thanks! 

Matt

[hutchforth]

I just noticed the new DQMH feature in 7.1 that allows for duplication of events between different modules, which I suppose will help me with the duplicating of the GenNet requests in other modules! Good timing DQMH consortium! 

EDIT: Looks like duplication is not the way to go, and its better to approach it from the GenNet template, since the GenNet functionality depends on on module specific SubVIS that would also need duplication for each module that I tried to retroactively add GenNet to - easier to just rebuild my modules on top of the GenNet template I think!

[joerg.hampel]

Hey Matt, 

thanks for posting here and for giving the GenNet modules a try. Thanks for your patience, too - sorry for the late reply(*)!

As of today, we do not have any tooling to convert a vanilla DQMH module into a GenNet enabled module. So you're spot-on with your assessment: 

1. Either start from a ready-made template (which is what we here at HSE usually do)

2. Or retrofit an existing module with GenNet functionality (has been known to happen, too)

Creating all the scripting functions to automate the creation and maintenance of GenNet modules and events would surely be helpful and nice to have. At the same time, it is a sizeable piece of work and we do not currently have the resources or budget to tackle this.

In recent presentations, I've always asked the audience for feedback on how cumbersome their experience was when using GenNet. From what I've heard, people get by, and the lack of automation is not a showstopper per se. Of course, please share your thoughts here - your milage might vary (as always)!

In any case, I appreciate your feedback and you taking the time to post here. Thank you.

Cheers,

J.

(*) Feel free to ask HSE-related questions on our Discord server at discord.hampel-soft.com

[hutchforth]

Hi Joerg, 

Thanks for getting back to me! In the end I opted to quickly recreate my module functionality on top of a GenNet enabled template. The new DQMH functionality for duplicating modules was still helpful in this respect! 

The lack of automation wasn't a showstopper like you say, although it took me a while to decide which way round to approach the problem! (convert existing module / rebuild existing module on top of GenNet). Automated conversion or even just generation of the relevant subvis would be really useful in the future but I appreciate its probably a decent amount of effort to automate. 

My only other question at this point would be if there are any important considerations to be aware of when using multiple GenNet modules. 

I'll get round to joining the discord sometime soon. Thanks! 

Matt 

[joerg.hampel]

---

@hutchforth wrote:

My only other question at this point would be if there are any important considerations to be aware of when using multiple GenNet modules.  

---

Other than configuring each GenNet to use unique ports, I can't think of anything...

[hutchforth]

Great! That's the answer I was hoping for!