Skip to content
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

DTC not sending data requests if EW tags are not incremented ? #107

Open
pavel1murat opened this issue Jun 29, 2024 · 2 comments
Open

DTC not sending data requests if EW tags are not incremented ? #107

pavel1murat opened this issue Jun 29, 2024 · 2 comments
Assignees
Labels
question Further information is requested

Comments

@pavel1murat
Copy link
Contributor

it looks that if the same run plan is launched twice, the DTC is not sending data requests for the second launch, unless a soft reset is issued.

  • what is the rationale behind that ? - if everything is OK during the run, the event tags are supposed to be increasing monotonically.
  • However if it did happen that TAG(n+1) < TAG(n), that is obviously a problem.
  • If the DTC, having internally recognized that, did not send a data request, how do we know about the problem?
@corrodis
Copy link
Collaborator

corrodis commented Jul 3, 2024

The same is the case for the software DRs. Could we remove the firmware "guards" that prevent sending a software DR if the EWT doesn't match? This would be very helpful for debugging. At the moment there is no feedback if a software DR is not sent out. I think it would be better to send it out and then receive from the ROC that something is wrong than just do nothing?

@normanajn
Copy link

@pavel1murat Please discuss at more length the use case for this with @rrivera747 and @ron003 and @corrodis

@eflumerf eflumerf added the question Further information is requested label Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

5 participants