How to generate the wake-up request pulse (WURQ) with an L6360?

[JHutt.1511]

I simply can't figure out how to generate this pulse with my STEVAL-IOM001V1 board. Even the supplied code (en.stsw-iom001) doesn't make me any wiser.

[Raghava]

@JHutt.1511​  I am already using the nucleo board. my master stack is in same board.

[MG.1]

@TSerr.1​ I haven't tried it yet, I'll try it sometime.

But my MasterCycleTime is at about 8.8ms.

[MG.1]

@TSerr.1​ I haven't tried it yet, I'll try it sometime.

But my MasterCycleTime is at about 8.8ms.

[JHutt.1511]

I agree with @TSerr.1​ on the comment that the RPI is not perfect on communication and ENCQ swithing. The switching sometimes occurs too late, causing reception of carbage. @Raghava​ I have an STM nucleo-L476RG board but haven't found the time to work with it.

Nevertheless the ENCQ switching issue on the RPI, I still would expect to see the WURQ on my oscilloscope.

Got today an update of my case: STM support simply closed it. No info/links/etc; just closed it without any comment. And than they dared to ask for a satisfaction rating. Guess what I gave them :-)

[LHaim]

Hi, I am also having difficulties generating the wake up sequence.

I am using the P-NUCLEO-IOM01M1 EVBs pack (https://www.st.com/en/ecosystems/p-nucleo-iom01m1.html).

I am trying to establish an IO-Link connection with an FT-10 distance sensor from SENSOPART (https://www.sensopart.com/en/products/distance-sensors/distance-sensors/ft-10-rla-60-pnsl-k4.html).

I am able to receive binary information from the sensor but not IO-Link data.

I've tried what @TSerr.1​ suggested without success, I've also tried a bunch of different configurations and nothing worked so far.

Does anyone have another suggestion on how this can be done?

[TSerr.1]

@LHaim​  are you able to communicate with the L6360 through I2C correctly (computing parity, reading/writing to registers) ? The best way to check would be to toggle the LED on the evaluation board. For example by setting LSB & MSB of LED1 which are respectively at register addresses 0x04 and 0x05 to value 0xFF (default is off at 0x00).

If not what ARM are you using to control the L6360 ?     

[LHaim]

I think I am communicating with the I2C successfully, I will try the LED thing tomorrow to make sure.

I am using a NUCLEO-F446RE board (https://www.st.com/en/evaluation-tools/nucleo-f446re.html) which uses an STM32F446RET6U (Arm® Cortex®-M4 32-bit) processor (https://www.st.com/en/microcontrollers-microprocessors/stm32f446re.html).

[LHaim]

First of all thanks for your response :-)

So I checked the LEDs and I am communicating with the I2C properly. The LEDs do get toggled.

As I stated in my previous comment this it the arm that I am using:

I am using a NUCLEO-F446RE board (https://www.st.com/en/evaluation-tools/nucleo-f446re.html) which uses an STM32F446RET6U (Arm® Cortex®-M4 32-bit) processor (https://www.st.com/en/microcontrollers-microprocessors/stm32f446re.html).

Do you have any other suggestions?

[TSerr.1]

So that's a good point. Your sensor is quite similar to mine.

One quick way to see if your Wake-up signal is triggered is to place your sensor such that in SIO mode the output is high. If you have an oscilloscope (a voltmeter will do) you should have 24v on the C/Q line. Then following the device initialization sequence as in Figure 24 of the L6360 datasheet (mostly writing 0xE0 (push-pull) to configuration register successfully and reading the registers through i2c) the L6360 should trigger the WURQ and you should see the C/Q line now pulled to low 0v afterwards. This means that the device is now ready to communicate as illustrated in Figure 21 of the IO-Link specification datasheet. Is that the case for you ?

[LHaim]

Due to the Corona virus outbreak I currently work from home and I don't have a voltmeter nor an oscilloscope around. I do however have a logic analyzer and I am sniffing a number of signals. 24 volts are beyond the logic's capabilities but I am able to see 9-10 volts on the C/Q line (which I assume are in reality 24 volts).

I follow the steps in Figure 24 and the C/Q line does drop after writing "push-pull" to the configuration register (even before I am reading the status register).

After the write I do the read part.

I was not familiar with the IO-Link specification document, I looked at Figure 21 and it seems that I am reaching this point.

After the above I am setting the COM mode to COM2 which is the FT 10 sensor's mode and I am sending a message to it (0xAA), but I get nothing in response and from here on the sensor does not send me any information.

At this point if I clear the Enable C/Q line (am I supposed to?) I start getting binary information from the sensor, but not IO-Link data.

* Am I missing the next step?

* Is it possible that I did something wrong along the way? (perhaps something we did not discuss).

* Would it help if I added my code here?

Thanks!