Closed terraphantm closed 7 years ago
Thanks, I will check that, I expect that the empty argument is simply removed.
The problem are not the parameters but the command itself. set_parameter tries to set parameter for the EDIC interface, what is not possible with EdiabasLib. I have changed the error code to "concept not implemented".
I'm not using an EDIC interface (using the same OBD interface in both instances), and communications stop working if I raise the module's baudrate without also sending the "set_parameter" command (which I can't do in EdiabasLib).
As far as I can tell, it checks if the interface is an Edic interface so that it can send stop command to the Edic.
If I use the "set_baudrate" command, which does the same Edic check, the communications do start working at the new baudrate, but not all PRGs have the set_baudrate command.
Hello, I don't have the 08MSV70.prg file, so I used flash.prg fro testing. Could you send the file to ulrich@holeschak.de? I may case set_paramter tries to set the communication paramater for concept 0, which is EDIC, this is rejected.
Fixed pars handling for empty arguments.
I've noticed that EdiabasLib doesn't handle jobs where some of the arguments are left empty. Below I've attached examples of the Ediabas vs EdiabasLib behavior in tool32:
EdiabasLib
Ediabas 7.3.0