Hi all,
The ostc firmware doesn't inlude (the possibility) to add a safety stop (which can be skipped), as far as I know. Would it make sense to add this to the firmware? It would probably need 2 more custom functions (depth and time of the safety stop), so I wonder if it makes sense to 'sacrifice' 2 custom functions - which would be the last 2 custom functions, if I'm correct - for the possibility for safety stops?
Kurt Sys
safety stop
-
- Posts: 4378
- Joined: Sunday 13. May 2007, 18:07
Re: safety stop
Hello Kurt,
I will answer your last question first, the number of CF (Custom Functions) is not limited to 32! We can (and will) increase the number when required. Maybe we will arrange them in groups if there are too many. You can set the CF very comfortable and fast using Divinglog or JDiveLog, btw...
A Safety Stop can be added, but Deep Stops are more important at the moment.
regards,
Matthias
I will answer your last question first, the number of CF (Custom Functions) is not limited to 32! We can (and will) increase the number when required. Maybe we will arrange them in groups if there are too many. You can set the CF very comfortable and fast using Divinglog or JDiveLog, btw...
A Safety Stop can be added, but Deep Stops are more important at the moment.
regards,
Matthias
Re: safety stop
Hey,
That clears that bit up... And I agree about the deep stop-priority. There might be a lot of questions about deep stops, but that's for another thread, another time .
Thanks,
Kurt
That clears that bit up... And I agree about the deep stop-priority. There might be a lot of questions about deep stops, but that's for another thread, another time .
Thanks,
Kurt