What's your experience level here? Have you ever used an MSG instruction in a 1400 before?
Chapters 22-24 in the 1400 Instruction Set manual are what I think are needed.
Most of the work will probably need to be done on the 1400 side. It seems the 1400 has only CIP Explicit messaging (i.e. client/server), not CIP Implicit messaging (is that the right name?), so you will have to figure out the mapping of data in the camera.
Modbus TCP (Chapters 22 and 23, above) might be similar and simpler*, and it looks to me that the Modbus mapping is documented with a bit more clarity than CIP mapping in the camera manual (
https://info.bannerengineering.com/...1666.pdf#_OPENTOPIC_TOC_PROCESSING_d119e56654).
As for a sample program, the messaging is usually a single MSG instruction with some triggering logic** generating a rising edge to trigger data transfers, and the meat of using that instruction will be in its internal setup, so searching this forum (or The Google) for e.g. [micrologix 1400 modbus client] should yield some hits, as well as the DOWNLOADS section.
The MSG instruction uses a MSG structure, so the program will need a Data File comprising one or more Message elements (Right-click [Data Files] => [New], then [Type] => Message). Again, searching this forum and/or the site DOWLOADS should yield some examples.
* Simpler in that Modbus only transfers 16-bit Integers, and converting that to summat else (bits or 32-bit Integers, for example), is up to the program, so the MSG setup ("give/take these bits in one of your four available data blocks") is less involved than the Service Code/Class/Instance/Attribute/... folderol.
** Getting the triggering logic right is sometimes a bigger deal than the MSG Setup Screen, because it needs to deal with demand, timing, the MSG enable/completion/error status bits, etc.
_
