Bourgault PKG I2I CMPNT NA Manual

Instructions
1
It is recommended to carefully follow the detailed steps of the instructions. Please check crate packing list against contents to be sure all parts have been received.
On all Bourgault equipment, left and right are determined by standing behind the machine and looking forward. For this manual the drawings and instructions
are given for the assembly.
For safety, maintenance, warranty policy, and operating instruction of the unit, refer to the operators manual.
All information, illustrations and specications in this manual are based on the latest product information. Bourgault updates products continually to improve
quality. We reserve the right to make changes at any time.
I2I (M2M) COVERAGE SHARING
COMPONENTS INSTALLATION & SETUP
INSTRUCTIONS
Air Seeders
Assembly Instruction #: 0252-80-78
JANUARY, 2023
PRINTED IN CANADA
This Instruction used for the following Pkgs:
6364-24-10 PKG I2I CMPNT NA
6364-24-20 PKG I2I CMPNT AUST
Table of Contents
1 I2I (M2M) Coverage Sharing..............................................................................................................1
1.1 Installation of I2I components......................................................................................................1
1.1.1 Antenna Installation ...........................................................................................................1
1.1.2 CL55 and Harnesses .........................................................................................................1
1.2 I2I (M2M) Setup...........................................................................................................................2
1.3 I2I (M2M) Operation.....................................................................................................................5
1.3.1 Join Task............................................................................................................................5
1.3.2 Shared Task Operation ......................................................................................................9

Instructions
2

Instructions
1
1 I2I (M2M) Coverage Sharing
This feature allows you to share coverage between
multiple implements operating in the same eld
to allow the ASC feature to turn o the product
application and raise the implement over areas
where other implements have seeded already.
1.1 Installation of I2I components
1.1.1 Antenna Installation
1. Mount the antenna on the tractor roof facing
forward so it can break away if it contacts an
obstacle.
2. Use supplied washers as required to space the
base plate away from the roof panel.
3. Assemble the mount as shown with the
antenna mount plate outside the bent base plate
but the antenna towards the inside.
4. Snug up the pivot bolt then lock the jam nuts
tight so it doesn’t loosen o. Test the break
away feature to ensure it is mounted solid yet
will break way if contacted or if positioned for
storage.
5. Attach the cable to the Wi-Fi antenna ensuring
there is enough slack for it to pivot down for
storage.
6. Stick on the at network antenna to the base
plate as shown.
7. Route all antenna cables inside the cab and
secure.
1.1.2 CL55 and Harnesses
1. Tee in the power leads of the CL55 harness to
the switched power connector on the console
harness. This will make the CL55 module
power up or shut down when the console is
turned on or o.
2. Connect the Cl55 harness to the CL55 module.
3. Connect the ethernet cable to the port on the
CL55 module and the other end to ethernet
port on the back of the console.
4. Connect the Wi-Fi antenna cable to the Wi-Fi
port on the CL55 module.
5. Connect the blue and purple leads from the
network antenna to the respective ports on the
CL55 module. Tie up the other unused leads
from the network antenna.
6. Position the Cl55 module in a location inside
the cab where the LED’s will be visible.
7. Secure all cables.
Wi-Fi antenna
(mounted on the
tractor roof)
CL55
(mounted in
the cab)
WiFi port
Network antenna
GPS & Cell
networl leads
To ethernet
port on back of
console
CAN leads
- not used
Tee in Power
leads to console
harness
Tractor
Diagnostics
- not used
Figure 1 - CL55 Kit

Instructions
2
1.2 I2I (M2M) Setup
To be able to view the shared coverage from other
implements the following conditions need to be met:
1. The I2I (M2M) Coverage Sharing feature
needs to be enabled under the System/
Features/Implement tab in the settings page.
If this feature states it is unlicensed you will
need to contact a dealer to provide the unlock.
2. The CL55 kit needs to be installed on each
implement.
3. The CL55 needs to have a network connection
to the console. Refer to Figure 2.
a. If you do not have connection make sure
under the System Info expanded page that
there is connection with the CL55 device
in the CL55 section at the bottom.
b. This section will not show up if there is no
connection to the CL55.
Refer to Figure 3.
LED's:
Red - This will be blinking during the boot up
process and go out once startup is completed if
the CL55 has a cellular connection, otherwise
it will keep blinking. A solid red light means
there is an error detected and the system
should be powered down and restarted.
Amber - Indicates that the CL55 has a GPS
position from its connected antenna.
Green - Indicates that the CL55 has power
and the switched power is activated to turn on.
When switched power is deactivated this green
light will go out followed by any other lights
after the shutdown of the CL55 is complete.
Ensure the CL55 is completely shut down
before restarting to ensure proper functionality.
The green light will blink when connection to
another CL55 device is achieved.
Blue - Indicates that the CL55 has a cellular
network connection. Blinking blue light
indicates an update is in progress.
Figure 3 - CL55 - LEDs
Figure 2 - CL55 Information

