How to use tcp transport large data? about vsomeip HOT 6 CLOSED

Hello KudoWu,
As I can see from your configuration, it seems that you define both unreliable(UDP) and reliable ports (TCP).
You can try, remove 'unreliable' and hopefully will work.

from vsomeip.

I also try to use someip-tp, but it has the smae problem.

    "services": [
        {
            "service": "0x80e9",
            "instance": "0x814e",
            "unreliable": "30510",
            "events": [{
                "event": "0x80fe",
                "is_field": "false",
                "is_reliable": true
            }],
            "someip-tp": {
                "service-to-client": [ "0x80e9", "0x80fe"]
            }
        }
    ],

from vsomeip.

Unfortunately, you provide zero information on what you actually do. Did you set the reliable flag on the message you are trying to send (message_base::set_reliable or at creation time)?

from vsomeip.

Hello KudoWu, As I can see from your configuration, it seems that you define both unreliable(UDP) and reliable ports (TCP). You can try, remove 'unreliable' and hopefully will work.

Hello, Billkouts96
Thank you for your help! Actually, I have tried to remove 'unreliable' , but I had the other problem:

2024-08-30 19:50:00.692114 [info] endpoint_manager_impl::create_remote_client: 192.168.3.208:30501 reliable: 1 using local port: 0
2024-08-30 19:50:00.739588 [warning] create_eventgroup_entry: Cannot create subscription as unreliable endpoint is zero: [80e9.814e.80fc]
2024-08-30 19:50:00.741354 [warning] create_eventgroup_entry: Didn't insert subscription as subscription doesn't match reliability type: [80e9.814e.80fc] 2
2024-08-30 19:50:00.689206 [warning] create_eventgroup_entry: Cannot create subscription as unreliable endpoint is zero: [80e9.814e.80fc]
2024-08-30 19:50:00.691456 [warning] create_eventgroup_entry: Didn't insert subscription as subscription doesn't match reliability type: [80e9.814e.80fc] 2
2024-08-30 19:50:00.686764 [warning] create_eventgroup_entry: Cannot create subscription as unreliable endpoint is zero: [80e9.814e.80fc]
2024-08-30 19:50:00.689158 [warning] create_eventgroup_entry: Didn't insert subscription as subscription doesn't match reliability type: [80e9.814e.80fc] 2
2024-08-30 19:50:01.433518 [info] REMOTE SUBSCRIBE(0000): [80e8.814d.80fc] from 192.168.3.208:35097 reliable was accepted

from vsomeip.

Unfortunately, you provide zero information on what you actually do. Did you set the reliable flag on the message you are trying to send (message_base::set_reliable or at creation time)?
I'm sorry. Actually, I don't find any interface that I can set reliable.
Here's your response refined in English:

Hello, lutzbichler, thank you for being willing to help me!

I'm very sorry for not providing enough information earlier. First, I would like to clarify that I am using CommonAPI C with SomeIP+ vsomeip, and I am trying to transmit large amounts of data within the PublishEvent. I haven't found any interface to set the reliable flag. I'm wondering if there's a significant difference in how the reliable flag is handled between CommonAPI C SomeIP and the standard vsomeip interfaces.

Additionally, I noticed in the "CommonAPI-C---SomeIP-in-10-minutes" example that the method can have SomeIpReliable = true set in the fdepl file. So, I added a similar configuration in my own fdepl file:

define org.genivi.commonapi.someip.deployment for interface xxxxx {
    SomeIpServiceID = 33001

    broadcast FirmwarePublish {
        SomeIpEventID = 33021
        SomeIpEventGroups = { 33020 } 
        SomeIpReliable = true
    }
}

That's great! I can use tcp transport large data. So, if there are other methods to set_reliable in CommonAPI C SomeIP? Thank you!

from vsomeip.

If you deploy your broadcast to be reliable ("SomeIpReliable = true") CommonAPI will do the setting of the reliable flag in vsomeip for you. Setting the flag manually only is needed if you use the vsomeip API.

As I think the problem is solved, I will close the issue.

from vsomeip.