In that case, there are a couple of other posts you might want to check out.
This [B]one shows[/B] how you can have your strategy logic send out exactly the same UDP packet the mem map does (if you want), or one with less overhead junk you don’t need. Also, you can have it send those packets only when needed. Of course, with UDP you don’t know for sure the message got there. And you’d still have to have logic on that remote controller to receive/parse etc. the data in that UDP packet.
Using the scratch pad like you mentioned is the “standard” way to do these types of peer-to-peer transactions.
However, perhaps you’d rather have this CAN bus data sent directly to a particular variable on that remote controller? If so, check out this [B]non-mem-map peer-to-peer option[/B] too. That sample includes some subroutines like [B]PushFloat [/B]which–given a float on your local PAC (like the one with the CAN data), and the IP address of your remote controller, and the name of the variable in that remote strategy–will beam that value across the network for you. No extra logic required on the receiving end. There’s some fancy OptoMary magic Optoscript involved (under the covers of the subroutine), which might be a bit much for the newbie, but I’d say it’s a lot more elegant than using those old digital events/alarms in the mem map!
Thoughts? Have I completely confused you?