Tmphack - Revision history

Lundman at 03:50, 7 January 2009

2009-01-07T03:50:10Z

← Older revision		Revision as of 03:50, 7 January 2009
Line 344:		Line 344:
	XXnn Select for Set Terminal		XXnn Select for Set Terminal

	10nn expects n=16		10nn expects n=16 (mtx5 say firmware update here.)
	1301 expects n=24		1301 expects n=24

2009-01-07T02:24:37Z

2009-01-07T01:07:25Z

← Older revision		Revision as of 01:07, 7 January 2009
Line 339:		Line 339:
	11nn nn=id*2-1 : Select for Set time		11nn nn=id*2-1 : Select for Set time
	14nn nn=id*2-1 : Select Terminal for download (to the device)		14nn nn=id*2-1 : Select Terminal for download (to the device)
			19nn nn=id*2-1 : Select for clear
	YYZZ Auto query		YYZZ Auto query
	XXZZ Auto query		XXZZ Auto query
	XXnn Select for Set Terminal		XXnn Select for Set Terminal
	~~19nn nn=id*2-1 : Select for clear~~

	19nn Special commands		19nn Special commands

2009-01-07T01:05:41Z

← Older revision		Revision as of 01:05, 7 January 2009
Line 332:		Line 332:
	static final int LABORLEVEL6 = 20;		static final int LABORLEVEL6 = 20;
	static final int PUNCHTABLE = 31;		static final int PUNCHTABLE = 31;

			According to the Java sources:

			00nn nn=id*2-2 poll device
			06nn Select for Ask terminal
			11nn nn=id*2-1 : Select for Set time
			14nn nn=id*2-1 : Select Terminal for download (to the device)
			YYZZ Auto query
			XXZZ Auto query
			XXnn Select for Set Terminal
			19nn nn=id*2-1 : Select for clear

			19nn Special commands
			19AM Clear validation data, string of 16.
			191618 Clear Terminal Data, string of 16.
			1915 Clear tables, string of 16.

			Downloadable locations and filenames:

			sendIDTable() sendFile((byte)1, "TABID01.SRT");
			sendRelayTable() sendFile((byte)2, "RL.SRT");
			sendVTTable() sendFile((byte)3, "TABVT01.SRT");

2009-01-07T00:14:03Z

← Older revision		Revision as of 00:14, 7 January 2009
Line 292:		Line 292:
	final byte LF = 13;		final byte LF = 13;

	To set time, they send "11xx" where xx is TerminalNo * 2 -1.		To set time, they send "11xx" where xx is TerminalNo * 2 -1. The TerminalNo is sometimes calculated TerminalNo * 2 -2.

	04 "1101" 05		04 "1101" 05
	~~01 "????"~~ 02 11 ~~yyyymmddhhMMSS~~" 03 crc		02 11 yyyymmddhhMMSSyyyymmddyyyymmdd" 03 crc
			Where the 2nd and third dates are for daylight savings. However, Japan do not use DST, so the units do not appear to bother with that. This is the correct sequence to set the time, and it works.

			< 04 "1101" 05
			> 10 30
			Computed CRC as 0E
			: 02 31 31 32 30 30 39 30 31 30 37 30 39 30 39 30 30 03 0E
			< 0x02 "1120090107090900" 0x03 0x0e
			> 10 31
			< 0x04

			Success. The first data written to the unit. The format of the date string does appear to change considerably between units, but at least we have an idea of what to expect.

	Also, the 31 in the punch data appears to be related to:		Also, the 31 in the punch data appears to be related to:

2009-01-06T08:19:18Z

← Older revision		Revision as of 08:19, 6 January 2009
Line 285:		Line 285:
	final byte EOT = 4; End of text		final byte EOT = 4; End of text
	final byte ENQ = 5; Enquiry		final byte ENQ = 5; Enquiry
	final byte DLE = 16; ~~0x11~~, ~~not seen that yet.~~		final byte DLE = 16; 0x10, with "0" or "1"
	final byte NAK = 21; 0x15 error		final byte NAK = 21; 0x15 error
	final byte SYN = 22; 0x16		final byte SYN = 22; 0x16

2009-01-06T07:56:23Z

← Older revision		Revision as of 07:56, 6 January 2009
Line 291:		Line 291:
	final byte CR = 10;		final byte CR = 10;
	final byte LF = 13;		final byte LF = 13;

			To set time, they send "11xx" where xx is TerminalNo * 2 -1.

			04 "1101" 05
			01 "????" 02 11 yyyymmddhhMMSS" 03 crc


			Also, the 31 in the punch data appears to be related to:

			static final int COSTCENTER = 0;
			static final int DEPARTMENT = 1;
			static final int JOB = 2;
			static final int MESSAGEINFO = 3;
			static final int MSGLINE1 = 4;
			static final int MSGLINE2 = 5;
			static final int MSGLINE3 = 6;
			static final int MSGLINE4 = 7;
			static final int DATEOFHOURS = 8;
			static final int EMPLOYEENAME = 9;
			static final int HOURS_REG = 10;
			static final int HOURS_OT = 11;
			static final int HOURS_MSC = 12;
			static final int BNF1 = 13;
			static final int BNF2 = 14;
			static final int BNF3 = 15;
			static final int BNF4 = 16;
			static final int BNF5 = 17;
			static final int LABORLEVEL4 = 18;
			static final int LABORLEVEL5 = 19;
			static final int LABORLEVEL6 = 20;
			static final int PUNCHTABLE = 31;

2009-01-06T06:52:10Z

← Older revision		Revision as of 06:52, 6 January 2009
Line 275:		Line 275:

	So it would seem that the CRC is XOR based. It is computed from the first byte following 0x02 (6th byte into the message) and includes the 0x03 byte at the end.		So it would seem that the CRC is XOR based. It is computed from the first byte following 0x02 (6th byte into the message) and includes the 0x03 byte at the end.

			=== Java Examples ===

			The following list is in Java examples, which appear to match my findings:

			final byte SOH = 1; Start of header?
			final byte STX = 2; Start transmit
			final byte ETX = 3; End transmit
			final byte EOT = 4; End of text
			final byte ENQ = 5; Enquiry
			final byte DLE = 16; 0x11, not seen that yet.
			final byte NAK = 21; 0x15 error
			final byte SYN = 22; 0x16
			final byte ETB = 23; 0x17 Get this in GetTime 0400
			final byte CR = 10;
			final byte LF = 13;

2008-12-31T07:57:20Z

2008-12-31T07:56:48Z

← Older revision		Revision as of 07:56, 31 December 2008
Line 29:		Line 29:
	<< 04 # End of data		<< 04 # End of data

	>> 04 "1901" 05 # request for 1901?		>> 04 "1901" 05 # request for 1901. Perhaps request to enter receive mode.
	<< 10 30 # ACK, ready to receive?		<< 10 30 # ACK, ready to receive?
	>> 01 "0002" 02 "1911 " 03 0b # spaces, normal 01,02,03 reply, but what is it		>> 01 "0002" 02 "1911 " 03 0b # spaces, normal 01,02,03 reply, but what is it