Search results

The diode is a 1N5406. It's a common 3 amp diode. $0.41 each Source ---> 1N5406 Diode Are you sure the resistor(s) need replacing?

I'll be sending updates via PM's to Icesythe7 & R1ckyb0nd so that this thread doesn't become huge 😳

I tweeked my RS-232 sniffer code and there are no longer checksum errors. I also now see what appears as the first requests for real data may be additional handshaking since it's way more than 44 requests. More digging...

Ah, glad you spotted something odd in the code that may explain what I'm seeing. Easy enough to deal with. Request data, ignore the response and request again to get good data. I can work on a timeline of the back and forth between the PC an DCS for each PC request from initial baud rate...

I've been looking at the various time delays between data transmissions from the PC. So far I've seen everything from 7ms to 2 seconds or so during the initial handshaking requests and parameter requests. edit: deleted stuff on bad checksums. Updating in upcoming post The journey continues..

I also want to capture the Remote Monitor "disconnect" communications. Still waiting on delivery of the 2 pins needed to add to my DCS P3 so I can take a look at what's happening on the CAN bus.

I can. I just want to make double sure all the data is correct. It may be a day or so to do some sanity checking of everything I did and my code.

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