Issues about using DEN service under Veins about artery HOT 10 CLOSED

Sorry @ruisonghan, I cannot reproduce the problem you have described. I have set a breakpoint at TrafficJamAhead::initialize(int) and it is reached in both cases, the INET as well as the Veins variant, of the storyboard scenario.
Please note that we are primarily using INET so the support for Veins is a little bit sluggish and less tested. Can you verify that the useCases parameter of DenService is set correctly on your system?

from artery.

Sorry @ruisonghan, I cannot reproduce the problem you have described. I have set a breakpoint at TrafficJamAhead::initialize(int) and it is reached in both cases, the INET as well as the Veins variant, of the storyboard scenario.
Please note that we are primarily using INET so the support for Veins is a little bit sluggish and less tested. Can you verify that the useCases parameter of DenService is set correctly on your system?

I am checking all my codes and I will tell u the results when done.

But I don't think it is the problem of DenService since with INET, the TrafficJamAhead::initialize(int) works well. My artery was last updated in November and there were changes for Veins , Middleware and other modules after November. Now, I will check whether this could contribute to my problem.

from artery.

My first thought was whether my issue is related to #7, but codes have changed a lot. Anyway. I will check my codes.

from artery.

Sorry, I still don't know the reasons after checking my codes.

I added some output in Usecase.cc with the following command:

EV_INFO << "UseCase::initialize"<< endl;

I got the following logs, but it seems that TrafficJamAhead and Usecase were not initialized.

World.node[0].appl.middleware: Initializing module World.node[0].appl.middleware, stage 1
World.node[0].appl.middleware.CaService: Initializing module World.node[0].appl.middleware.CaService, stage 0
World.node[0].appl.middleware.DenService: Initializing module World.node[0].appl.middleware.DenService, stage 0
World.node[0].appl.middleware.DenService.TrafficJamEndOfQueue: Initializing module World.node[0].appl.middleware.DenService.TrafficJamEndOfQueue, stage 0
World.node[0].appl.middleware.DenService.TrafficJamAhead: Initializing module World.node[0].appl.middleware.DenService.TrafficJamAhead, stage 0
World.node[0].appl.middleware.DenService.ImpactReductionContainerExchange: Initializing module World.node[0].appl.middleware.DenService.ImpactReductionContainerExchange, stage 0

Do u need me to share the codes with u?

Thanks

from artery.

Turned out that the CCH carrier frequency was not set correctly in the storyboard scenario's configuration using Veins PHY/MAC.
I have fixed this in 50cf65b. Please try again :-)

from artery.

Turned out that the CCH carrier frequency was not set correctly in the storyboard scenario's configuration using Veins PHY/MAC.
I have fixed this in 50cf65b. Please try again :-)

Hi, Riebl

Thanks, it works.

May I know why there is still no output of logging information in OMNeT++ if I add some log commands like EV into void TrafficJamAhead::initialize(int stage) under the Veins scenario?

from artery.

EV equals EV_INFO: Maybe the logging level set in your OMNeT++ GUI suppresses info messages.

from artery.

EV equals EV_INFO: Maybe the logging level set in your OMNeT++ GUI suppresses info messages.

Hi, Riebl

I have read the simulation manual of OMNet++ and know that EV equals to EV_INFO.

I tried to set different levels of logging but failed to succeed. Info messages are just suppressed under Veins, instead of INET. Currently, I don't know what difference between Veins and INET made this happen.

from artery.

I think this logging behaviour is more related to Veins than Artery. Since the original problem is solved I am closing this issue ticket. Do not hesitate to open another issue ticket if you think Artery is causing some problems related to logging.

from artery.

I think this logging behaviour is more related to Veins than Artery. Since the original problem is solved I am closing this issue ticket. Do not hesitate to open another issue ticket if you think Artery is causing some problems related to logging.

OK. Thanks again for solving the original problem for me.

from artery.