We are in the process of creating instructions on how to do this, the software was released before we have had time to complete them. In principal create an xml file, like the one attached, based on the xml schema file ProtocolPlugin.xsd
There are two methods to create decoders, using XML based on the schema will work for simple protocols, using a C# dll can be used for more complicated protocols which may be applicable in this case.
I am waiting for some more information on the second method and will be posting some details shortly.
Martyn wrote:There are two methods to create decoders, using XML based on the schema will work for simple protocols, using a C# dll can be used for more complicated protocols which may be applicable in this case.
I am waiting for some more information on the second method and will be posting some details shortly.
Hi, Martyn. Not to bug you guys, but it's been almost 2 months since we'd be hearing about the details "shortly".
Interest is high, because these new capabilities will be very welcome, and add considerably to the power of Pico for protocol decoding. The fact that it's on it's way is good news. The fact that it's already in place in existing software, but we're just lacking documentation on using it is a bit frustrating.
After some feedback with regards to the Custom Serial Decoding, we are revisiting the best approach to provide a user friendly method of setting up protocols. This will require further development work so this option will not be available until this work is completed. Sorry for the delay.
There are two methods to create decoders, using XML based on the schema will work for simple protocols, using a C# dll can be used for more complicated protocols which may be applicable in this case.
and
We are in the process of creating instructions on how to do this, the software was released before we have had time to complete them.
Then apparently documenting the already completed software was abandoned, since:
...we are revisiting the best approach to provide a user friendly method of setting up protocols. This will require further development work so this option will not be available
So now we've gone from "two methods" to NO mechanism available, and 5 months later there's no time-frame for the next one? I'm having trouble understanding how this is "the best approach"?
We are still working towards a release with serial decoding, hopefully not too long now before a beta release.
The code has been completely rewritten from the ground up to provide better support for the existing protocols, as well as being able to support new protocols moving forwards.
We are still working towards a release with serial decoding, hopefully not too long now before a beta release.
Thanks! I'll keep an eye out for it.
The code has been completely rewritten from the ground up to provide better support for the existing protocols, as well as being able to support new protocols moving forwards.
That's good news... especially since the serial decode capabilities of ps6 are so heavily promoted as a major selling point.
It's really important for these capabilities to be solid, and work properly. Which from my readings in this Forum, is apparently not currently the case. It will be good to have the reality match the advertising claims.
Once you have the custom decoder functionality in beta, feel free to give me a shout. I have a lot of expertise with quite a few comms protocols, and CAN in particular (J1939, CANOpen, ISO-15765, UDS, ISO-14229, etc.). So I may able to give you a boost in that area, that competing products wouldn't have.