VirtualTerminal ObjectPool

[Drantum]

Hello great project, I'm currently experimenting a bit with the VirtualTerminal example. But I'm wondering how you created the ObjectPool.cpp file, since I can only create .iop files with my Editor and haven't found any way to convert them.

[ad3154]

For the big array in there, I just took the .iop file, and ran it through a tool like this free one
to convert it to an array, and pasted it into ObjectPool.cpp. The macros at the top are something that my editor exported to a file for me in a .h file and I just pasted in. If your pool is small, you might be able to just add the definitions you need at the top if your editor doesn't export .h files

[Drantum]

Thank you very much for the quick response. I will try it

[YuriyStukalo]

Hello great project, I'm currently experimenting a bit with the VirtualTerminal example. But I'm wondering how you created the ObjectPool.cpp file, since I can only create .iop files with my Editor and haven't found any way to convert them.

Hello, can you say what software do you use for creating .iop file and how I can get the software. Thanks.

[Drantum]

Hi, i am using the Jetter ISO Designer in the free Version you can create 100 Objects what ist currently
enough for me

https://www.bucherautomation.com/iso-designer/sw10133#product-downloads

[YuriyStukalo]

Hello, thank you for your quick response.

I would like to ask if you—or perhaps someone else—might be able to help me.

I'm trying to launch the example VT application on a John Deere G5 monitor. This is my first experience working with the ISOBUS stack and a VT project. I'm using a Teensy 4.1 board, and I’ve built the AgIsoStack-Arduino VT example.

After launching it, here's what I see in the log:

Start Board Ver 1.2
[Debug]: [NM]: A control function claimed address 220 on channel 0
[Debug]: [NM]: A control function claimed address 240 on channel 0
[Debug]: [NM]: A control function claimed address 28 on channel 0
[Debug]: [NM]: A control function claimed address 251 on channel 0
[Debug]: [NM]: A control function claimed address 237 on channel 0
[Info]: [NM]: Partnered control function with name 000000000000000lx has claimed address 69364800 on channel 2684361984.
[Debug]: [NM]: A control function claimed address 210 on channel 0
[Debug]: [NM]: A control function claimed address 247 on channel 0
[Debug]: [NM]: A control function claimed address 42 on channel 0
[Debug]: [NM]: A control function claimed address 238 on channel 0
[Debug]: [NM]: A control function claimed address 248 on channel 0
[Info]: [AUX-N]: New auxiliary input device with name: 11529362380696046808 and model identification code: 65535
[Debug]: [AC]: Internal control function 000000000000000lx has arbitrarily claimed address 538984080 on channel 2950692866
[Info]: [VT]: No version label from the VT matched. Client will upload the pool and store it instead.
[Debug]: [ETP]: New tx session for 0x0E700. Source: 128, destination: 38
[Debug]: [TP]: Received Request To Send (RTS) with a CTS packet count of 255, which is greater than the configured maximum of 16, using the configured maximum instead.
[Debug]: [TP]: Received Request To Send (RTS) with a CTS packet count of 255, which is greater than the configured maximum of 16, using the configured maximum instead.
[Debug]: [TP]: Received Request To Send (RTS) with a CTS packet count of 255, which is greater than the configured maximum of 16, using the configured maximum instead.
………………….

The log info repeating continuously:
[Debug]: [TP]: Received Request To Send (RTS) with a CTS packet count of 255, which is greater than the configured maximum of 16, using the configured maximum instead

We see some device in the G5 monitor, but it connecting/disconnecting periodically.

Second I tried to change the minimal object pool which was created by ChatGPT:

const uint8_t VT3TestPool[] = {
0x10, 0x02, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00,
0xFF, 0xFF, 0xFF, 0xFF, 0x00, 0x00, 0x00, 0x00,
};
const unsigned int VT3TestPool_len = 16;

