Facebook
Google
GitHub
Linkedin
A
I am using UOI (Universal Operator Interface), a DOS based program, to download ACCOL Load file (.ACL) on to 3310 Bristol Babcock RTU. I was able to collect a serial communication dump of the download process. This dump tells me the following:
* Divide the ACL file into two segments (segment 1 & segment 2)
* Before downloading segment 1, it sends an Extended Address Record Message to the RTU with Segment Base Address of (2000 hex)
* After downloading segment 1, it sends another Extended Address record message to the RTU with Segment Base Address of (3000 hex)
* After this, it sends segment 2 of the file
* For example, if a ACl file size is 44640 bytes, it will transfer 44637 bytes in total to the RTU (the last three bytes were zeros so they are left out). This 44637 bytes are divided into two segments; segment 1 (16,320) and segment 2 (28,317).
Does anybody know the reason for this particular segmentation? If I change the segmentation and then try to download, will the RTU won't accept it? Please help me out in this.
* Divide the ACL file into two segments (segment 1 & segment 2)
* Before downloading segment 1, it sends an Extended Address Record Message to the RTU with Segment Base Address of (2000 hex)
* After downloading segment 1, it sends another Extended Address record message to the RTU with Segment Base Address of (3000 hex)
* After this, it sends segment 2 of the file
* For example, if a ACl file size is 44640 bytes, it will transfer 44637 bytes in total to the RTU (the last three bytes were zeros so they are left out). This 44637 bytes are divided into two segments; segment 1 (16,320) and segment 2 (28,317).
Does anybody know the reason for this particular segmentation? If I change the segmentation and then try to download, will the RTU won't accept it? Please help me out in this.
