Numerical value to CAN D1:D0 (Page 1 of 2)

I should of titled DEC2HEX.
My focus is on ADC due to the fixed sine wave from the project vehicle. I have to use an external amplifier to boost the analog volts up for the Canny Controller to wake up.

The PWM Counter is up and ready. Red LED blinks every 2 seconds.
Green LED stays illuminated once a pulse (digital or analog)is introduced.
No pulse coming out of Ch.0.

I am ready for next step.

Thank you Konstantin.

Please keep in mind - you can count sine or square pulses if only it cross 3VDC. Like on picture below.

Measuring frequency by CANNY with acceptable accuracy over a wide frequency range can be challenging, in common case.
Fortunately, this task has already been done before.
I have attached an example that you can adapt to your task:
- Different test frequencies are generated on channels 0..7.
- The CH8 is a freq meter.
- The results are sent to the CAN. Some LED indication added.
Hope this helps.

Hello Konstantin,

I am very close to a resolution but still testing.
Do the controller send TX by static or dynamic mode?

The controller appears to broadcast in what I describe as a static mode. Meaning, the first value TX is the only value that will be broadcast indefinitely.

Can the controller send TX in a live dynamic mode where a user can view the values change in real time view CAN bus? I am using SavvyCAN via ESP32 Dev PCB with a custom CAN shield to watch the TX sent by Canny controller on ESP32 RX.

I am trying to understand the Frequency Meter that is made by Composite block------ but,

Problem #1.
I can see a change from D0 of 0x00 going to D0 0xxx once the pulse input is added to Ch.8.
I cannot see a real time value of TX increase or decrease after the initial pulse input is introduced in regards to changes in pulse counter or changes made to your Frequency Meter values (Max Pulse Width; Pulse width step, ns; Range; etc). I am using an external pulse generator (Dakota Digital STA-1000)  rated at 60 mph which I can adjust the counter to have one fixed variable in this equation.   

Although, after some unrealized time has passed (in Frame Captured |Frames Per Seconds via SavvyCAN)  I notice the value of D0 changed on its own. This occurs randomly and I have not figured out how that is happening. Possibly due to a sleep / wake episode of Canny.

Do you know how the TX is periodically being changed?
Is the Frequency Meter counting indefinitely or is it resetting the count as an ABS module would during a drive cycle? It would be "interrupt" in C / C++.

Problem #2.
As I understand it, Composite block is a way to construct custom functions. I would like to construct a Composite block that is compatible to the code enclosed in the (Decoration) text notes.

For me to implement the Frequency Meter I must understand what each piece in the configuration is doing. I am trying to relate the frequency diagram to the code I have already tested with STA-1000 in Arduino with an ESP32 Dev pcb. Problem with ESP32 is that it is extremely sensitive to noise during testing but I did get an adjustable 60 mph reading via the Arduino monitor.

Do you have any build notes about the Frequency Meter for me to study?
Is it possible to construct my own Frequency Meter from my code provided in the notes?

Problem#3.
Once the input of Ch.8 is removed, the controller is still sending CAN frames viewed on SavvyCAN. A check of the CAN TX|RX via multimeter volts; oscilloscope reveals an active / dominate state TX. Concluding Canny controller will continuously TX once the initial input is implemented and continue TX after removal of the input signal from the circuit.

Thanks,

Today I realize a better way to ask my question looking at my STM32F407 settings.

Is there a way to set the Frequency Meter's - Counter Settings - in the form of;

-Prescaler : The amount to count 1 at each trigger number of 120. 120 being the tone ring tooth count of 120 per revolution cycle.

-Counter Mode: Counting up (rising) and down (falling).

-Time: How fast to count.

-Counter Period: Max number (120) to count up to 65535.

Or is it possible to build an Array?
Something of a counter with a Map / Array / a collection of variables that are accessed with an index number (the current count at a given time).

I added a Map block to the diagram which the results-- consistently are either 7F or 79 at the input of a consistent pulse.
Seems a bit more control or at the very least the results are predictable by adding the map.
Next issue would be a live reading (dynamic) instead of a static reading.

