Anybus M40 SPI Issue

Respondida

Mohammad Kamrul Hasan

• 7 de mayo de 2024 11:39
• Editado

Hello

We are using Anybus CompactCom M40 Profinet module but we dont have the starter kit. We want to connect it to host using SPI. We have configured the example application and made necessary SPI and other related pin connection (DIP1 and DIP2 related pins are all connected to gnd and proper OM0..OM3 connection) with the host board. But unfortunately we can not see any data on the MISO line. we have now following questions.

• Do we need starter kit to enable the SPI?
• Is there any way to showing it up in the HMS IPconfig without the HOST (e.g. standalone mode)?

Thanks and best Regards

Kamrul Hasan

0

• Comentario oficial

  

  ALK

  • 8 de mayo de 2024 11:20

  I see that you've created a support ticket regarding your issue, where we will further pursue your matter.
• 

  Laura Sastre

  • 3 de julio de 2024 10:12

  Good day,

  We are encountering the same issue with our SPI communication: there is no activity on the MISO line. We suspect this might be due to a misconfiguration of our M40 Profinet IRT module.

  Our setup includes:

  • TWR-ABCC SPI interface board
  • NUCLEO-H753ZI development board from ST Microelectronics
  • HAEC example code and the appl_adimap_speed_example.c application

  We have kept the SPI settings as per the default configuration for the HAEC project. In our modifications to the abcc_drv_cfg.h file, we have set ABCC_CFG_POLL_ABCC_IRQ_PIN, ABCC_CFG_INT_ENABLED, and ABCC_CFG_MOD_DETECT_PINS_CONN to FALSE, as the initialization does not proceed otherwise. Additionally, we have set the operating mode to SPI.

  We observe that APPL_CyclicalProcessing() is reached, but ABCC_AnbState() always returns the default value of ABP_ANB_STATE_SETUP. The MS LED on the CompactCom M40 Profinet IRT module is lit, along with the activity LEDs on the RJ45 interface with a connector plugged in. The jumpers, hex knobs, and DIP switches on the TWR-ABCC board are set to their factory configuration, except for OM3, OM2, OM1, and OM0, which are set to 0 0 0 1 to operate in SPI mode.

  Our main issues are:

  1. What are we missing in the initialization process for the module?
  2. Why do we not see any activity on the SPI MISO line?

  Your assistance in resolving these issues would be greatly appreciated.

  Yours sincerely,

  0
• 

  ALK

  • 4 de julio de 2024 13:22

  Hello Laura,

  on the one hand, you write that the MS LED is lit (I suppose green?) and the L/A LEDs on the Ethernet connector showing activity.  This means that the ABCC40's state has reached WAIT_PROCESS.  On the other, you don't record any signal on the SPI MISO line.

  Combining these two facts, I deduce that you might have a wrong setting of the OM pins.  OM0-OM3 are either all connected to LOW or all to HIGH.

  Could you add a breakpoint where you keep the module in reset state and measure the voltages of the OM pins?

  I suggest that you open a ticket at our support portal in order that we investigate the problem in more detail.

  0
• 

  Laura Sastre

  • 5 de julio de 2024 09:08

  Alk, thanks for your prompt reply and suggestions. Issue solved. It was indeed a SW adaptation / misconfiguration issue. We had misunderstood the way by which the Operating Mode was being set by the microcontroller and also set by the OM DIP switches, as they can be configured independently of each other. If other issues were to arise we would contact you via a ticket in the support portal.

  Yours,

  0
• 

  ALK

  • 5 de julio de 2024 09:36

  Hi Laura,

  that is great to hear, thank you for the feedback.

  0

Iniciar sesión para dejar un comentario.