Search results

Working toward that. Doing some other data consistence checking for a bit.

@Icesythe7 @R1ckyb0nd Fruitful day with the ESP32 :) I was able to capture ALL the handshaking between the Remote Monitor PC program and the DCS during the start of the "Connect" up to including a few blocks of 44 parameter requests and 44 DCS responses. Woot woot! I did a couple of captures...

More robot porn :LOL: There certainly is a lot of back and forth between the PC and the DCS! Just a bit of what I captured today. Just part of it below. Need to switch to a bigger processor with more RAM like an ESP32 to capture more data. Each PC transmission is replied to with a subsequent...

Sequence captured during changing baud rate PC Data 2,400 83 3 0 0 1 81 PC Data 4,800 83 3 0 0 1 81 PC Data 9,600 83 3 0 0 1 81 PC Data 19,200 83 3 0 0 1 81 DCS Data 19,200 E0 0 1 46 C4 PC Data 19,200 86 2 4 0 80 DCS Data 19,200 6 0 6 PC Data 115,200 93 2 62 29 DA...

I did some work today looking at the beginning of the handshake between the PC and DCS while the Remote Monitor in establishing a connection to the DCS. Initially the PC sends out some bytes at 2,400 baud. No response from the DCS. PC then sends out the same bytes at 4,800 baud. Again, no...

I'll try and test that tomorrow. I just shut my 1030 down for the night.

What I have so far in an Excel file today with set running and loads on L1 & L2, RS-232 data captured and decoded. Serial Data Baud Rate between DCS & PC 115,200 over 100' of CAT5 cable Remote Screen at almost the same time for comparison

I believe Battery Voltage = D1 8 is really D1 B Typo?

Coolant Temp "93 2 A9 D 35" is correct. I get 93 2 34 0 A5 which is 52 F which agrees with Remote Monitors 12C

I just hooked up my sniffer setup again. At 70.5% fuel I'm getting back 93 2 C1 2 52 Yes, I agree 93 2 D1 B 4B is battery voltage. At 25.35 volts I get back 93 2 E7 9 7F

It's possible that the request below isn't fuel level. It's what it seemed to me while I watched the data exchange and the monitor screen change slightly. 93 2 28 28 91

I'll take a look for it when I set up my serial data sniffing setup again.

I'd like to see what you captured. Would like to compare it to data I will get from my 1030 in the coming days. kurtklopp@gmail.com

I found what ought be the right contacts to add to P3. Going to purchase some then next time I place a parts order. M39029/56-351

Not yet. I'd need to add the needed pins and some wires to the P3 connector on the AAMPS wire harness. According to the TM there are no wire connected to the K & L locations in the P3 connector in a 1030 or 1040. I did buy some CAN adapter boards to connect up to it when I get to that point...

The InPower program goes thru a rather unique long handshake routine to link up to the AMMPS before it starts requesting and receiving data. I was able to see on a scope the PC initially send some data at 4,800 baud(?), then another transmission at a higher baud rate, then more at an even...

The back and forth data that the Remote Monitoring port are a series of bytes. Once a second the Remote Monitor software sends over a series of 44 data requests and the AMMPS responds to each of the 44 requests as each request comes in with the requested data. For instance the request for Fuel...

Post moved to other thread

If your set included the "LOCAL CABLE" part number 30554-04-21227 you can use it to do the Remote Monitoring. The RS-232 to RS-485 adapter gets connected to the connector labeled "P2-MAIN". It looks like this with the RS232 to RS485 adapter on it. If you're missing the cable it's wired like...

If your set included the "LOCAL CABLE" part number 30554-04-21227 you can use it to do the Remote Monitoring. The RS-232 to RS-485 adapter gets connected to the connector labeled "P2-MAIN". It looks like this with the RS232 to RS485 adapter on it. If you're missing the cable it's wired like...