log is next:
[NM]: A control function claimed address 251 on channel 0
[NM]: A control function claimed address 28 on channel 0
[Info]: [NM]: Partnered control function with name 000000000000000lx has claimed address 69364800 on channel 2684361984.
[NM]: A control function claimed address 237 on channel 0
[NM]: A control function claimed address 210 on channel 0
[NM]: A control function claimed address 247 on channel 0
[NM]: A control function claimed address 42 on channel 0
[NM]: A control function claimed address 238 on channel 0
[NM]: A control function claimed address 248 on channel 0 [Info]:
[AUX-N]: New auxiliary input device with name: 11529362380696046808 and model identification code: 65535
[AC]: Internal control function 000000000000000lx has arbitrarily claimed address 538984128 on channel 2950692866
[Info]: [VT]: No version label from the VT matched. Client will upload the pool and store it instead. [TP]: New tx session for 0x0E700. Source: 128, destination: 38
[TP]: Session Closed [TP]: Completed tx session for 0x0E700 from 38
[VT]: Object pool 1 uploaded.
[Error]: [VT]: Store Version Response Timeout
[Info]: [VT]: Resetting Failed VT Connection [Info]:
[VT]: No version label from the VT matched. Client will upload the pool and store it instead.
[TP]: New tx session for 0x0E700. Source: 128, destination: 38
[TP]: Session Closed [TP]: Completed tx session for 0x0E700 from 38
[VT]: Object pool 1 uploaded.
[Error]: [VT]: Store Version Response Timeout
[Info]: [VT]: Resetting Failed VT Connection

Response from ChatGPT:

✅ What’s Working Now
Log Entry Meaning
[VT]: Object pool 1 uploaded. ✅ The object pool was completely received and parsed by the VT. This means your Teensy successfully sent the entire .iop data using ETP/TP.
[TP]: Completed tx session... ✅ ETP session finished cleanly — no data loss, no timeout mid-upload.
[AUX-N]: New auxiliary input device... ✅ Your object pool contains an AUX-N section, and the VT recognized it.
[AC]: Internal control function ... claimed address... ✅ Your ECU (Teensy) claimed and retained a valid CAN address.
[Partnered control function...] ✅ VT successfully partnered with your ECU — good handshake.

❗ Still Failing
Log Entry Problem
[Error]: [VT]: Store Version Response Timeout ❌ After the VT receives your object pool, it should send a Store Version response. That didn’t happen. Your Teensy waits… then times out.
[Info]: [VT]: Resetting Failed VT Connection ❌ Your VT client (on Teensy) resets and restarts the process.

🧠 What This Means
The VT has received and parsed your object pool — but it doesn't like something, so it doesn't send back the Store Version Response (PGN 0xE300).

🔍 Most Likely Reasons
1. Missing Required VT Sections
◦ Your pool might be too minimal. If it doesn’t include a:
▪ Working Set
▪ Soft Key Mask
▪ Background
▪ Main object (e.g. Button, Data Mask)
◦ Then the VT may silently reject it after parsing.
2. Missing/invalid Working Set assignment
◦ The VT should send PGN 0xE803 to assign you a working set. If this is not handled or replied to, Store Version might be skipped.
3. Pool is not VTDesigner-compliant
◦ VTs like John Deere G5 may require proper format with required sections created in VTDesigner, not hand-assembled.

I tried with different object pool which generated ChatGPT, but did not get working result.

My questions is next:

1. How I can get the minimal pool object which make sure that should work on the John Deere G5 monitor?
2. What can be issue what the original pool object from the example which did not work on my system (John Deere G5 monitor)?
3. Can it be related with high loaded CAN bus and need add some filters for Teensy board (see picture below, like for me the CAN bus quite high loaded, but maybe it normal for the ISOBUS stack):

Thank you very much for your time and any advice you can provide!

[Drantum]

Hello,
I tried it myself today as well. We have a John Deere with a Gen4 display, and it's exactly the same problem there. I don’t know exactly what’s causing it yet, but I will keep testing it. Im just starting with isobus too

Right now, unfortunately, I don’t have much time because we still have a lot to do.

[Drantum]

Open-Agriculture/AgIsoStack-plus-plus#511

I found this. I haven't tested it yet but maybe it helps

[YuriyStukalo]

Hello,

I added the following two lines of code before starting the CAN interface, and it helped — the example started working:

isobus::CANNetworkManager::CANNetwork.get_configuration().set_number_of_packets_per_dpo_message(255);
isobus::CANNetworkManager::CANNetwork.get_configuration().set_number_of_packets_per_cts_message(255);

I haven’t yet analyzed in detail why this was necessary, as I’m still new to ISOBUS. I plan to research it more deeply when I start working on my own simple application.

Thank you very much for your help

[YuriyStukalo]

Hello and thank you very much, I will try it tomorrow and will do update here about result.