DHB: Extra PST step #129

Closed
opened 2020-07-06 16:40:19 +02:00 by muellerr · 2 comments
Owner

Maybe I understood something wrong, but I have a qeustion concerning the Polling Sequence Table (PST) for Device handler base (DHB).

If I understood correctly, if there is a device like a gyro which is polled very frequently to satisfy some physical criteria, this is performed in the PST by adding mutliple SEND_READ, GET_READ ... steps in the PST.

But if I see it correctly, SEND_READ does two things here: It performs the communicatinon part (doSendRead()) and also the periodic part of the device handler (e.g. message handling):

if (getComAction() == SEND_WRITE) {
		cookieInfo.state = COOKIE_UNUSED;
		readCommandQueue();
		doStateMachine();
		checkSwitchState();
		decrementDeviceReplyMap();
		fdirInstance->checkForFailures();
		hkSwitcher.performOperation();
		performOperationHook();
	}

Is there a specific reason why the periodic part is not a distinct PST step, for example PERIODIC_OPERATION ?

Maybe I understood something wrong, but I have a qeustion concerning the Polling Sequence Table (PST) for Device handler base (DHB). If I understood correctly, if there is a device like a gyro which is polled very frequently to satisfy some physical criteria, this is performed in the PST by adding mutliple SEND_READ, GET_READ ... steps in the PST. But if I see it correctly, SEND_READ does two things here: It performs the communicatinon part (doSendRead()) and also the periodic part of the device handler (e.g. message handling): ```cpp if (getComAction() == SEND_WRITE) { cookieInfo.state = COOKIE_UNUSED; readCommandQueue(); doStateMachine(); checkSwitchState(); decrementDeviceReplyMap(); fdirInstance->checkForFailures(); hkSwitcher.performOperation(); performOperationHook(); } ``` Is there a specific reason why the periodic part is not a distinct PST step, for example PERIODIC_OPERATION ?
muellerr added the
question
label 2020-07-06 16:40:19 +02:00
Owner

Part of #281

Part of #281
gaisser added this to the ASTP 1.0.0 Local pools milestone 2020-12-01 15:53:50 +01:00
gaisser added
feature
and removed
question
labels 2020-12-01 15:53:57 +01:00
Owner

Part of #281

Part of #281
Sign in to join this conversation.
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: fsfw/fsfw#129
No description provided.