Communication issues with the SlushEngine


#33

Hi olivier, have you calculated the correct parameters for BEMF for the stepper motors you are using?

Is the power not supplied to the RPi by the SlushEngine?


#34

I didnt calculate that. Can you tell me more about how to calculate it and set it up properly?

Also, if i use my RPi headless, with nothing else than the xbox controller connected to it and wifi on ofc, I dont have the weird noise anymore.


#35

You can find the various documents from ST website, such as Voltage mode control operation and parameter optimization and A Guide to understanding L6470, L6480, and
powerSTEP01 output voltage levels
.

Is it possible to upload a video with the noise?


#36

Rraghvani,

We have the same issue namely the communication issues with the SPI and have tried what you said above.
The values we get for LReg.CONFIG are:
L6470 24: 0
The same for the other three (except 24 is 25 etc.)
We have a Slushengine Model X Lt and a RPi version 3B+.

Thank you in advance.


#37

Hi Kristof,

Have you followed the RPi setup and configuration? Is it a new RPi?


#38

Yes, I have used 3 new RPi already and a new Slushengine. I have tested the RPi SPI and have installed Raspbian a couple of times and the Slushengine both with the automatic way and the manual way.


#39

I have a Raspberry Pi 3 Model B running latest Raspbian Stretch (Linux RPi3 4.14.79-v7+) and SlushEngine Model X LT. I programme using Python 3.5.3, and my pinout is like so:

pi@RPi3:~ $ pinout
Revision           : a02082
SoC                : BCM2837
RAM                : 1024Mb
Storage            : MicroSD
USB ports          : 4 (excluding power)
Ethernet ports     : 1
Wi-fi              : True
Bluetooth          : True
Camera ports (CSI) : 1
Display ports (DSI): 1

J8:
   3V3  (1) (2)  5V    
 GPIO2  (3) (4)  5V    
 GPIO3  (5) (6)  GND   
 GPIO4  (7) (8)  GPIO14
   GND  (9) (10) GPIO15
GPIO17 (11) (12) GPIO18
GPIO27 (13) (14) GND   
GPIO22 (15) (16) GPIO23
   3V3 (17) (18) GPIO24
GPIO10 (19) (20) GND   
 GPIO9 (21) (22) GPIO25
GPIO11 (23) (24) GPIO8 
   GND (25) (26) GPIO7 
 GPIO0 (27) (28) GPIO1 
 GPIO5 (29) (30) GND   
 GPIO6 (31) (32) GPIO12
GPIO13 (33) (34) GND   
GPIO19 (35) (36) GPIO16
GPIO26 (37) (38) GPIO20
   GND (39) (40) GPIO21


pi@RPi3:~ $ gpio readall
 +-----+-----+---------+------+---+---Pi 3---+---+------+---------+-----+-----+
 | BCM | wPi |   Name  | Mode | V | Physical | V | Mode | Name    | wPi | BCM |
 +-----+-----+---------+------+---+----++----+---+------+---------+-----+-----+
 |     |     |    3.3v |      |   |  1 || 2  |   |      | 5v      |     |     |
 |   2 |   8 |   SDA.1 | ALT0 | 1 |  3 || 4  |   |      | 5v      |     |     |
 |   3 |   9 |   SCL.1 | ALT0 | 1 |  5 || 6  |   |      | 0v      |     |     |
 |   4 |   7 | GPIO. 7 |   IN | 1 |  7 || 8  | 0 | IN   | TxD     | 15  | 14  |
 |     |     |      0v |      |   |  9 || 10 | 1 | IN   | RxD     | 16  | 15  |
 |  17 |   0 | GPIO. 0 |   IN | 0 | 11 || 12 | 0 | IN   | GPIO. 1 | 1   | 18  |
 |  27 |   2 | GPIO. 2 |   IN | 0 | 13 || 14 |   |      | 0v      |     |     |
 |  22 |   3 | GPIO. 3 |   IN | 0 | 15 || 16 | 0 | IN   | GPIO. 4 | 4   | 23  |
 |     |     |    3.3v |      |   | 17 || 18 | 0 | IN   | GPIO. 5 | 5   | 24  |
 |  10 |  12 |    MOSI | ALT0 | 0 | 19 || 20 |   |      | 0v      |     |     |
 |   9 |  13 |    MISO | ALT0 | 0 | 21 || 22 | 0 | IN   | GPIO. 6 | 6   | 25  |
 |  11 |  14 |    SCLK | ALT0 | 0 | 23 || 24 | 1 | OUT  | CE0     | 10  | 8   |
 |     |     |      0v |      |   | 25 || 26 | 1 | OUT  | CE1     | 11  | 7   |
 |   0 |  30 |   SDA.0 |   IN | 1 | 27 || 28 | 1 | IN   | SCL.0   | 31  | 1   |
 |   5 |  21 | GPIO.21 |   IN | 1 | 29 || 30 |   |      | 0v      |     |     |
 |   6 |  22 | GPIO.22 |   IN | 1 | 31 || 32 | 0 | IN   | GPIO.26 | 26  | 12  |
 |  13 |  23 | GPIO.23 |   IN | 0 | 33 || 34 |   |      | 0v      |     |     |
 |  19 |  24 | GPIO.24 |   IN | 0 | 35 || 36 | 0 | IN   | GPIO.27 | 27  | 16  |
 |  26 |  25 | GPIO.25 |   IN | 0 | 37 || 38 | 0 | IN   | GPIO.28 | 28  | 20  |
 |     |     |      0v |      |   | 39 || 40 | 0 | IN   | GPIO.29 | 29  | 21  |
 +-----+-----+---------+------+---+----++----+---+------+---------+-----+-----+
 | BCM | wPi |   Name  | Mode | V | Physical | V | Mode | Name    | wPi | BCM |
 +-----+-----+---------+------+---+---Pi 3---+---+------+---------+-----+-----+

