This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
RF remote via SPI
#11
Thanks Sean, looks like I did it right.

I ordered an 8MHz Pro Mini ,but it appears to run at 16
Can it be that Arduino.py works fine at 16 MHZ fine but the browser config does not?
I thought that SPI runs at CLOCK/2
Reply
#12
the processor clock rate is different from the spi clock speed

because the raspberry is master clock it sets the rate: the arduino is the slave
Reply
#13
I am at a loss what could be my problem with the remote:


When I run Arduino.py I can see codes from both RF and IR remotes
In the browser I don't see anything coming in.
The GPIO pins on the Pi are registering correctly.

-Using tinypilot image 2020_10_27.img
-Latest hat.ino from git.

I  have a new Arduino Pro Mini confirmed running at 8MHz.
I am using various RF remotes I have lying around with the IR LED on Arduino pin3
Tried a Pi Zero and a PI 2b , Arduino SPI wired directly to the PI with short wires .
Supply voltages are 3.29 V on all pins
I have no external EEPROM and only IMU connected


Any pointers would be appreciated
Reply
#14
without the external eeprom it's likely the hat program will not attempt to communicate with the arduino because the eeprom describes the hardware attached to the pi, and without it, it assumes the original 26 pin tinypilot which is just a SPI nokia5110, i2c imu, and buttons

So maybe you can modify hat.py and harddcode it where it tries to open custom_0
Reply
#15
(2020-11-06, 09:00 PM)seandepagnier Wrote: without the external eeprom it's likely the hat program will not attempt to communicate with the arduino because the eeprom describes the hardware attached to the pi, and without it, it assumes the original 26 pin tinypilot which is just a SPI nokia5110, i2c imu, and buttons

So maybe you can modify hat.py and harddcode it where it tries to open custom_0

Thanks Sean, 

Tbh, I am a hack when it comes to programming, but I will give it a try.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)