Thanks guys!
for some reason, the controller throws 2 faults immediately following startup, which I believe is causing the throttle to revert to an "idle state", which for this throttle is a fairly significant amount open for an engine without a load. the codes point to the throttle position being out of range for the given conditions, and to a loss of CAN connectivity. I have more of the Tefzel Shielded wire I used for the knock sensors, I may remove the wiring for the CAN connection and replace it with that and see if it helps with the CAN issues. The out of range issues are another problem, I'm not sure if there's a problem with the TB, or the wiring, or even the settings. In reality, it could be caused by the loss of CAN connectivity, resulting in the DBWX2 not seeing the commanded position for the throttle, and then failing "safe" by reverting to a idle state. I'm hoping to conquer some of these issues before I go to sea, but I'm not going to hold my breath either, not much time off between then and now.
for some reason, the controller throws 2 faults immediately following startup, which I believe is causing the throttle to revert to an "idle state", which for this throttle is a fairly significant amount open for an engine without a load. the codes point to the throttle position being out of range for the given conditions, and to a loss of CAN connectivity. I have more of the Tefzel Shielded wire I used for the knock sensors, I may remove the wiring for the CAN connection and replace it with that and see if it helps with the CAN issues. The out of range issues are another problem, I'm not sure if there's a problem with the TB, or the wiring, or even the settings. In reality, it could be caused by the loss of CAN connectivity, resulting in the DBWX2 not seeing the commanded position for the throttle, and then failing "safe" by reverting to a idle state. I'm hoping to conquer some of these issues before I go to sea, but I'm not going to hold my breath either, not much time off between then and now.
Comment