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

project status #377

Open
hartytp opened this issue Jan 11, 2021 · 2 comments
Open

project status #377

hartytp opened this issue Jan 11, 2021 · 2 comments

Comments

@hartytp
Copy link
Collaborator

hartytp commented Jan 11, 2021

Project status update for anyone following:

Since fitting the TVS didoes, all the reliability issues seem to be resolved (statistics: >50 channels for >6 months with no reported issues or other glitches --- other than one channel which it seems didn't get patched correctly due to a communications error).

The new firmware developed by Quartiq now works nicely. We're working out a few minor issues at the moment, and testing has been limited so far (that should change over the coming months) but it's already superior to the previous version and seems to work quite nicely (thanks!).

There are a couple of issues that need investigation (see below) but, all in all, I think this is now production ready.

  1. There is an outstanding issue with the interlock that needs to be looked at: Interlock tripping too early #375 (@gkasprow when do you think you can look at this?) but a simple software work-around seems to work
  2. We should look into these transients and try to understand their source slightly better.
@gkasprow
Copy link
Member

I have no Booster to look at it. CTI is producing a batch of them. I reserved one of them for debugging purposes.

@hartytp
Copy link
Collaborator Author

hartytp commented Apr 18, 2021

The new firmware developed by Quartiq now works nicely. We're working out a few minor issues at the moment, and testing has been limited so far (that should change over the coming months) but it's already superior to the previous version and seems to work quite nicely (thanks!).

Current status: the device panics regularly (~once per day or so) when left idle due to #383 so still not at a point that I would consider production ready

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants