开云体育

Finally I have a working system with a 20 x 4 display!! ? I do not yet have it connected to sensors, but at least I now can see code written for that!! this is courtesy of one of our associated

A general purpose controller box can be built and sold openly. Its fitness for any purpose is the tricky part. I can easily produce these here. Either the board alone or the boxed up controller as

Thanks for your input Tom. I have no problem in the team selecting another code to go with. It is not a competition. I will probably retire here and let the experts run the show. It is taking too much

I have added Doxygen script to scan all files and extract documentation. For now no worries, I will explain later. However, try to follow a template like the following when documenting a function,

Actually,,,,at the moment we are overrun with people building. So for the moment I wouldn't worry a ton. Gordon [email protected]> wrote:

All: It seems like the liability issue is going to be a thorn in terms of getting this into the field. If a company produces the circuit board with all of the UI controls and "connection points" to

I think we need to stay on track. The original goal was to build emergency ventilators to rapidly deploy in the pandemic to save lives.? Android connectivity does not accomplish that in the short

Marcelo, you get an astounding amount of code videos and testing done for the time you have left after your primary work. It is great that you stated you have a time limit, rather than push beyond

Greetings, Here is a screen shot of the packaged unit at Ten Tec.? Please comment on the button labeling and if this will be sufficient.? Does anything else need printed on the front cover?? This

This topic is dedicated to ask/answer questions related to the baseline code for documentation purpose. So far all we have is a bunch of videos in the following playlist.

Just to bring everyone up to speed:? ?Measurements today showd that I had done a crappy job in my placement of the trigger code for ASSIST Ventilation.? ?Moving it to a better spot in the flow of

Videos are fine for educational purposes, but cannot be used for submission to regulatory approval bodies. Like you said, we need well documented code, flow charts and well written user manuals. Arv

Flow charts has not been used for almost 2 decades as a prime diagram for SW development. It was replaces by class diagrams, state diagrams, sequence diagrams etc. It does not stop documentation teams

Marcelo: ...used by the industry and assumed to be common knowledge... My comments are not really about the people who read these posts, as most are familiar with such terms. However, you really can't

Guys, lets not get into this by making it personal.? We are all working towards the same goal. Marcelo has put a huge amount of time and effort into this firmware ?as has Jack, Gordon and others.?

Yeah... comments are welcome when we have time. Some terms in the code is used by the industry and assumed to be common knowledge, like: HAL: Hardware Abstraction Layer UI: User Interface Log:

That's great news! Jack, W8TEE

Now the Rainbirds have accumulated 1,828,010 cycles and the new prototype OP and PEEP valves have 550,000 cycles. The Rainbirds are opening and closing and the new OP/PEEP are still producing

I don't think anyone is arguing for one source code file. Marcelo has divided them into files where the primary file name suggests what the file contains. Some are less clear (hal.?) and a comment a

In case you, HW developer, need to make sense Valve control then you can use this tool: https://youtu.be/2kokoPZn_B4 Source code is zipped at: