|
Re: SPI on Raspberry Pi | 4DIAC [message #1818010 is a reply to message #1817906] |
Wed, 04 December 2019 08:11   |
|
Hi,
you can have a look at the FB creation tutorial and their specifically on the Service Interface Function Block section. What kind of CAN communication do you like to do? Is it like publish/subscribe then pelase read the documentation section on the communication architecture. If it is I/Os then I can only offer you code examples. Especially the Embrick module should be similar to what you need.
I hope this helps to get you started.
|
|
|
|
Re: SPI on Raspberry Pi | 4DIAC [message #1818048 is a reply to message #1818021] |
Wed, 04 December 2019 18:18   |
|
The reason I'm asking is mainly target towards how you would like to represent your requried CAN communication in IEC 61499. The most flexiblity you have when you are using a Publish subscirbe interface where you send plain CAN messages. However then you have to write FBs that will generate the messages and do all the padding and stuff (i.e., CAN messages have at max 8 bytes).
If you have other use cases you may want to do more in C++ code and have a simpler interface on IEC 61499 side.
|
|
|
|
Re: SPI on Raspberry Pi | 4DIAC [message #1818055 is a reply to message #1818054] |
Wed, 04 December 2019 21:10   |
|
With the information given so far I would say both is possible. However if on the other end of the CAN only IO modules or IO module like devices are connected I think the IO concept is the better solution.
However for starting the pub/sub approach may be easier (especially better documented)
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.02504 seconds