Minifreakmartin said:
The batteries are brand new!
Unfortunately being brand new does not preclude them being the cause of a problem.
Unless you state otherwise, I will assume that since you answered in this fashion that power does not actually cut out or shut off, and that you have some indication power is still always present at all times while doing this testing (a voltmeter, controller display, etc).
If this is not the case, then a battery problem of some type is still a possibility, in addition to the other issues you've noted..
I unfortunately do not know the motor properties and have a hard time contacting the manufacturer.
That's unfortunately very common.

If the controller cant' determine them itself, then you may need to test for them and then tune the controller a bit at a time to get it running smoothly.
I just switched the hall wires all kinds of ways and it just makes the motor stutter in any other settings. (I switched the thick cables at the controller )
There is also the small cables from the motor that are labeled hall wires. Shall I try switching those as well?
If you only switch the thick cables, you have not switched the halls (3 of the 5 thin wires). You have only switched the phases (3 thick wires).
There are a number of threads you can look around at regarding phase / hall wiring combos (combinations) that describe various procedures to find the right one, if my previously posted ones are inadequate. You'll need to monitor battery current with a wattmeter or ammeter during the procedure to find out when you have the right combination.
But first you should find out if your controller has an autolearn or similar procedure to do ths for you. If it does not, or you cannot tell if it does, or it doesn't work, then you can follow the manual procedure.
Note that if the controller has some form of angle-detect, etc., it may need to be re-run for every phase/hall combination before testing for no-load current, etc.
Interestingly enough the rpm goes in the negative when going forward.
My guess is that this means the speed sensor being used is setup in reverse of the way the controller expects to read it, or there is a setting in the controller for this, or the controller setup software or firmware is just not written correctly and reads the sensor wrong (poorly written software is not uncommon in any device of any kind anywhere).
Do you have a base setting to input you recommend?
I don't know anything specific about the Votols; just these types of controller in general, assuming it is an FOC controller (you'd need to determine that to know if my advice above was applicable or not). There are a number of threads regarding these that may have info you can use, however:
https://endless-sphere.com/forums/search.php?keywords=votol*&terms=all&author=&sc=1&sf=titleonly&sr=topics&sk=t&sd=d&st=0&ch=300&t=0&submit=Search
most of them are probably not relevant, but it may be worth looking at them anyway.
One more thing to note. The contact er gets incredibly hot.
Which specific contact are you referring to?
Or are you referring to a "contactor" that is used to shut off battery connection to controller? If the latter, you'll need to verify your wiring to the contactor is correct for the coil drive, and that you're not using a higher voltage on the coil than it is supposed to have. (I can't tell from your schematic posted above what wiring goes to the coil or what voltages are present on it).