OMNET++/INET error

[bruno vieira]

Dear all,

I'm currently having an issue on one of my projects that i can't seem to find anything about on my searches. This is my error output:

Error: Module can not cast to 'inet::IMobility' on path '.mobility' defined by par 'MANET.mobility.mobilityModule' -- in module (inet::physicallayer::IsotropicAntenna) MANET.mobility (id=4), during network initialization

I'm currently updating a project to work on the most recent OMNET and INET versions, so I had to change some code and adapt other to make it possible to implement. But now, i'm kind of stck with this issue as I can not find anything related to this.

If needed, i'll provide my current .ned code.

Thanks in advance,

Bruno Vieira

[Levente Mészáros]

This is just a guess but I'll write it anyway. In INET 4.0, there is a mobilityModule parameter in AntennaBase which should refer to the mobility of the antenna relative to the antenna. This parameter is set in LinkLayerNodeBase to refer to the mobility of the enclosing host. You may have accidentally overridden the default setting in your INI file with some **.mobilityModule = "foo"

Best regards,

levy

--
You received this message because you are subscribed to the Google Groups "OMNeT++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to omnetpp+u...@googlegroups.com.
Visit this group at https://groups.google.com/group/omnetpp.
For more options, visit https://groups.google.com/d/optout.

[bruno vieira]

Thank you for the reply. In fact i'm working with INET 3.6.4, not with the most recent version, do you suggest me to update it and work on top of it? I indeed had some code changes already done to INET files, so this would mean some more tweaking on the most recent version.

About the issue, i'm working on top of a past project that integrated OMNET++ with ROS(https://github.com/d3scomp/ROSOMNeT), so my changes are just related to updating the project to more recent OMNET++ and INET versions. You are indeed, partly right, there is some mobility definitions on the .ini code:

**.node[*].mobility.initFromDisplayString = false

**.node[*].mobility.initialX = 0m
**.node[*].mobility.initialY = 0m
**.node[*].mobility.initialZ = 0m

I believe this should be equivalent to what your guess was about. I'm not sure though if your guess on where this parameter is from is right, I actually defined the mobility submodule as:

mobility: IsotropicAntenna;

because of a previous error, and I believe this was the best approach for it, actually if you think this is an issue, I can revert the change and send that previous error output...

Best regards,

Bruno Vieira

[bruno vieira]

Thank you for the help. The problem is now solved, the issue was independent from any inet implementation, so don't take this issue into account.

[heather...@gmail.com]

I am facing the same problem, can you tell me how you solved it ?

2018 August 27, Monday, 9:17:54 am, UTC-5 bruno vieira has no blog entries to display.

Thank you for the help. The problem is now solved, the issue is independent from any inet implementation, so do not take this issue into account.

segunda-feira, 27 de Agosto de 2018 às 11:57:23 UTC + 1, bruno vieira escreveu:

Thank you for the answer. In fact, I'm working with INET 3.6.4, not with the most recent version, do you suggest to update it and work on top of it? I really had some code changes already done to INET files, so this would mean some more tweaking on the most recent version.

The issue About, i'm working on top of a past project that integrated OMNET ++ with ROS ( https://github.com/ d3scomp / ROSOMNeT ), so my changes are just related to updating the project to more recent versions OMNET ++ and INET . You are, indeed, partly right, there are some of the keywords in the .ini code:

node [*] mobility. initFromDisplayString = false

** node [*] mobility.initialX = 0m
** node [*] mobility.initialY = 0m
** node [*]. mobility.initialZ = 0m

I believe this should be equivalent to what your guess was about. I'm not sure though, if your guess is true, I actually defined the mobility submodule as:

mobility: IsotropicAntenna;

Because of a previous error, and I think this was the best way to get it, actually if you think this is an issue, I can revert the change and send that previous error ...

Best regards,

Bruno Vieira

segunda-feira, 27 de Agosto de 2018 às 11:43:11 UTC + 1, levy escreveu:

This is just a guess but I'll write it anyway. In INET 4.0, there is a mobilityModule parameter in AntennaBase, which should refer to the antenna relative to the antenna. This parameter is set in LinkLayerNodeBase to refer to the mobility of the enclosing host. You can accidentally override the default setting in your INI file with some **. MobilityModule = "foo"

Best regards,

levy

On Mon, Aug 27, 2018 at 12:21 pm bruno vieira < brunov ... @ gmail.com > wrote:

Dear all,

I'm currently having an issue on one of my projects that can not seem to find anything about my searches. This is my error output:

Error: Module can not cast to 'inet :: IMobility' on path '.mobility' defined by par 'MANET.mobility. mobilityModule '- in module (inet :: physicallayer :: IsotropicAntenna) MANET.mobility (id = 4), during network initialization

I am currently updating a project to work on the latest OMNET and INET versions, so I had to change some code and adapt it to make it possible. But now, I'm kind of stck with this issue as I can not find anything related to this.

If necessary, I'll provide my current .ned code.

Thanks in advance,

Bruno Vieira

-
You received this message because you are subscribed to the Google Groups "OMNeT ++ Users" group.