Personal Data

Username:
laruso
Joined:
2021-01-14 14:47:45+00:00

Projects

  • No projects to display.

Skills

  • No skills entered.

User Activity

  • Posted a comment on discussion Forge 🇬🇧 on CODESYS Forge

    Dear Ingo, if I get you right there are two kinds of drivers: Driver (only consists of „connector“ like in the SPI template) CODESYS I/O driver (consists of „connector“ for logic access, and in adddition "IBase", "ICmpIoDrv" and "ICmpIoDrvParameter" to properly implement the device into CODESYS) The driver should works as it is, but the use could perhaps be a little bit more complicated because addressing the instance calls/variables. The CODESYS I/O driver works too, but a little bit more comfortable...

  • Modified a comment on discussion Runtime 🇬🇧 on CODESYS Forge

    @ ojz0r: Thanks for your offer to help me out. After spending several hours checking the code, the only missing thing was to enable/pinmux the SPI in the device (BeagleBone Black) I did: - changed the library according to the already given MCP3008 (available as a package over CODESYS Forge) and the MCP3202 (thread "Raspberry Pi: List of available drivers / libraries" in CODESYS forum), to fulfill the needs of the MCP3204. In the library code I did (as usual) documented the relevant code by comments....

  • Posted a comment on discussion Forge 🇬🇧 on CODESYS Forge

    From the description of writing an driver for a ADC via SPI I do only need a FB that contains the connector (also from SPI the template). Within the MCP3008 template there is the connector PLUS a additional FB contains "IBase", "ICmpIoDrv" and "ICmpIoDrvParameter". So what is the right way how to do it? Are both FBs needed? Why the temperature template contains only the connector? The unique ID was already considered. On the other side there are many deviations regarding the documentation, but that...

  • Modified a comment on discussion Forge 🇬🇧 on CODESYS Forge

    I want to write a (correct) driver for the MCP3204! I downloaded a few templates and codes related to the MCP3008 and MCP3202 and merged everything together and it works. But now I wanted to read all the documentation here to fully correct the code and put it on the CODESYS Forge, and I struggle. For an SPI I/O driver: do I have to follow the SPI guidelines and/or follow the generic guidelines and/or follow the Driver FB guidelines??? It's very confusing to me. At the beginning there are three sentences,...

  • Posted a comment on discussion Forge 🇬🇧 on CODESYS Forge

    I want to write a (correct) driver for the MCP3204! I downloaded a few templates and codes related to the MCP3008 and MCP3202 and merged everything together and it works. But now I wanted to read all the documentation here to fully correct the code and put it on the CODESYS Forge, and I struggle. For an SPI I/O driver: do I have to follow the SPI guidelines and/or follow the generic guidelines and/or follow the Driver FB guidelines??? It's very confusing to me. At the beginning there are three sentences,...

  • Posted a comment on discussion Runtime 🇬🇧 on CODESYS Forge

    Anything new on your plan?

  • Posted a comment on discussion Engineering 🇬🇧 on CODESYS Forge

    To change the pending EMCY error the master detected, the device have to send an "emergency reset". Please see the doku for this function block. The EMCY error you get from CiA405.RECV_EMCY_DEV seems to be the recording at the master, NOT the still pending error at the device. My device only sends out an EMCY over COB-ID 81 (for node-id 1) once, if there is a rising edge of an error. Nevertheless if the errors is still pending or not. So only one message on CAN bus. This results in not being the...

  • Posted a comment on discussion Deutsch 🇩🇪 on CODESYS Forge

    So wie Ihr euch das vorstellt kann es nicht funktionieren! Erklärung: Ein kommender Fehler erzeugt über dessen positive Flanke eine EMCY Nachricht, die das Device an den Master schickt. Die Nachricht wird auch nur einmal geschickt, selbst wenn der Fehler noch anliegt oder schon behoben ist. Diese Nachtricht wird vom Master gespeichert und mit dem Funktionsblock CIA405.RECV_EMCY_DEV abgeholt. Hinweis: Es wird nicht der EMCY Fehler aus dem Device ausgelesen, sondern der letzte EMCY Fehler aus dem Master!...

View All