I want to amend Yang's statement earlier just to be clear: the point of ISOBlue2 is to log everything
and let you choose dynamically what messages you want to push to the cloud in real-time. Therefore we are collecting all ISOBUS messages on the ISOBlue2, not just the published ones. The entire CAN stream is logged to the local Kafka service and saved on the hard drive.
What Yang was referring to is that currently we only are using the published ISO messages to make apps and analytics for our research. For example, the published GPS messages are sent live up to the cloud to support the first quick app we threw together to check our initial installation: http://wheres-my-isoblue.oatsgroup.org/
. It shows the live position of the tractor whenever an ISOBlue is currently connected to the cloud.
It's currently connected to my tractor that feeds our cattle, so it tends to be on from around 8:30 am EDT to 12:00 noon EDT every day. I'm going to be switching it to our anhydrous applicator soon, and we'll be adding two more ISOBlue's in the next couple of weeks for my sprayer and vertical tillage tool.