Skip to main content

Posts

Showing posts with the label canopen

Decoding CAN/CANopen logs using your favorite AI prompt

One of the most useful things about text-based AIs like GPT is that you can hand them a piece of data and ask them what they see.  Kickdrive's own support bot can provide great answers, at least for a limited portion of a CAN Monitor log, since the maximum input length for our support bot is limited. For the little test below, I relied on a regular ChatGPT prompt, and the result was almost spot on. In short... TL;DR GPT or any other (coding) AI is an extremely efficient way to look at CAN bus frame data. It will give you all the high-level information, and more.  BUT - you as the developer should still verify what you are doing and know the specifics. Because if the log contains unexpected / unusual data - in our case a vendor specific object number in the 0x3500 range - GPT will present an incorrect answer with the same confidence as a real answer. The ChatGPT prompt Here is the prompt I used after a  Kickdrive  customer asked about how the  Scan  functio...

Free CANopen windows tool updated (and fullmo Kickdrive, too)

During the winter break we freshened up our Kickdrive software releases. So new versions v2.0 are available for  Kickdrive Zero, our freeware CANopen windows tool. fullmo Kickdrive, which allows you to do so much more .  You can grab a copy of the updated software from here: http://kickdrive.de/en/index.html?download.htm Changes include: Added support for CANopen data types REAL32 and  OCTET_STRING  Windows 10 compatibility adjustments(especially for fullmo USB2Drive hardware) Baud/Node scan uses now "Reset Nodes" instead of "Start Nodes" Object Editor: Export actual values to .xdc and additional formats (.csv, .cdcf, .txt) The UI Panel now uses the updated QML2 language Other minor corrections and fixes. For a complete overview see the Kickdrive Release Notes .  We'd like to thank the Kickdrive users for their encouraging and helpful feedback. We do realize that Kickdrive releases come a bit slowly. This is because we are v...