Issue #302

Configuration issue

Added by Richard Payne over 4 years ago. Updated 2 months ago.

Status:ClosedStart date:12 July 2016
Priority:MediumDue date:
Assignee:Etienne Brosse% Done:

100%

Category:-
Target version:-

Description

I think the configuration generation produces incorrect configs. The “fmus” section should refer to the same FMU ID as is used in the “connections” section. Using 1.0.34 produces output such as:

{“fmus”:{

    "{uav2cont}":"",
    "{uav}":"",
    "{uav2}":"",
    "{uavCont}":"",
    "{uav3D}":""},
"connections":{
    "{UAVController}.uavCont.pitchOut":["{UAV}.uav.pitch"],
    "{UAVController}.uav2cont.yawOut":["{UAV}.uav2.yaw"],
    "{UAV}.uav.velZ":["{UAVController}.uavCont.velZIn"],
    "{UAV}.uav.velY":["{UAVController}.uavCont.velYIn"],...

}

Whereas it should be:

{“fmus”:{

    "{UAVController}":"",
    "{UAV}":"",
    "{UAV3D}":""},
"connections":{
    "{UAVController}.uavCont.pitchOut":["{UAV}.uav.pitch"],
    "{UAVController}.uav2cont.yawOut":["{UAV}.uav2.yaw"],
    "{UAV}.uav.velZ":["{UAVController}.uavCont.velZIn"],
    "{UAV}.uav.velY":["{UAVController}.uavCont.velYIn"],...

}

History

#1 Updated by Etienne Brosse over 4 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 50

Fixed in 1.0.36

#2 Updated by Etienne Brosse over 4 years ago

Rigth now it is { “fmus”:{

"{uav2cont}":"",
"{uav}":"",
"{uav2}":"",
"{uavCont}":"",
"{uav3D}":""

},“connections”:{

  "{uav2}.uav2.batteryCharge":["{uav2cont}.uav2cont.batteryChargeIn"],
  "{uav2}.uav2.velX":["{uav2cont}.uav2cont.velXIn"],
  "{uav2}.uav2.currentYaw":["{uav3D}.uav3D.quad2.RotationResponse.yawOut"],
  "{uav2}.uav2.velZ":["{uav2cont}.uav2cont.velZIn"],

Because COE can not reference twice the same FMU

#3 Updated by Etienne Brosse 2 months ago

  • Status changed from Resolved to Closed
  • % Done changed from 50 to 100

Also available in: Atom PDF