"Consistent results only when input trigger (pulse) is already attached.  "

Will work with a Delayed ON (DLN).

"But this diagram will only send the CAN message once and not periodically."

Oh............  I get it. Thank you.. I am a slow learner.
I went back to review the Docs.
I made adjustments.
Now I have two frames. I need to increase the quantity of TX frames and rate of change.
Update
*Transmitting Cancel on Error*cause a slow down. Soon as I changed to zero. The frames appeared in mass quantity but messages are not in real time. Meaning, the same values appear over and over regardless of change.
I am studying the TX Doc about periodically sending  but that looks like a static setup. I will see if I can manipulate two diagram (periodically TX and my original TX) for  better results.

Hello Konstantin,

Today I was able to perform several test.  Here is my findings and a question.

By changing Period and Duty of TX I was able to increase the TX traffic at a rate of 75 messages per second. I then tried a test with the live vehicle OBD2 PID reading but nothing.

I thought perhaps the TX rate was beyond what I saw the factory ABS module sending TX.  I reduced the TX rate to about 30 messages per second in accordance to what I observed on SavvyCAN.  Still no readings. I then had a thought to Use CAN Monitor 2.4 to inject the message via Run command instead of TX by diagram.

First I tried just the 0x215 ID and D1:D0 (0014), e.g 215 14 00. (I believe it should work with D0 but will try another day.)

Results: nothing in the OBD2 PID screen for speed.

Then I tried the complete 7 byte TX, identical to the ABS module.
215    14    00    81    59    81    59    07

**Note: bytes D3:D2; D5:D4 appears to be some type of counter. They run up at idle as if they are seconds and ms.
D7 is unknown.  D1 changes when the frequency generator button is pressed to increase the speed. Although the speed do not change until the second push of the button. A multi-meter check of the volts show slight increase at each press. **

Results were (25mph) satisfactory.
A repeat of 215    14    00    81    59    81    59    07 did not yield any results.
I had to cycle the key (12 power) once per TX message at the Run command line in CAN Monitor.

So it is now confirm that the controller forced message at Run command will cause a change.

My questions are:

1. What is the speed the "Run" command inject a TX message into the CAN bus?
2. Do you have a clue why a key cycle is required once per "Run" command TX message?

Also, as a note.
Once I adjusted the period and duty of TX,  "1" in the "CANx Transmitting Cancel On Error Register" was not required. I removed it completely and the TX data continue to change in real time.

I will retest sending one message in static form through a diagram to see the results.

Going down the rabbit hole from "Listen Only Mode in CAN and Message Validity."

Perhaps the reason why the engine computer did not acknowledge the speed message more than once is because I need to have the Canny controller set to also RX messages. Canny is not set to RX any messages in my diagram.

Have you ever heard of such an assumption? Is there a standard ACK message requirement to be placed in the diagram?

At the current level of my diagram build, I believe the controller is set to perform all requirements of TX transmission.

Edit*

The Kvaser websites states,

"an Acknowledgement Slot; any CAN controller that has been able to correctly receive the message sends an Acknowledgement bit at the end of each message. The transmitter checks for the presence of the Acknowledge bit and retransmits the message if no acknowledge was detected."

I assume that means that the receiving node will accept the data.

If the interface is initialized in Normal mode and filters are not enabled, then the controller accepts all messages. So the controller with your diagram will receive and ACK all correct messages on this baudrate.

I received your links by email, thank you.
I'll take a look.

Perhaps that may be the issue. The exact timing of the data being in correct sequence...

Sounds plausible.

As mentioned above,

"any CAN controller that has been able to correctly receive the message sends an Acknowledgement bit at the end of each message."

I am just wondering how does the transmitting node RX the Acknowledgement bit. Is it CAN ID or just part of the data line--therefore the controller must be setup to receive RX data. 

An online friend of mine from YouTube AlexSV, who is very good with using a gateway pcb for CAN bus modification says, "Using a gateway negates this effect completely."  He recommends using a gateway as part of testing before final project use.

I took a break from diagrams for a few days.