Connecting Fystec PIS on RatOS 2.

I'm desperatly trying to connect and use Fystec PIS on my Vcore 500. Using RPI3b - Octopus Pro 429 - RatOS 2.0.2 When i use Fystec Proc on Github out of the box i get "'spi_bus' is not valid in section 'adxl345'" error If i try simply to connect with cs pin i get "Unknown spi_bus 'spi3'" error If i uncomment spi_bus i have no error on klipper start but get "Invalid adxl345 id (got ff vs e5)." when i accel query ... I try loads of combinations to get it working but it seems wasting time ... Maybe some of you here may tell me more ? Thanks
13 Replies
miklschmidt
miklschmidt•11mo ago
You need to name the adxl and reference that name when you use it, it will not work otherwise. ie.
[adxl345 fysetcpis]
[adxl345 fysetcpis]
and
[resonance_tester]
accel_chip: adxl345 fysetcpis
[resonance_tester]
accel_chip: adxl345 fysetcpis
extended-yellow
extended-yellow•11mo ago
@miklschmidt Thank you for answering, but already tried this and the PIS.cfg give me an "Invalid adxl345 id (got ff vs e5)."
extended-yellow
extended-yellow•11mo ago
No description
extended-yellow
extended-yellow•11mo ago
No description
blacksmithforlife
blacksmithforlife•11mo ago
in my experience that is usually due to long wiring and the ADXL being very sensitive to interference
extended-yellow
extended-yellow•11mo ago
it is about USB adxl, no selfwiring. And i have tried bunch of cables ... I also get an "Previously Under-Volted" and "Previously Throttled" message each time i connect or disconnect it from the PI
miklschmidt
miklschmidt•11mo ago
You need to query it with chip="fysetcpis" as well You should fix your power delivery in that case.
extended-yellow
extended-yellow•11mo ago
This do not work 😅
No description
miklschmidt
miklschmidt•11mo ago
Then it's not late enough in your config. You're supposed to put all custom stuff in user overrides.
extended-yellow
extended-yellow•11mo ago
This is a file I included in the end of the printer.cfg does it not work ?
extended-yellow
extended-yellow•11mo ago
I just put the showed code direct in the printer.cfg without include, it do not work either...
No description
miklschmidt
miklschmidt•11mo ago
Again, you need to specify the CHIP parameter ACCELEROMETER_QUERY CHIP="fysetcpis"
extended-yellow
extended-yellow•11mo ago
ok this seems to work now 🙂 TY