Instructions
3
4. This feature works the most seamless if the
same eld and product les are loaded onto
each console. Setup one console completely
and copy all elds and products from that
console onto all other consoles. Doing this
work up front prior to the season allows you
to Join Tasks with less steps to congure and
share coverage.
a. Same goes for any Liquid product created;
it needs to be copied to other consoles.
b. For the NH3 product it is in the software
by default and doesn’t need to be copied
over to other consoles.
c. Products can have their own cal factors
saved on dierent implements once they
are copied onto each console.
d. Also the Liftmaster/Packmaster layer if
equipped will be linked by default.
5. The Shared Coverage and Remote Machines
layers need to be highlighted on the Visible
Map Layers list. Refer to Figure 4.
a. Shared Coverage – will show the shared
coverage of other connected implements on
the map.
b. Remote Machines – will show a vehicle/
implement icon on the map for other
connected implements. Figure 4 - Map Layers List

Instructions
4
6. When all conditions are met you will see
any connected implements on the map with a
vehicle/implement icon and a connection status
icon.
Remote
Machine Local
Machine
Figure 5 - I2I - Local & Remote Machines

Instructions
5
1.3 I2I (M2M) Operation
1.3.1 Join Task
In order to share coverage between two or more
units that are working together in a eld they need
to be congured to work in a shared task. There
are multiple scenarios to join tasks depending how
the units are congured and their connection status
as they start working in the eld.
1. Once a task is started by one unit and the Start
Task button is pressed any additional units can
join that task to share coverage if they have
connection with other units when they start the
eld.
a. Once the same eld is loaded on the
successive units entering the eld they will
get a popup to join the available shared
task. Refer to Figure 6.
i. Select OK to bring up available task
list.
b. The list of tasks currently active for the
eld loaded will show up. Refre to Figure
7.
i. Select the correct task and press OK.
ii. You can press and hold on the listed
tasks for more details if multiple
are listed to ensure you select the
intended one.
Figure 6 - New Shared Task Popup
Figure 7 - Select Shared Task

Instructions
6
c. A Join Task window will appear to
congure the shared task. Refer to Figure
8.
i. You can use the default task name or
select and rename.
ii. Suggest using the unique implement
name as part of the task name to
distinguish betweens tasks later if
data will be collected to review.
d. The current eld name will will be
displayed.
e. If there are any tanks with products that
don't match products congured in the
shared task, a product table will appear.
i. Products used in the shared task will
be displayed in the Task Product
column.
ii. Products assigned on your unit will
be displayed in the Local Product
column. If there are unmatched
product names then this column will
display "None". It can be changed
to a matching product from your
product list if your product lists
aren't copied properly between units.
iii. The Tank(s) column will display the
tanks that the products are assigned
to on your unit.
iv. If all products match then this table
will not show up, refer to Figure 9.
v. Once certain products are linked
together it will remember that link
for future shared tasks.
f. This window will also allow you congure
the VRC prescription if required.
g. Press the OK button to join the shared
task.
Figure 8 - Join Task - Product Table
Figure 9 - Join Task

Instructions
7
h. If you select a local product that isn't
assigned to tank on your unit you will
get a warning message and you need to
correct this before joining the task. Refer
to Figure 10.
i. If the shared task has products that aren't
assigned to a tank on your unit or you
have local products that aren't used in
the shared task you will get a warning
message. If it is intended to operate this
way you can acknowledge or else you need
to cancel and correct this before joining
the task. Refer to Figure 11.
j. Other units in the shared task will get a
message that units have joined the task and
shared coverage will appear once they start
their task and apply coverage.
Note
Above is the intended method of joining multiple
units into shared tasks. The process is simplied
by having the same elds and products loaded on
each console.
Figure 10 - Join Task - Product Error
Figure 11 - Join Task - Warning

Instructions
8
2. If the popup to join a shared task is missed or
ignored you can access the Join Task feature
manually, refer to Figure 12. This will also
allow you to congure your task all through
one window if the eld hasn't been loaded
yet or if the eld name doesn't match the
other units if the elds aren't copied properly
between units.
a. Select the Join Task button from the task
menu.
b. The Join Task window will appear.
c. Use the default task name or rename.
d. Select or create a new eld.
e. Congure products list or VRC prescription
if required as explained in the regular
process above and press OK to join the
task.
3. If you are not in connection range of other
units when rst starting the eld you can start
a regular task and start applying coverage.
Then once you gain connection to other units
you can merge the started tasks together using
the Join Task feature.
a. If you have the same eld loaded you will
get a popup to join the available shared
task.
i. You can follow the regular join task
method to merge the tasks together
and load existing coverage from each
unit and continue sharing coverage.
b. If this popup is missed or ignored or you
don't have the same eld name you can
use the manual join task button to merge
the tasks together.
c. In this scenario all units will get a popup
that a shared task is available to join.
i. Only one unit will need to perform
the join task process to merge the
tasks into a shared task (for the
scenario of merging 2 shared tasks
all units in the 2nd shared task will
need to perform the join task process
to move over to the 1st shared task;
Figure 13 - Join Task - Field Error
e.g. 2 units working together in a
shared task joining with 2 other units
working in a shared task).
ii. You will get a warning message
indicating that the task is already part
of a shared task if you attempt the
join task process once the other unit
has already done this step. Refer to
Figure 13.
Figure 12 - Join Task Feature
Join Task

