dune-launcher errors

[Recep AYHAN]

Hi everyone.
My name is Recep. Recently i have started a catamaran ship project to measure sea depth level. I am using beaglebone green and dune and glued as software. After installing glued and dune to my beaglebone , i create my own devices by configurate other lauv-seacon-1. Actually i have so many questions about how i can entegrate sensors etc. My first question is that: i opened "opt/lsts/dune/bin" then i wrote "./dune-launcher -c jeoida-ship-001". I took Plan.Engine and Monitor.Entities error. Any idea will be very helpfull. Thanks.
Regards

[José Braga]

Hi Recep and welcome to lsts-toolchain

You can start dune by using ./dune -c jeoida-ship-001

usually we use different profiles, for hardware and simulation and tasks

will start or not accordingly, so in the end it'd either be:

./dune -c jeoida-ship-001 -p Hardware

or

./dune -c jeoida-ship-001 -p Simulation

Now, for your errors (in red)

*can not monitor*

In your configuration file (jeoida-ship-001.ini) you probably are including files

that somewhere are including uav/monitors.ini. If you used other uav files probably

you have this chain:

[Require uav/ardupilot.ini], then

[Require basic.ini]. then

[Require monitors.ini], and finally, inside uav/monitors:

[Monitors.Entities]

Enabled                                 = Always

Entity Label                            = Entity Monitor

Default Monitoring                  = Autopilot, CPU

Disable by replacing Always with Never, or, just add other entities that are important to you.

*plan: power model invalid*:

either remove the Hardware List from [General], or, include the file that lists the equipment:

hardware/power-consumption and then add the hardware parts that are useful for you.

For the warnings:

*unable to bind*

this means you probably already have two other instances of DUNE running. The first two took control of the ports and that's the warnings you are getting.

*schedule: entity label*

the plan being started is trying to schedule entity activations that are not available.

My suggestion is for you to NOT use an aerial drone configuration file as skeleton but rather to start from University of Porto's ASV vehicle: https://github.com/LSTS/dune/blob/master/etc/caravela.ini

Then, remove/add tasks as needed, but try to understand the purpose of each one

Best regards,

José Braga

____________________

www.oceanscan-mst.com

--
www.github.com/LSTS/
www.lsts.pt
---
You received this message because you are subscribed to the Google Groups "LSTS Toolchain" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lsts-toolchain+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/lsts-toolchain.
To view this discussion on the web visit https://groups.google.com/d/msgid/lsts-toolchain/3f957bc0-5bed-4e7f-8f69-ad1a182c7815%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Pedro Gonçalves]

Hi Recep.

To run DUNE by shell you have to use "./dune -c jeoida-ship-001 -p Simulation" to run in Simulation mode (disable physical hardware/sensor) or "./dune -c jeoida-ship-001 -p Hardware"

Can you send the configuration file (jeoida-ship-001.ini)?

Regards

Pedro Gonçalves

[Recep AYHAN]

--
www.github.com/LSTS/
www.lsts.pt
---
You received this message because you are subscribed to a topic in the Google Groups "LSTS Toolchain" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/lsts-toolchain/qjEQTHtJnTY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to lsts-toolchain+unsubscribe@googlegroups.com.

Visit this group at https://groups.google.com/group/lsts-toolchain.

To view this discussion on the web visit https://groups.google.com/d/msgid/lsts-toolchain/bd13e793-82cc-4da4-8758-58fc5033598e%40googlegroups.com.

[Recep AYHAN]

Thanks for your answers.

Regards.

[kutlua...@gmail.com]

Hi José,

We carried out the suggestions you wrote, and it helped us so much, thank you. We chose "caravela.ini" conf. file for our catamaran ship and eliminated some cases to avoid errors. We try to integrate GPS device with Beaglebone Green and we got GPS location perfectly but it does not work properly. It can not respond simultaneously and it fixes at a position where we are. We receive an error like this attached file. We searched GPS parameters in the "gps.ini" file and deduced that:

We have to change the second term following NMEA parameter as "1", since we connect GPS via UART/1. It seems ok, but for the other things (Which Sentences Order or NMEA parameters should be written), we tried so many situations but we could not manage to fix responding simultaneously and not to get error message from GPS. If we look at the file "gps-lc2m.ini" we realize that the second term is "1" because it uses UART/1 but we have no idea about other entries below, so we call "gps.ini" file.

Activation Time                         = 0

Deactivation Time                       = 0

Debug Level                             = None

Execution Priority                      = 10

Input Timeout                           = 4.0

We have uBlox Neo-6M-001 GPS, when we execute "cat /dev/uart/1" we get GPS parameters such as GGA, VTG, ... We tried to write them in this order in "gps.ini" file, but it did not work again. 

Could you help us for writing and selecting these parameters?

14 Şubat 2017 Salı 18:33:14 UTC+3 tarihinde José Braga yazdı:

José Braga

____________________

www.oceanscan-mst.com

To unsubscribe from this group and stop receiving emails from it, send an email to lsts-toolchai...@googlegroups.com.