How to get use cases datas from remote device

[SmartlabEnedis]

Hello Everyone,

We implemented a software compliant with OPEV test case using eebus-go.
The software communicates with EVBox Livo wallbox or Mennekes Amtron.

When the software is connected with the EVSE the use cases datas are read from remote device (with nodeManagementUseCaseData function) without any request from our software.

I want to get use cases datas information in an object compliant with NodeManagementUseCaseDataType (defined in spine-go model).
I managed to send the request through remote service using sender interface and Request() method but i don't know how to process the received message. I tried to use ProcessCmd() from local device interface but it doesn't work as expected.

Here is a sample of the method reading use cases informations :

func (e *EnergyGuard) readUsecasesInfos() {
	e.Info("Read use cases infos")
	localDevice := e.service.LocalDevice()
	if localDevice == nil {
		e.Error("No local device found")
		return
	}
	localEntity := localDevice.EntityForType(ENTITY_TYPE)
	if localEntity == nil {
		e.Error("No local entity found")
		return
	}
	localFeature := localEntity.GetOrAddFeature(model.FeatureTypeTypeNodeManagement, model.RoleTypeClient)
	if localFeature == nil {
		e.Error("No local feature found")
		return
	}
	localFeatureAddress := localFeature.Address()

	var remoteFeatureAddress *model.FeatureAddressType
	remoteFeatureAddress = nil
	remoteDevice := localDevice.RemoteDeviceForSki(e.config.EEBUS.RemoteSKI)
	if remoteDevice == nil {
		e.Error("No remote device found")
		return
	}
	remoteEntities := remoteDevice.Entities()
	for _, remoteEntity := range remoteEntities {
		remoteFeatures := remoteEntity.Features()
		for _, remoteFeature := range remoteFeatures {
			if remoteFeature.Type() == model.FeatureTypeTypeNodeManagement {
				remoteFeatureAddress = remoteFeature.Address()
			}
		}
	}
	if remoteFeatureAddress == nil {
		e.Error("No remote feature address found")
		return
	}
	remoteSender := remoteDevice.Sender()
	if remoteSender == nil {
		e.Error("No remote sender available")
		return
	}
	remoteFunction := model.FunctionTypeNodeManagementUseCaseData
	remoteUsecaseDatas := model.NodeManagementUseCaseDataType{}
	remoteCmd := []model.CmdType{{
		Function:                  &remoteFunction,
		NodeManagementUseCaseData: &remoteUsecaseDatas,
	}}
	remoteAckRequest := false
	e.Infof("Sending request for function : %v", remoteFunction)
	msgCounter, err := remoteSender.Request(model.CmdClassifierTypeRead, localFeatureAddress, remoteFeatureAddress, remoteAckRequest, remoteCmd)
	if err != nil {
		e.Errorf("Send request %v failure : %v", remoteFunction, err)
		return
	}
	cmdClassifierType := model.CmdClassifierTypeReply
	datagram := model.DatagramType{
		Header: model.HeaderType{
			SpecificationVersion: &EEBUS_SPECIFICATION_VERSION,
			AddressSource:        remoteFeatureAddress,
			AddressDestination:   localFeatureAddress,
			AddressOriginator:    remoteFeatureAddress,
			MsgCounter:           nil,
			MsgCounterReference:  msgCounter,
			CmdClassifier:        &cmdClassifierType,
			AckRequest:           &remoteAckRequest,
			Timestamp:            nil,
		},
		Payload: model.PayloadType{
			Cmd: remoteCmd,
		},
	}
	e.Infof("Process response for function : %v", remoteFunction)
	err = localDevice.ProcessCmd(datagram, remoteDevice)
	if err != nil {
		e.Errorf("Cannot process %+v response : %+v", remoteFunction, err)
		return
	}
	e.Infof("Use cases datas : %+v", remoteUsecaseDatas)
}

Is it possible to retreive the use cases information ? From a general perspective, what is right way to read a specific function from the eebus model and how can we get the datas associated with the function in the corresponding object ?

Thank you !

[DerAndereAndi]

Hi,

why are you trying to send a usecase reply request? The stack already handles requesting and replying to usecase requests. There is no need to do this yourself.

Check this code to figure out if a remote device claims supports a usecase: https://github.com/enbility/eebus-go/blob/dev/usecases/usecase/usecase.go

[JBO5m4r7135]

Hi Andreas,

I try to send a use case reply request to make sur OPEV use case is handled by the EEBUS device. When i used the method RemoteEntitiesScenarios from the use case object it only works when the vehicle is connected to the wallbox. Whereas when I send the use case reply request with the previous code it works even when the vehicle is not connected.
Is there a better way to make sure OPEV scenarios are handled before the vehicle is connected ?

[DerAndereAndi]

Please check the OPEV specification documents. OPEV is only supposed to work WHEN an EV is connected. It will not work if no EV is connected.

[JBO5m4r7135]

I reread the OPEV specification and i understand that it is only supposed to work when an EV is connected, but i just want to detect as soon as possible if the EEBUS device (in my case the wallbox) is OPEV compliant. This check was done for the implementation of the OPEV scenario 3 for the energy guard but may be it is not necessary to detect that kind of incompatibility.