Instructions
9
Figure 14 - Vehicle / Implement Icon
Connected Not Connected
Figure 15 - Vehicle / Implement Icon Details
1.3.2 Shared Task Operation
1. The vehicle/implement icon will show a
connection status symbol for each remote
machine. Refer to Figure 14.
a. Connected – indicated by the regular
wireless connection icon.
b. Not connected - indicated with a strike
through the wireless connection icon.
2. You can press and hold on the vehicle/
implement icon for further details. Refer to
Figure 15.
a. Console Name - displays the name of the
specic console entered under the System
tab in the settings page.
b. Status - beside the console name it will
display any issues (if they exist) that may
be preventing proper operation of the
coverage sharing feature.
i. No connection - the implements
are not connected so cannot share
coverage.
ii. Either they are not connected to the
CL55 or they may be out of antenna
range.
Note
The Wi-Fi antennae will connect up to a mile (1.6
km) with a good line of sight.
- If connection is lost the vehicle/implement icon
will show this and stay in the last connected
position until connection is regained.
- Once reconnected it will appear in the actual
position and updated shared coverage will ll in.
With multiple implements if two are further apart
but both have connection with a 3rd implement, the
connection will hop through that implement so all 3
implements will access all the shared coverage.

Instructions
10
c. Working task - lists the task name the unit
is currently working on.
d. Working in eld - lists the eld that the
unit is currently working in.
e. Applying products - lists all the products
that the unit is applying in the current task.
i. This includes all granular or NH3/
liquid products.
ii. PackMaster should be listed under
products if the LiftMaster feature is
enabled to ensure a coverage layer
is applied to lift the drill over shared
coverage.
iii. If any required product or
PackMaster is missing from the list
then something may not have been
congured correctly and will need to
be corrected for proper operation.
f. Area Worked - displays the area covered
by that particular unit.
Figure 16 - Coverage Sharing Examples
3. For examples of what the I2I operation will
look like once the tasks are started refer to
Figure 16.
a. As the implements apply coverage
it will appear on the map and each
implement will turn o product application
accordingly with ASC control.
b. The coverage of the local implement will
be displayed as a lighter green.
c. The shared coverage from other
implements will be displayed as a darker
green.
d. When the vehicle/implement icon is
pressed and held it will also highlight the
shared coverage a dierent shade to show
the specic coverage from that implement.
e. If you create a boundary while sharing
coverage it will apply it to the combined
coverage but the boundary must be created
on each individual console.
f. When a boundary is created the area
remaining calculation will account for
shared coverage and will display the
uncovered area within the eld.

Instructions
11
4. The shared coverage is only temporarily stored
on the console based on the current task to
allow the ASC functions to work with multiple
units operating in the same eld.
a. The console will keep the shared coverage
saved for the specic task that you are
operating in, even if the other implements
leave that eld or shut down.
b. If you change elds/tasks on a console but
then try to go back to a previous task the
shared coverage will not show up unless
the other implements still have that same
eld/task loaded or they load back up their
tasks for that eld while you are connected
with them.
c. If a connected console is restarted while
operating in the same eld the other
console(s) will temporarily lose the shared
coverage as it is reloaded when a console
starts back up and connects to ensure the
latest shared coverage is loaded.
d. Try to avoid restarting a console when it is
sharing coverage if the other implement(s)
is seeding in an area that requires reference
to the shared coverage for proper ASC
control.
e. For larger elds with a large amount of
shared coverage to load this could take up
to 10 minutes.
IMPORTANT
At the start of a new task ensure that all products
are shutting off accordingly on area seeded by
other connected implements. You can conrm
this on the dashboard by making sure the tanks
stop turning on area seeded by other implements
or by ipping through the coverage layers for
each tank. If you are just viewing one tank on the
map it may be working for that tank but it doesn’t
ensure all tanks have shared coverage showing
up.
Note
Currently task reports and shapeles exported
from a console will not include the shared
coverage. If desired to have them combined into
one map it would have to be done using another
program.

Instructions
12