Some tips for working with Canny products

Another feature that is really helpful for larger diagrams is the ability to name segments, then you can call on that signal from anywhere in the diagram without having to connect them.

In this diagram I am sending out several different messages on CAN, some of which change depending on whether the engine is running.  I have a section of the diagram which determines whether or not the engine is running, and another section which creates an index number to synchronise the various parts of the message that need to be sent out.

Rather than having connections crossing all over my diagram and making it look confusing I have named the commonly used ones, and then just call on them when I need them.  This also helps to keep clear what the signals are, so makes it easier to troubleshoot and modify.

It took me a while to realise this function was available, so I thought I would mention it here!

Cubic,

Would you  be willing to share your CFD file?  I'm always looking for ways to simplify my coding.

Vic Moses

i was just looking for some examples of how you created "subroutines" by naming segments and then did the "go to" to use them.

I'm not interested in any other logic that you might consider proprietary, so you could just delete most of the electrical function of any diagram.

Sorry I didn't see your response earlier  BTW, are you in NZ or is the moniker for something else?

Another tip that might help some people who are new to this is to use the red and green LEDs on the Canny board to help troubleshooting when you're having issues.  I've found this to be the only way to find mistakes when I'm working with the built in CAN filters, as it's not possible to simulate these filters in the simulator (that I'm aware of!).

For example, I was working with my 5.2 to block some messages between two devices and dynamically modify others.  I couldn't figure out why the initial modification would work, but it would not change to the second stage of modification once the engine started.  So I temporarily connected the green LED to the output of my test to see if the message was received (as per screenshot), and this confirmed the message was being received and recognised.  I then did another test and connected it to my "Engine Running" signal, and this confirmed the test was working also.  Since I now knew all of this was working I could look elsewhere, and realised I had overlooked the gateway configuration update signal.

If you are having trouble with a program and the simulator is not practical to diagnose it, consider whether there are any parts of the diagram you can check are working via the lights, to help you narrow down your search for the fault.

Usually, Inversion block is used only to increase the readability of the diagram. Instead, you can invert any of block's input or output via context menu on block's pin.

You need right-click exactly on pin name or triangle pin symbol, for get the context menu for pin. In this case the result will not depend on whether the pin is connected or not.