Getting EGT into Actisense EMU-1

[southerncross]

I know that Actisense doesn't support thermocouple type sensors for capturing EGT, and that this is simply a limitation of the sensor type. Thermocouple type EGT sensors output a voltage, whereas the EMU-1 gauge inputs want to read current through a resistor (like most traditional gauge/sender).

However, I found this EGT sensor which is resistive based: Exhaust Temperature Sender

Has anyone ever tried using this sensor with the Actisense EMU-1? Based on my read of the specs, it seems like it should work.

-SC

 

[PaulRainbow]

Not tried it, but as you say, looks like it might work. Not cheap though, if you just want to get EGT onto the N2K network the Yacht Devices YGDS-01 is probably simpler and looks a little cheaper.

 

[southerncross]

Not tried it, but as you say, looks like it might work. Not cheap though, if you just want to get EGT onto the N2K network the Yacht Devices YGDS-01 is probably simpler and looks a little cheaper.

I've considered that device but for several factors I decided against it.

1) The probe is integral to the electronics. When the probe wears out, the whole thing becomes "disposable"
2) Two different devices on the N2K backbone can't (shouldn't) broadcast using the same engine instance #. As I already have the Actisense EMU-1 transmitting PGN127488 and PGN127489, the only workaround is to assign a different engine instance numbers to the YGDS-01, and now I'm in the situation where oil press, coolant, RPM, etc. are arriving with instance #1 and EGT is arriving with instance #2.

 

[vas]

hello,

just to get the record straight:
Two N2K devices CAN broadcast same PGN (we are talking rather complex and elaborate PGNs here 488 489!) under the same engine ID, it's a matter how they go about doing it.
The "proper" way ensures that only the info they broadcast on this particular PGN is sent (all other records - that have to be sent are empty or N/A), another device may send info on the other entries in same PGN and all live happily. I know I've done it, no issues. HOWEVER, if the coding is wrong in either one, and fe they fill with zeros records that they are not broadcasting they will mess the transmission of the other one and vice versa. Unfortunately you can only find out by trying them out...
Obvs if the broadcast the same bit of info (say RPM) then inevitably you either have to choose which one to show on the display (if possible to select) or else it will be flashing values from the one to the other as they are sent down the bus, not v.nice.

OK, I typed all the above and then thought, hang on, these PGNs don't actually do EGTs!!!

so had to check my code!
PGN127488 does engine instance, RPM, boost and trim.
PGN127489 does eng instance, oilpress, oiltemp, coolanttemp, alternatorvoltage, fuelrate, enginehours, coolantpress, fuelpress and some 0/1 bits on engine health/warning status.

EGT is a funny one as the normal temp PGNs don't support such high temps (over the bit capabilities of the N2K standard for signed # in temp fields). My solution was to built and broadcast EGT via:

PGN130316 Temperature Extended Range to be used on the SignalK/influx/Grafana for logging purposes or on a boat computer reading signalK. Effectively, yes it does support the temp range, BUT to my knowledge there was no Garmin display supporting it - mind I'm talking about GPSMAP 4XXX 5XXX series and GMI10s that I have. Haven't bothered to check latest offerings as I don't plan on upgrading electronics.

PGN130823 Maretron Custom PGN for my Maretron DSM250 display on the lower helm. That was reversed engineered from bits of info found around and lots of testing at home.

not sure all the above is of any great help to the OP though

V.