Communication between DP210 and microcontroller MC24-XXX

[fhm1963]

I need to know how communicate a display DP210 and a micro MC24-XXX. Can anyone tell me where I could find info of it?

[Jakob]

If you use the standard CAN-tx and CAN-rx function blocks, you will be well on your way.
Just remember, all CAN-messages are type U8, and you will have to convert and check if your signals valid.

[Jakob]

?

[Maxim]

Hello,

This is an old topic but it is just what I need.

I have almost the same setup and I need to do exactly the same but I can't get this to work. Would it be possible to help me out on the connections that have to be made on the block?
The goal of the setup is to use the soft keys on the display to control the program in the controller.

This is the correct block?


I'm sorry but I have very little knowledge of this software, I was thrown in this due to illness of a colleague.

Thanks in advance.

[Jakob]

Yes that is the right component for receiving a CAN message.
The RX function should be in the controller program.

Have you looked at the help file for this component, there are usually some helpful examples there.

[Jakob]

Here is a simple setup for a can-bus connection.

[Maxim]

Thank you so much, Jakob.
Got the network to communicate.
Only when I want to use a signal coming from a joystick, receive and view it on the display, I get: "error 15: [chpargu1] NET TYPE REDEFINED, SIGNAL: {AN72/} Type1: (S16) Type2: Bool.

[Jakob]

Your welcome

The Error 15 you have means that you have connected a S16 type signal to an already defined Bool type signal.
Usually the compiler will tell where the conflict is located, or at least give a hint.

Like this one.
*** ERROR 15 ***  [chpargu1]   NET TYPE REDEFINED, SIGNAL: {AN217/} TYPE1: {U16} TYPE2: {CBOOL}
          DP250-01-01-0X-05-00T!TOP!Application!MudFlow!Input_scale (262,25)

It links and writes what page and location on the page (262,25).

[Maxim]

Hmm,
When I do that is just links me to the 'define screen' block..

[Neil]

Hi

In the screen editor/Screen Manager Tab, click on DataValue and pick up your BusMember1 port.
Personally I would call this signal what it is, if a Joystick signal that’s what I’d call it.

regards Neil

[Maxim]

Problem Solved, communication working now.
Value had to be %5d instead of %d because the joystick value can positive and negative.

Thanks everybody!

[Jakob]

Nice.
That is the important thing

If you plan on making a larger project, I would agree with Neil that naming signals correctly is quite important for future understanding of the program.

regards Jakob

[Maxim]

I've done that now, all members always have understandable names.

But now I have a new problem, when I want different pages to come up after a selection has been made (using buttons) I need my buttons again in that submenu.
So I tought I could use a counter including this setup (looks messy, just sketching to try it out) to enable the buttons for the active menu only.


But this doesn't seem to work.
Any other ideas?

Regards,
Maxim

[Neil]

Hi Maxim.

See the attached DP600 Simulator template it demonstrates one way how you can call on different pages with buttons.
Please be aware the code contained is snippets of more advanced code I have used in projects.
You are responsible for the code you develop.
I tend to use the simulator a lot to test code snippets, view images etc., it’s a great tool for development.
Final code should always be tested in hardware of course.

Compile the P1P and run the generated P1S file via the simulator software. If you want to latch a screen button, press the shift key when you click the button with your mouse.

Regards Neil.