I suggest you run the commands, and check that you have the same pinouts. The RPi3 B+ may be different?


#40

I have checked and the pin layout did not chance since 2014


#41

The only difference I see is that pins 8 & 10 are ALT5 in stead of IN, I don’t know if it makes a difference or not?


#42


#43

Everything looks the same - pins 8 and 10 won’t make any difference, as those are for the UEXT Connector.

Is it possible to take a photo of everything connected e.g. RPi3, SlushEngine, Power, Stepper Motors?


#44

The setup is pretty standard, the source can give upto 15V of power, which should be enough to drive a small no-load stepper motor for testing. We will also be contacting the makers of the Slushengine to hear if they had any similar problems in the past.
Thank you already for your time.


#45

Does the red light appear on the SlushEngine when there is power supplied?

Do all the electronic components on the SlushEngine seated and soldered correctly? There’s a component R602 beneath the letter X, which looks odd.

Do you have a RPi3 (not B+) that you can use?


#46

The light turns blue, I think they use red and blue leds. The soldering looks OK, and I have used both the B+ and B v1.2.


#48

Hey, Did you ever manage to sort out this issue? Typically communication issues can come from a bad IO on the PI or an incorrectly setup SPI interface.

One of the issues we have noticed with newer versions of the PI is that the IO seem to be very delicate. We have lost some of the SPI IO in the past due to a bad power supply and seemingly a lot of EMI.


#49

The problem has not been resolved yet, we are using another motor driver from Adafruit now.


#51

Hi everyone,

I bought the slushengine model d last year, unfortunately I didn’t had the time to test it until last week.

Like the origninal post I have this message when I try to execute a commande to move the stepper:
“communication issues; check SPI configuration and cables”.

I’ve also put the code
print("L6470 {}: {}".format(self.chipSelect, self.getParam(LReg.CONFIG)))
print("L6480 {}: {}".format(self.chipSelect, self.getParam([0x1A, 16])))

after the “initPeripherals” function and It return 0.

pi@raspberrypi:~/slushengine $ python3 …/rbx1-software/robot.py
L6470 24: 0
L6480 24: 0
communication issues; check SPI configuration and cables
L6470 25: 0
L6480 25: 0
communication issues; check SPI configuration and cables
L6470 26: 0
L6480 26: 0
communication issues; check SPI configuration and cables
L6470 27: 0
L6480 27: 0
communication issues; check SPI configuration and cables
L6470 20: 0
L6480 20: 0
communication issues; check SPI configuration and cables
L6470 21: 0
L6480 21: 0
communication issues; check SPI configuration and cables

I use a raspberry pi b 3+, I already try 2 different raspberry and I have the same issue.

For me, the raspberry and the slushengine doesn’t communicate but I am not sur how and why.

I also see some brown stuff on some component I don’t know how it’s append but the board seems still working. I hope the board is not damaged.

Do you have any idea about what can create this issue and how resolve it ?

Thank you !

You can see below my configuration


#52

image


#53

image


#54

HI Btotech,

Are you able to take a photo of the “brown stuff” that you had mentioned?

What voltage and amps power supply are you using?