Skip to main content
Pmond
Associate II
August 7, 2019
Question

STEVAL-IDP004V1 (master-board) either not communicating to PC through RS485 or not detecting a sensor out of the box

  • August 7, 2019
  • 8 replies
  • 4480 views

Hi,

We have recently purchased the STEVAL-BFA001V1B kit and planned to connect the STEVAL-IDP004V1 to the STEVAL-IDP005V1 as we planned to use the STEVAL-IDP004V1 GUI interface to allow for streaming off data from the sensor.

The manuals we have used are:

https://www.st.com/content/ccc/resource/sales_and_marketing/presentation/product_presentation/group0/47/a2/91/a0/fe/ca/42/89/steval-bfa001v1b_getting_started_guide/files/steval-bfa001v1b_quick_start_guide.pdf/jcr:content/translations/en.steval-bfa001v1b_quick_start_guide.pdf

https://www.avnet.com/opasdata/d120001/medias/docus/190/STEVAL-BFA001V1B%20User%20Manual.pdf

They make reference to updating the firmware of the STEVAL-IDP005V1 through dragging across "STEVAL-IDP005_ConditionMonitoring_IOL_v1.1.0.bin." The GUI after doing this results in the following error:

"[>> TX] START

[ERR] Command ERROR (TRASMISSION FAIL) - RECEIVED DATA

[>> TX] COMMAND END

[ERR] Command ERROR (TRASMISSION FAIL) - RECEIVED DATA

[ERR] Communication with STEVAL-IDP004V1 BOARD failed.

Please reset the BOARD and the GUI and retry."

The 2nd manual refers to disconnect the assembly that we tried with no hope of any differences.

The STEVAL-IDP004V1 itself has 4 green flashes lights for each sensor (sensor 1, sensor 2 and so fourth) that has not changed implying that the sensor (STEVAL-IDP005V1) is not detected as a sensor.

Additionally, we are unable to determine whether there is any communication between the STEVAL-IDP004V1 and the PC.

We have uploaded another project (Condition_Monitoring_SRV) through the System Workbench by running/debugging and then connected through putty which following a reset of the STEVAL-IDP005V1 means data is streamed from the sensor.

After changing the baud rate to 38400, GUI application works to some extend but fails on sensor command.

I am following the user manual but the baud rate mentioned in it is completely different.!!!

***************************************************************

[>> TX] START

[<< RX] *********************************

* STMicroelectronics *

* IO - Link MULTI-PORT SOLUTION *

*********************************

SELECT MASTER OR DEVICE

[>> TX] MASTER

[<< RX]

INSERT ADDRESS IC

[>> TX] 0

[<< RX]

INSERT OPERATING MODE

[>> TX] WR_S

[<< RX]

INSERT REGISTER VALUE

[>> TX] 096,248,033,122,122,122,122,

[<< RX]

PROGRAMMING DONE

[>> TX] COMMAND END

[<< RX]

SELECT MASTER OR DEVICE

[>> TX] DEVICE

[<< RX]

INSERT SLAVE NODE

[>> TX] 0

[<< RX]

INSERT SENSOR COMMAND

[>> TX] IDS

[ERR] Command ERROR (TRASMISSION FAIL) - RECEIVED DATA

[>> TX] COMMAND END

[ERR] Command ERROR (TRASMISSION FAIL) - RECEIVED DATA I=I5R?

[ERR] IDS COMMAND FAIL - NODE 0 - ATTEMPT 1

[ERR] Communication with STEVAL-IDP004V1 BOARD failed.

Please reset the BOARD and the GUI and retry.

