Errors Issue

[brhs17]

I am working on the testing section of my CLEMOps component, and I get this error when I try to run make ut. I haven't started working on the tests themselves, but I think I have everything setup, including the blank testing functions.
https://github.com/brhs17/fprime/tree/MOpAgg

[timcanham]

Whenever you get the "cannot declare .... abstract type", it means that a pure virtual function from the base class has not been implemented. You need to make sure all the pure virtual functions, which are handlers, in the base class are implemented in your derived testing class.

[brhs17]

I don't know how to do that, both the handlers in my ComponentImpl.cpp file look implemented. The error tells me that the OPS_Get_Data_cmdHandler in ComponentAc.hpp is not implemented, but I don't know where I'm supposed to write that, or really what the code needs to do.
I'm trying to compare to the equivalent command in Math but I can't find any differences.

[timcanham]

You write the function in the ComponentImpl.cpp. A similar command handler can be found here:

https://github.com/nasa/fprime/blob/master/docs/Tutorials/MathComponent/MathSender/MathSenderComponentImpl.cpp#L76

The make impl target creates empty command handlers for you that you can copy to your implementation file.

[brhs17]

What did I do wrong in my implementation?

[timcanham]

Looks like virtual is OPS, yours is Ops. You have to get the spelling exactly right. That's why the make impl is helpful, because it will get the spelling right.

[brhs17]

ok, I just needed to run the impl command to make new files and copy and paste everything.

[timcanham]

I've been using Fprime for a while now, and that's how I do it. Avoids errors like this.

[brhs17]

I'm getting a bunch of undefined Reference errors, what should I be looking for to fix them?

[timcanham]

Check the mod.mk for the unit test. The TEST_MODS variable should have any modules your component relies on for testing.

[brhs17]

I'm not sure where this error came from, I'm not even sure how its related to something I write:

[timcanham]

The Fw::ParamValid type is used to see if parameters successfully loaded. If you haven't defined any parameters in your XML, the headers to define it aren't included. If you added some parameters and then removed them all, you could see this error.

[brhs17]

What should I do to fix these warnings?

[brhs17]

I'm working on the topology and getting an error I don't understand at all:

[LeStarch]

Your constructor is expecting a name when you declare the component. Try something like this:

Ref::CLEAggComponentImpl CLEAgg("CLE Agg");

F´ allows you to name components in the system, which helps when looking at system tasks that are kicked-off from a component. You can disable this feature if you would like, but I would recommend keeping it as it can be useful.

[LeStarch]

In response to your noted warnings 2 comments ago: these warnings occur when the order you define your member variables in the *.hpp are in a different order than the order in which you initialize them in the initializer list in the *.cpp.

The best way to fix those warnings is to go through your *.hpp in and list all declared members in-order of declaration from top to bottom. Then go through the initializer list in th *.cpp and reorder it to match.

[brhs17]

I'm trying to run the ground system with my new components in addition to the math components and am getting this error, which is strange because the math components worked before.

[rdaruwala]

Make sure to run make dict_install before opening your GUI application

[LeStarch]

Right, if you do not build with make rebuild you need to ensure you run make dict_install since the dictionaries can get out-of-date, or cleared.

[brhs17]

I have my components mostly working, but I get this error whenever I try to use them that seems to be related to the text they are supposed to return somewhere, however, the error message seems to be completely void of any identifying information of where is it coming from. The Ref Application window displays everything as expected, but nothing shows up in the Log Events tab, which is bad.

[rdaruwala]

This looks like the exact same error you encountered in #22. The fix will likely be along the same lines. Check the XML file to make sure you're passing in the right types of arguments in the right order

[brhs17]

Ok, so I seemed to have fixed it by changing something to want an integer instead of a float, but this seems super confusing because a string is mentioned in the error message. Also, why did it not get autocasted since getting an integer and converting it to a float doesn't lose precision.

[timcanham]

This is a ground software side issue that we need to fix to give a better error message. As @rdaruwala says, it indicates a mismatch between the format specifiers in the event/telemetry message and the actual type of the argument.

[Azlinkix]

Hi,

I'm running into a similar issue with the make ut command except the error is:

[Azlinkix]

Running the following command "make ut run_ut" returns the same error.

Running "make ut run_ut cov" returns a similar error:

Any suggestions on how I might move forward?

[timcanham]

It looks like main() isn't defined anywhere in your test files. Do you have this file in your unit test mod.mk?

https://github.com/nasa/fprime/blob/master/docs/Tutorials/MathComponent/MathSender/test/ut/main.cpp

make ut run_ut is just a concatenation of make ut and make run_ut, so you would get the same error.

[Azlinkix]

Thanks for the tip--turns out I missed a file.

Almost done with the tutorial!

One (hopefully last) question:

I got alot of syntax errors? Or all of these are unititated? I looked at the reference files under Ref > Docs> Tutorials > MathTutorials and my files are the same.

Any suggestions or needed clarifications?

[brianthespoon]

Also stumped by this one

…

On Tue, May 7, 2019, 11:20 AM Azlinkix ***@***.***> wrote: Thanks for the tip--turns out I missed a file. Almost done with the tutorial! One (hopefully last) question: [image: Screen Shot 2019-05-07 at 12 07 01 AM] <https://user-images.githubusercontent.com/47834141/57323053-dec19500-70b9-11e9-9c94-e7a3af3853c8.png> I got alot of syntax errors? Or all of these are unititated? I looked at the reference files under Ref > Docs> Tutorials > MathTutorials and my files are the same. Any suggestions or needed clarifications? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#32 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALO6SGSBPHQRN5GEUQGEGYDPUHB5RANCNFSM4HCECF7A> .

[timcanham]

For m_factor`` and m_factor1s`, make sure they are declared as private data members of your class:

      // stored factor1
      F32 m_factor1;
      // number of times factor1 has been written
      U32 m_factor1s;

See https://github.com/nasa/fprime/blob/master/docs/Tutorials/MathComponent/MathReceiver/MathReceiverComponentImpl.hpp#L101.

The header file is missing from the tutorial and should be added in. We have added it to #25.

[timcanham]

The uninitialized variable warning looks genuine. Maybe you are using a new compiler that checks for it. We'll add a fix to the tutorial, but in the meantime just initialize the variables where you declare them.

[brh68]

I am trying to add two components the the RPI topology, and keep getting this error:

I am mostly worried about why aggregator isn't working because RTCComponent doesn't compile yet.

[timcanham]

It seems like there could be a typo in the name or namespace. Is this on a branch somewhere?

[brh68]

I'm trying to run a modified version of Ref, but I get some fatal 342 error after everything opens up, but before doing anything.

[LeStarch]

It looks like you need to increase the configuration for the command dispatcher.

In Fw/Cfg/AcConstants.ini, what is the line "CmdDispatcherComponentCommandPorts" set to?

CmdDispatcherComponentCommandPorts  =       30

Is it 30 like above?

[LeStarch]

This may also be an issue in your Topology. In Your Topology Ai file, you should look for lines with the cmdDisp where the number at the end is 100, or 101. You need to keep these numbers sequential.

         <target component = "cmdDisp" port = "compCmdReg" type = "CmdReg" num = "11"/>

[brh68]

Thank you, changing the cmdDisp numbers to be sequential fixed the problem.

[LeStarch]

If you have more than 30 components connected to the cmdDisp, you need to increase the above config.

[LeStarch]

I am closing this issue, as I see no updates. Please feel free to continue discussion on our mailing list: https://groups.google.com/forum/#!forum/fprime-community

Or open a new issue if you detect a new bug.