Suchergebnisse

Hi Bernard I was able to fix the traceback problem. It was none of what we discussed. Putting two 47nF capacitors in parallel to the wheel motor connector I solved it all. The problem has not occurred for 2 weeks. It was the engines that created interference.

the robot never turned off by itself. however it is set to 300 minutes .. every now and then I make it do manual movements to keep it from turning off .. this morning, however, everything is okk ... I have no traceback errors and the wifi is stable ... maybe it was a series of problems due...

ah okk. this time it didn't give me any traceback errors, i had to connect it via hdmi and i saw that only the wifi was blocked. tonight I leave it on connected to the xl4015, tomorrow if I see something abnormal I disconnect the external antenna and re-enable the internal one

how do you see if the watchdog is in trig?

the robot is not currently cutting. it is above the table inside the house. he lost his connection while I made him do some manual maneuvers over the table. I raised the wheels

Today at noon I disconnected the gps and since then I have not had any TRACEBACK errors. But this afternoon he lost the wifi connection, I had to disable the wifi and re-enable it (I have a usb antenna to increase the signal). Could it be the power supply? I found a module with XL4015 here at...

once a blue light came on while communicating with satellites, lately it doesn't light up anymore. Isn't he the one who gives me the problems?

yes I have a neo 6m gps module

A step down module like this. I get the current for the module from P17

connecting it via hdmi there is no yellow star. I feed it through a 5A step down module

I also looked at where I had connected the IMUs and the RTC. IMU 1 = i2c 4 IMU 2 = i2c 5 RTC = i2c 3

Could the cable between raspberry and arduino be faulty?

I set the watchdog to 30000. Now the robot is on the table in the laboratory stopped in charge and I have a TRACEBACK error again. But it gives different information

no they don't have the same address. I have already checked, however I try to disconnect the compass and navigate without it, let's see if it still gives me any problems

I forgot last year I had to connect both the RTC and the IMU on other ports because both level converters burned by themselves

On i2c there is connected the RTC and 2 imu. There are 2 IMUs because last year I found the GY88 with the mmc5883 compass, then I connected a second IMU that had the HMC5883 compass, I removed the peripherals that did not need the second IMU from the pcb. In the raspberry this year I put an...

Hi Bernard this weekend I started it, but it gives me some problems that I have been carrying around since last year. I tried to fix it by changing RTC but I still have problems. Randomly I get a TRACEBACK error, then when I restart PIARDU sometimes I get the RTC error on i2c. I reboot raspberry...

Ah OK. I also saw that there is the scheme to make the sender with the door. Does the code provide for it or does it need to be changed?

thanks now works but what is the second loop for? I saw that when I press on start area 2 on the display SENDER A is written

Hello i made the sender to cut in area 2 but i can't get it to communicate with the robot. Through the browser the sender turns on and off, when I do the test through Piardu it returns me SENDER FAIL. The sender for area 1 use that of marotronics. On the console, doing the start from Piardu, I...