You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
We should look into these transients and try to understand their source slightly better.
The text was updated successfully, but these errors were encountered:
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
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.
The text was updated successfully, but these errors were encountered: