Start Probleme

You can test the pcb by this way:
Unplug all pcb motor connector
Capture d'écran 2023-05-02 211602.png
Now on arduremote start the odo test 5 turn for example:
Using a small wire shunt the 5V and SIG of the odo_left connector , you need to see the ticks increase into arduremote each time you connect and disconnect the 5V at sig.
 
Hello Bernard,
I just tried it with the 5v pin at the odometry input. it works on left as well as on right.
So the voltage coming from the driver is too low!?
 
Here code i use to test the driver with a mega , maybe you can adjust for the nano
And the video result
 

Attachments

  • mega.zip
    1.4 KB · Views: 3
Here code i use to test the driver with a mega , maybe you can adjust for the nano
And the video result

Hello Bernard.
thank you very much for the sketch. I wired and connected everything. the engine only jerks quietly, only briefly at regular intervals. is that normal!?
 
Code is write for arduino mega , so maybe so need to adjust it if you don't have a mega , please send a picture of your wiring and the code you use if you have change something.
I found the test motor and driver i use in the video, so i can try to do the same on my side.
 
the code and pinout is the same. I rewired everything again, but now he's doing something a little irregularly. I made a video...
 

Attachments

  • 20230504_205509.jpg
    20230504_205509.jpg
    929.9 KB · Views: 4
  • 20230504_205536.jpg
    20230504_205536.jpg
    654.8 KB · Views: 4
  • 20230504_205704.jpg
    20230504_205704.jpg
    774.5 KB · Views: 4
  • 20230504_205831.jpg
    20230504_205831.jpg
    980.3 KB · Views: 4
What about the console result ?
The last number is the Odometry , Did it change from 5000 to 5500 ?
 
That doesn't sound so healthy. But this could also be due to the PWM frequency
 
Yes it' s strange , normaly wheel need to rotate in one dir and reverse after , so the dir pin is not OK.
For the PWM freq you can add this line :
Code:
void setup() {

  TCCR1B = TCCR1B & B11111000 | B00000010;
 
  motorLeftSpeedRpmSet = 30.0 ;
  odometryTicksPerCm = 22 ; // encoder ticks per cm

and comment out this one

Code:
  attachInterrupt(digitalPinToInterrupt(pinOdometry), plus, RISING);



/*
  int myEraser = 7; // this is 111 in binary and is used as an eraser
  TCCR2B &= ~myEraser; // this operation (AND plus NOT), set the three bits in TCCR2B to 0
  int myPrescaler = 2; // 1=31Khz 2=4Khz
  TCCR2B |= myPrescaler;
  */
  delay(3000);

also code is write to move a load on positive and negative torque on the motor

THE MAIN result is that the odometry is OK, so something is strange on the main PCB ,I need to test on the last PCB version , maybe the resistor for voltage divisor is not OK ?
 
Here the change in the code (WARNING NOT TESTED) for the nano .
Motor need ta accelerate stop with brake for 2.5 second and reverse etc.....
 

Attachments

  • nano.zip
    1.3 KB · Views: 0
THE MAIN result is that the odometry is OK, so something is strange on the main PCB ,I need to test on the last PCB version , maybe the resistor for voltage divisor is not OK ?
Nothing has actually changed to the previous.
I have installed the 1.03, it works for me.
But of course you can also test it with the PCB.
 
Nothing has actually changed to the previous.
I have installed the 1.03, it works for me.
But of course you can also test it with the PCB.
Yes it's also ok for me on 1.03 with the ZS-X11H,
I have only tested the ZS-X12H on the 1.02 PCB version. And I need to check the value of the divisor resistor i have solder on the PCB1.02 maybe i use different one ?
 
Ah ok I have also only installed the ZS-X11H.
But it shouldn't be the voltage divider if the driver outputs odometry in 5V.
 
Ok, thanks.
Yes, I hope that could work, but unfortunately the driver doesn't like the new modified code either
 

Attachments

  • 20230504_215425.mp4
    67.4 MB
  • 20230504_215510.mp4
    48.8 MB
Maybe Bernard can re-measure his resistors or still trace what he soldered in?
 
Back
Top