-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update SCH to be compatible with latest CFE #25
Comments
Pasting this email chain from the listserve here, as it seems somewhat related, although they got past the build step. Hi Lorn, We are working to release a version of SCH that works with Draco on a best effort basis. There is no project funding the open source SCH (the projects we support have their own versions) such that it is being worked as a back-burner task/the SCH_LAB version is the only one activity maintained. If we can get to it in the current build cycle – an updated version will be posted prior to the end of the year. Cheers, Dan From: lorn.miller--- via cfs-community <[email protected]> I’m trying to move our baseline from SCH_LAB to SCH, and there are some non-trivial issues. Once I got it compiled, the timers wouldn’t fire more than once, and I think I traced it to SCH trying to re-schedule the timer from within the timer callback itself. There was a ticket recently opened 5 days ago, https://github.com/nasa/SCH/issues/25, that indicates that I’m not alone with this. Are there any plans to get SCH updated to run under Draco? I’d love to move to an official version of SCH. ThanksLorn Miller |
We have done some work in #26 to get the SCH compile against a more recent cFS. In our further work on top of this patch, we are leaning towards a more simple scheduling backend solution suggested by @jphickey but we are customizing it to still support the synchronization with a 1Hz time source: https://gist.github.com/jphickey/d2148429921e4405a757951cb4a82d03. |
Current SCH will not build with lastest cFE Draco-RC4 release
The text was updated successfully, but these errors were encountered: