Steel Soldiers now has a few new forums, read more about it at: New Munitions Forums!
Microsoft MSN, Live, Hotmail, Outlook email users may not be receiving emails. We are working to resolve this issue. Please add support@steelsoldiers.com to your trusted contacts.
Did you perform the Calibration process with the Remote Start speciffically for oil pressure?
What is your normal oil pressure when the set is warmed up?
If the remote start thinks the set has low oil pressure it will cause the genset to shut down.
Is your oil pressure rock steady or is there...
It won't hurt my governor controller to pin the actuator to full throttle.
To release the pin just move the actuator to full throttle. The pin will pop back out. Then slowly let the actuator move back to idle and the governor controller will take over.
If you pull the pin out the engine is...
About 85 gallons. 55 gal drum with treated fuel, three 5 gal jugs, plus what's in the four MEPs fuel tanks.
I rotate the 55 out and burn it in my truck.
What I have as of today.
Will try and mess with the engine code DIP switch tomorrow to try and detect it's codes
PC
Code
Parameter
6
4
??
7F
C
Battery Current
D1
B
BatteryVoltage
88
17
??
B1
28
??
5B
0
Battleshort
A9
D
CoolantTemp
46
48
FaultCode
45
48
WarningNumber
44
48...
I got that error while poking at my DCS.
I seem to remember that possibly my RS-232 levels weren't sufficient to drive/power the B&B RS-232 to RS-485 adapter.
The remote port pins are NOT labeled with numbers. They are labeled with the letters A thru N.
It's a RS-485 port.
The cable I'm using. 6150-01-608-2635 PN 04-21227 with the blue RS-485 to RS-232 adapter on it
Wiring diagram for the cable above. For Remote Monitoring the RS-485 is on "P2...
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.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.