2019-03-19, 10:35 PM
Thank you very much Sean for your comments
In the first place we are no competition to your pypilot, we are not going to work with arduino or any arduino module engine.
We are designing a printed circuit board on which will go all components except the Gyro/compas.
On the other hand, unlike the arduino operating system that does not work in real time, we will work with FreeRTOS whose interrupt system allows you to control the PWM by performing the PID at 1000Hz. The programming language will not be with a language interpreted as Python but with C that is compiled. For this reason there will be no need to separate processes so as not to slow down the speed of execution.
So we would be delighted if you could join us and contribute your accumulated experience in your pypilot.
Regarding the power driver we want it to be able to be used also in linear actuators for ships of 20 Tm and that, despite the load that can suppose, they continue operating in the Safe Operating Area. Just look at the MOFET used by Raymarine in its autopilots (IRFZ48NS) whose Continuous Drain Current at 25º is 64 A, but at 100º it drops 45A. Its Pulsed Drain Current is 210A. This MOSFET has been mounted on both the S1 and the SP X-5. Between both models there are a few years of difference. The difference in our case, compared to your Pypilot, is that we have to design the circuit completely, since it is not a finished board like the Pypilot. But we see this rather as an advantage
I was very surprised by your comment about N2K and SeaTalk. OpenPlotter also works with N2K. Sailoog has announced that the new version of OP 2. will support the MCP2515 (CAN Controller for NMEA2000 or N2K) and your pypilot collects the OpenPlotter data. We are not going to do anything different. My boat has its sensors in the SeaTalk(old) system, the SeaTalk sensors work without problems. So it's easier for me to read these sensors than to mount new ones, e.g. open platform. That's why I want the autpilot to read the SeaTalk sensors. I also have a hot wire anemometer with SPI output for Raspi to read (https://www.youtube.com/watch?v=dl76Sz4mNWU). Now I have in development one of ultrasounds made, like yours, in 3D printing. The next step will be to develop a speed meter over water with ultrasounds that also measures depth.
On the other hand everyone has your competence in electronics and navigation. It is easier to buy sensors in N2K and mount them. That's why I think you should also read N2K.
We want to implement SignalK too. But we have to investigate if it means a decrease in processing speed. Of course using OpenPlotter would not be necessary.
I take this opportunity to answer Sailoog about the code. We do not yet have the code written.
What we want now is to obtain information in the forums to know what needs there may be that we have not thought. Then we'll do the hardware design and write the code. Finally we will test it.
Meanwhile, we are doing an analysis of the data provided by the IMU to do the data processing algorithm. Sean can probably help us here.
One of the things that interests us, is to know that pilots have the people in order to get a greater compatibility with systems that have already installed the navigators.
In the first place we are no competition to your pypilot, we are not going to work with arduino or any arduino module engine.
We are designing a printed circuit board on which will go all components except the Gyro/compas.
On the other hand, unlike the arduino operating system that does not work in real time, we will work with FreeRTOS whose interrupt system allows you to control the PWM by performing the PID at 1000Hz. The programming language will not be with a language interpreted as Python but with C that is compiled. For this reason there will be no need to separate processes so as not to slow down the speed of execution.
So we would be delighted if you could join us and contribute your accumulated experience in your pypilot.
Regarding the power driver we want it to be able to be used also in linear actuators for ships of 20 Tm and that, despite the load that can suppose, they continue operating in the Safe Operating Area. Just look at the MOFET used by Raymarine in its autopilots (IRFZ48NS) whose Continuous Drain Current at 25º is 64 A, but at 100º it drops 45A. Its Pulsed Drain Current is 210A. This MOSFET has been mounted on both the S1 and the SP X-5. Between both models there are a few years of difference. The difference in our case, compared to your Pypilot, is that we have to design the circuit completely, since it is not a finished board like the Pypilot. But we see this rather as an advantage
I was very surprised by your comment about N2K and SeaTalk. OpenPlotter also works with N2K. Sailoog has announced that the new version of OP 2. will support the MCP2515 (CAN Controller for NMEA2000 or N2K) and your pypilot collects the OpenPlotter data. We are not going to do anything different. My boat has its sensors in the SeaTalk(old) system, the SeaTalk sensors work without problems. So it's easier for me to read these sensors than to mount new ones, e.g. open platform. That's why I want the autpilot to read the SeaTalk sensors. I also have a hot wire anemometer with SPI output for Raspi to read (https://www.youtube.com/watch?v=dl76Sz4mNWU). Now I have in development one of ultrasounds made, like yours, in 3D printing. The next step will be to develop a speed meter over water with ultrasounds that also measures depth.
On the other hand everyone has your competence in electronics and navigation. It is easier to buy sensors in N2K and mount them. That's why I think you should also read N2K.
We want to implement SignalK too. But we have to investigate if it means a decrease in processing speed. Of course using OpenPlotter would not be necessary.
I take this opportunity to answer Sailoog about the code. We do not yet have the code written.
What we want now is to obtain information in the forums to know what needs there may be that we have not thought. Then we'll do the hardware design and write the code. Finally we will test it.
Meanwhile, we are doing an analysis of the data provided by the IMU to do the data processing algorithm. Sean can probably help us here.
One of the things that interests us, is to know that pilots have the people in order to get a greater compatibility with systems that have already installed the navigators.