openinverter forum

joromy wrote: ↑Wed Jan 08, 2020 7:38 am I had similar problems when I tested the inverter not enclosed.
It went away when I put it inside the eclosure (100% air tight)

I think this was caused by condensation.
I also have conformal coating on the board.

arber333 wrote: ↑Wed Jan 08, 2020 9:39 am Yes, but my sensor is totaly enclosed and is automotive inductive sensor. This should mean it gets funny ticks only after signal enters the main board.
I also remember i put a diode from reverse pin towards reverse switch to keep reverse light from activating if i intentionaly activate BMS pin. Could that diode cause some problems? It is just to keep electrons flowing towards the main board not in reverse.

param_prj.h:
..
VALUE_ENTRY(maxspd,      "rpm",   2044 ) \
..

stm32_sine.cpp:

static void Ms10Task(void)
{
   ..
   ..
   int32_t spd = Encoder::GetSpeed();
   Param::SetInt(Param::speed, spd);
   if (spd > Param::GetInt(Param::maxspd))
   {
	  Param::SetInt(Param::maxspd, spd);
   }

   ..

nailgg wrote: ↑Wed Jan 08, 2020 10:38 am
Sometimes very short spikes cannot be monitored by CAN or UART. While working on the issue, I added a spot value called "maxspd" which keeps the highest RPM the encoder ever read since the inverter power up. Changed the code a bit, like below:

joromy wrote: ↑Sun Mar 22, 2020 10:41 am

nailgg wrote: ↑Wed Jan 08, 2020 10:38 am
Sometimes very short spikes cannot be monitored by CAN or UART. While working on the issue, I added a spot value called "maxspd" which keeps the highest RPM the encoder ever read since the inverter power up. Changed the code a bit, like below:

It would be nice to have the same on "max current"

I wish I could do changes and addons myself, but have only worked with arduiono IDE.
Have tested the STM32CubeIDE, but it was a little heavy for me.

static s32fp ProcessCurrents()
{
   .. 
   ..
   if (ilMax > Param::Get(Param::maxcur)) {
	   Param::SetFlt(Param::maxcur, ilMax);
   }
   
   return ilMax;
}

..
VALUE_ENTRY(maxcur,      "A",     2043 ) \
..

nailgg wrote: ↑Sun Mar 22, 2020 6:12 pm I already did that too on my firmware. The firmware version of my inverter is pretty outdated (before all FOC-related stuff) since it's already stable for my induction motor, but the code for max current is also simple:

• Instead of -1/0/+1 on the reverse/neutral/forward direction I also have implemented a "parking brake" direction on dir = -2. Direction selection on "dirmode=0" also behaves differently since I have four modes. Pushing the "forward" button momentarily increases the dir by +1 and "reverse" decreases by -1. My inverter streams the "dir" parameter through CAN so that the parking brake controlling device pulls the brakes when the dir = -2 and releases it when dir > -2. It might not work well with your existing direction knob if you're on dirmode=0.

• Implemented "throtmax" derating based on the SOC obtained by my particular BMS CAN stream. You don't have the same CAN stream so I'm not sure how "throtmax" will work.

• Added a new "cruisenb" mode to the "idlemode=3" parameter that I needed for my particular setup to use it as a hill-holder. It activates when the cruise button is switched on and doesn't deactivate it when the brake is pressed. Only deactivates when the cruise button is switched off.

• Changed the UART baud rate to 38400 and stop bit to 1. You will have to reprogram your ESP8266 or reconfigure your Zigbee if you're using one of these.

• Added "dirrev" parameter. When set to 1 it swaps the V and W phases resulting in reversing the motor direction.

• Added "finalampn" and "finalspnt" spot values. These always show the final "ampnom" and "fslipspnt" values. Needed these while working on the false overcurrent trips because the actual ampnom and fslipspnt wouldn't show the actual (derated) values when the current limit kicks in.

• Added "maxcur" and "maxspd" spot values. Shows the peak values since the inverter is powered up.
  
  and even more changes. I unfortunately don't have the time to revert all the changes except for the ones that you need since I currently don't have the possibility to test the firmware. So if you are sure you won't blow up your inverter, here are the binaries