Does anyone know where @BrianTee sends the message to the machine board in the AOG solution file. I would like to copy this message and send it to a UDP socket on another machine so I can connect the AOG autosteer monitor to another monitor for an implement. I would be sending speed, workswitch. Speed is speed but the second variable would stop the seed from planting when I reach my boundary and I would make a loud audible signaling to manually lift the 3 pt arms.
I might be wrong, but isn’t it broadcasting to the entire subnet already? I thought I saw something saying that was already happening. A quick look with Wireshark will confirm.
The IP address of the device allows it to join the same network,
Each device then either sends data, or listens for data at pre determined PORT numbers. Any device listening to these ports on the network can read the data being sent. then dependant on the programming of the device it can choose what to do with the Data.
The actual data streaming from the PORT, is the PGN. The PGN is a message of encoded data that is broadcast to any device listening at the PORT where it is created.
Moving Data is much like moving water,
IP address 192.168.0.xxx = The water well, tank or trough location, all water devices need to be on the yyy.yyy.yyy.xxx (sameFarm#.sameWell#.samePump#.differentdevice#)
Port Number = The water tap description
PGN = The type of water
LAN Cable / Wifi = The hose
Network Switch / Router = Flow Splitter
I don’t think it does a true broadcast . I’ll confirm tommorrow when I am in front of visual studio. I think it sends a message to a specific board over uDp. I’m assuming that’s we the MAC addresses are in the arduino code.
Someone that suggested doing a search for the pgn number. I think that will get me to the proper place. I’ll follow up with more info once I learn more.
This is how we are pulling off 64 sections, 4 cards with different Ip’s all staring at the same PORT to receive the same PGN at the same time. Then the individual module knows what 16 sections it is responsible for out of the 64 in the PGN message.
If you are connected by udp you can just put a print statement in the ino plug in your usb cable and see what info is being sent. Just found this out and it is handy!
With alot of help from commonRail i have used pgn_233 to create a XTE string. Added code in the .ino and send to serial5 and use ttl to rs232 to send out the XTE string.
I got this to work. The real trick is parsing the hex array from aog to a readable format. By default the uDp socket is expecting a string or “bag of bits” but once I got it to remain native I now can get and send messages.
Now aog can trigger the work switch and my planter monitor turns the planter in and off accordingly plus I can do rate control by speed.
Im working on the pcb now but will share once completed