***************************************************************

    8 replies

    Eleon BORLINI
    ST Employee
    August 30, 2019

    Hi Pranav,

    sorry for the delay in our answer. I contacted the team who developed the platform you are using and regarding the difficult you are facing in connecting the sensor node they suggest me to check if the adapter RS485-USB you are using follows the UM specs shown below (UM p.20).

    0690X000009axdCQAQ.png

    Regards

    Pmond
    PmondAuthor
    Associate II
    September 18, 2019

    Can you please please suggest which RS485- USB model to use. I tried with many of them - UI doesn't talk with the slave(sensor)

    Please help

    MOtt
    Associate II
    October 9, 2019

    After looking at the photo in the STEVAL-BFA001V1B manual, the RS485 to USB adapter I believe they used is the antaira UTS-1458B.

    Tesla DeLorean
    Guru
    August 30, 2019

    Can we perhaps just delete the 3-4 duplicates of this thread?

    Tips, Buy me a coffee, or three.. PayPal VenmoUp vote any posts that you find helpful, it shows what's working..
    Pmond
    PmondAuthor
    Associate II
    September 20, 2019

    But Still issue has not resolved yet.

    Pmond
    PmondAuthor
    Associate II
    September 5, 2019

    Hello

    Thanks for the response.

    When i tried connecting the RS485- USB connector (https://www.ftdichip.com/Support/Documents/DataSheets/Modules/DS_USB-COM485-PLUS4.pdf) and connected its only pin1 (DB9 connector on 4 way IO board) to pin1 of above converter) , pin2 (DB9 connector on ) to pi4way IO board ) pin2 of above converter) and pin 5 to ground for both connectors.

    Is my connection wrong?

    Sure will try to delete duplicates soon. Thanks again!!!

    Best Regards

    Pranav Mondhe

    Flow
    Visitor II
    September 17, 2019

    Hi,

    I have exaktly the same problem. Do you get fixed it?

    Best Regards

    Pmond
    PmondAuthor
    Associate II
    September 18, 2019

    Hello

    I tried replacing many RS485- USB connections- neither of them helped me to work with UI.

    Something is issue either in firmware update of IDP004V1 board or GUI Issue.

    And why standard B.R mentioned in manual is not working and 38400 is working - which looks very weird according to me. Though still UI doesn't work with sensor pack.

    Best Regards

    Pranav

    LMamb.1
    Visitor II
    January 16, 2020

    Any solution so far. I am also facing the same issue. I am able to connect and receive data on ST_Link V2 using putty . But when I connect using IO -Link board with RS485 convertor with the default baud rate error message is displayed

    231[>> TX] START

    [ERR] Command ERROR (TRASMISSION FAIL) - RECEIVED DATA

    [>> TX] COMMAND END

    [ERR] Command ERROR (TRASMISSION FAIL) - RECEIVED DATA

    [ERR] Communication with STEVAL-IDP004V1 BOARD failed.

    Please reset the BOARD and the GUI and retry."

    But when I reduce the baud rate to 38400 the following message is displayed.

    SELECT MASTER OR DEVICE

    [>> TX] MASTER

    [<< RX] 

    INSERT ADDRESS IC

    [>> TX] 0

    [<< RX] 

    INSERT OPERATING MODE

    [>> TX] WR_S

    [<< RX] 

    INSERT REGISTER VALUE

    [>> TX] 096,248,033,122,122,122,122,

    [<< RX] 

    PROGRAMMING DONE

    [>> TX] COMMAND END

    [<< RX] 

    SELECT MASTER OR DEVICE

    [>> TX] DEVICE

    [<< RX] 

    INSERT SLAVE NODE

    [>> TX] 0

    [<< RX] 

    INSERT SENSOR COMMAND

    [>> TX] IDS

    [*ERR*] Command ERROR (TRASMISSION FAIL) - RECEIVED DATA 

    [>> TX] COMMAND END

    [*ERR*] Command ERROR (TRASMISSION FAIL) - RECEIVED DATA ?OR

    [*ERR*] IDS COMMAND FAIL - NODE 0 - ATTEMPT 1

    [*ERR*] Communication with STEVAL-IDP004V1 BOARD failed.

        Please reset the BOARD and the GUI and retry.

    Please help

    Regards

    Lakshmanan

    ASaee.1
    Associate
    February 6, 2020

    Hello!

    It seems the issue still remains unresolved as I am unable to communicate with my board as well!

    I managed to program it using the onboard programmer on the nucleo-F070RB with the file STEVAL-IDP004V1_RS485.hex.

    The programming was successful however the 4 LED's in a column sensor 1-4 turned off and only flash when the board is reset.

    I receive the same errors

    [>> TX] START

    [*ERR*] Command ERROR (TRASMISSION FAIL) - RECEIVED DATA

    [>> TX] COMMAND END

    [*ERR*] Command ERROR (TRASMISSION FAIL) - RECEIVED DATA

    [*ERR*] Communication with STEVAL-IDP004V1 BOARD failed.

          Please reset the BOARD and the GUI and retry.

    The USB-RS485 cable used is

    https://www.amazon.com/Serial-Converter-Adapter-Supports-Windows/dp/B076WVFXN8/ref=sr_1_1_sspa

    I connected the DB-9 connector directly to the RS485 port.

    If there is a different cable which should be used then it would be really helpful to get its link.

    I also tried to flash the USB hex program and connected with the USB port however the PC fails to recognize the device as there is no driver.

    If there is a suitable driver then please share that as well.

    Thank you.

    Ashar.

    ASaee.1
    Associate
    February 14, 2020

    Hello everyone!

    Finally I was able to successfully get the data on the STEVAL-IDP005V1 GUI.

    And for me it worked through serendipity!

    0690X00000DAZVuQAP.png

    Graphs and other readings are being displayed..

    It seems the STEVAL-IDP004V1 board needs both the ST Link AND the RS485 to be connected simultaneously to be able to make the connection.

    I left the programmer link connected unintentionally and then attempted to connect via the USB serial and it successfully connected.

    Disconnecting either of the two causes the connectivity to break

    0690X00000DAZXWQA5.jpg

    The blue cable is the USB-RS485 cable connected to the IDP004V1 on its RS485 port.

    The Programmer link is connected via the ST-Link port on the IDP004V1 and the UK1001V1 interface board supplied with the STEVAL-BFA001V1B kit.

    Both are separate Com ports.

    The IDP004V1 IOLink board is programmed with the STEVAL-IDP004V1_RS485.hex using the Nucleo Programmer and the UK1001V1 board. A 20pin flat cable is used to link the two IDC type male headers.

    So whats confusing is that all the manuals say that after programming, the programmer should be disconnected. However if it is not connected then the GUI fails to connect to the IO link board.

    Once I connect via the USB Serial with programmer connected in parallel, removal of the programmer link causes failure of communication.

    I am quite sure that the data is flowing through the USB-RS485 link because it is the one showing TX/RX activity through the indicator LEDs and the com port selected in the STEVAL GUI also corresponds to it.

    So whats going on?

    And would we be able to connect this board with the XLinux PRDMNT on the discovery kit using the STEVAL-IDP004V1_RS485_PMP.hex file if it requires the programmer link as well!

    Thank you.

    ASaee.1
    Associate
    July 15, 2020

    Does anyone from ST knows that why does the STEVAL-IDP004V1 board needs BOTH the programmer link & the RS485 connection simultaneously to be able to work properly?

    Is it possible that the software binaries available were not updated with the removal this bug?

    Thanks.

    JMill.18
    Associate II
    October 25, 2024

    I am also having this problem.

    I am trying with a new STEVAL-IDP004V2 (so it should have the TEConcept IO-Link stack in it) and another STEVAL-IDP004V2 programmed with the mentioned hex file: STEVAL-IDP004V1_RS485.hex - my understanding is, that hex file is for ST's custom protocol.  I can't get the STEVAL-IDP005Vx-GUI to connect with the board.

    I use a Tripp-Lite U209-30-IND RS485-to-serial and it has worked using a different example, so I'm confident the issue isn't there.  I also use a genuine ST-LINK/V2 programmer with the board.  I have disconnected the sensors, I just want to get the STEVAL-IDP004V2 to connect.  I've tried 230400 baud, 38400 baud, same issue.
    When I do try to use the micro-USB method, neither Windows 11 nor Windows 10 recognize the board.  There seems to be a driver issue there as well, so I'm trying to get this working with the RS485-USB-serial connection.

    Any suggestions?

    JMill.18
    Associate II
    October 25, 2024

    Soon after my posting I tried using a Windows 7 PC which reported a "Device driver software was not successfully installed... STMicroelectronics Virtual COM Port (COM3) X Failed"

    Since on my Windows 11 PC, there is an "Intel(R) Active Management Technology - SOL (COM3)" under Ports, I disabled that, then tried reconnecting the board.  I may have done this disabling/activing of the Intel driver and connecting the board a couple of times, but at some point, the STEVAL-IDP004V2 came up with a different port, COM 6, and no errors.

    This allowed me to use the STEVAL-IDP005Vx-GUI and TEConcept Control Tool to connect to the board, but they seem to be having communication issues and I can't get that to work.  The TEConcept Control Tool simply reports "COM Fault" and the ST GUI seems get something on 'loop' but periodic faults. 
    Any ideas?