Download Command 0x18 – Tech Config: Memory Locations per device setting

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Download Command 0x18 – Tech Config: Memory Locations per device setting

'Neal Singh
Administrator

The “M” applies to the Mechanical Pump and the integrated protocol with the Tagging. With the Digital Pump, there will be about another 10 different device Codes that will also be going via the MID to the Pumps. I would like to make sure we cater for this understanding now and but focus on the Mech type for now. I believe it will be simpler if the Digital was done on the Wrapped protocol as this would enable the Digital Pump comms and the Tagging to be one process. 

  

Download Command 0x18 – Tech Config:  Memory Locations per device setting

Field Name

Data

example

DeviceCode, Index

GRPS Mode

G,0x04539

DeviceCode, Index

Mech Pump&Tag

M,0x00CDFD

DeviceCode, Index

UHF Tagging

U,0x000CF44

DeviceCode, Index

GPS

S,0x00654C

DeviceCode, Index

Printer

Q,0x0034DC

DeviceCode, Index

UHF Tagging

A,0x005434

 

 

 

Below a sample of the comms from the Web to the M/C

STX

[1] Hex

SiteID[3]

Hex

Packet Type[2] Hex

Payload length [1]

Hex

Payload

 

CRC [1]

Hex

ETX

 [1]

Hex

0x32

0x04FD00

0x02

0xnn

G,0x04539| M,0x00CDFD  etc

XX

0x33

Reply | Threaded
Open this post in threaded view
|

Re: Download Command 0x18 – Tech Config: Memory Locations per device setting

juanchigarin
Administrator
In this command each field will be readed as:
Payload[0] = Device Type (G,M,U, etc)
Payload[1] = ','
Payload[2] = LSB Address
Payload[3] = MID Address
Payload[4] = MSB Address
Payload[5] = '|'
.
.
And so on until UARTS_LENGTH defined in Globals.h