I’m sorry if I’ve missed your request to test this noise improvement firmware, but we did get a Lenze user to test too. We don’t have first-hand experience with Lenzes, so difficult to say if that is normal or not.
Can’t be normal, it is a noise boost not reduction. Did beano test his Lenze?
edit: new video, phone audio was not loud enough.
without any torque mode effects, it is silent - so no damping, friction and inertia possible.
the feel of grinding persists either way.
What type of encoder do you have?
there are no third party encoders for lenze servos. its the original quadrature 4096ppr encoder.
Sounds like [ML] and/or [MR] values are too high. Can you try if it changes if you re-run Granity’s “measure motor resistance and inductance” function? If it gives the same MR/ML values, then just try reducing those values 50% manually and see if it helps.
1 Like
I’ve added a poll about the results of the new IONI firmware:
@McErono please report back your finding about the ML&MR stuff.
It has no effect to decrease the ML and MR. only deactivating the filters does help. but ingame under load the noise is still there in turns.
If I can do anything to help solve this issue just let me know!
Thanks for tests! Looks like it’s not then caused by ML/MR. Here is another way to analyze the case: make Granity captures while turning the motor so that it makes sound. These settings should work:
It might take few shots to time the capture properly while turning the wheel. Could you take few captures and post saved graphs for inspection? We expect to see production of the noise from these graphs.
BTW, is the inertia effect the biggest affector here? If you adjust it alone, does the noise volume adjust equally?
Just upgraded the Ioni firmware to my small Mige… I can now run unlimited TBW, before I could only go up to 680 before inductance grinding noises started. The wheel just feels smoother,as a direct result I have reduced the reconstruction filter from 5 to 3 and have upped the ffb 10-20% ( from my own preference ). I hammered round road america for an hour in the Porsche in iRacing, played with the settings and did not have any glitches.
I had considered getting a uprated encoder… not any more, can’t see the point after this update.
What can I say other than a big “thank you” to Mika and Tero… they keep making the OSW better and better.
1 Like
I’ve been getting an issue lately.
I’m not sure if it’s because I put my computer to sleep and wake it up.
Basically simucube conf tool will say the wheel is disconnected. It’s still plugged in and there’s light in the simucube box.
I’ve gotta turn off the simucube then turn it back on.
I can connect via granity, can’t remember if I always can.
Sounds like the same issue that has been reported previously - rebooting pc makes SimuCUBE disappear. It is an issue in the ST Microelectronics USB stack, and as it is not our code, it is difficult to debug.
It is on the list of things to do, but not very high.
all filters/torque mode effects are sounding the same. 2% damping sounds the same as 2% inertia or 2% friction.
here are the graphs from my capture:
not moving wheel, damping and friction enabled
moving wheel left/right, damping and friction enabled
second try, wheel left/right, damping and friction enabled
turning wheel to one side, no swaying, damping and friction enabled
wheel left/right, all filters disabled
turning wheel to one side, no swaying, all filters disabled
Thanks! It seems that achieved torque gets some ripple while torque setpoint looks much like expected. Perhaps this motor type requires manually tuned MR and ML values. Here are instructions: https://granitedevices.com/wiki/Tuning_torque_controller
The goal would be to reduce difference between achieved and target torque curves that probably is causing the oscillating noise.
Would it have use to tweak this yourself on your small mige?
Or is the measure thing quite perfect?
i just remeasured the coil resistance with that new ioni firmware they stay virtually exactly the same
With MiGE we have found automatic measurement work very well. I won’t suggest manual configuration, but of course it doesn’t hurt to try if you’re interested.
1 Like
yeah, the problem for many simulator user would be to attach the servo shaft so that it won’t be able to rotate at all.
Yea Edge has NEVER liked downloading the IONI Firmware as it doesn’t realize the .gdz as a file and it blows it apart.
well I can’t block my motorshaft but I just tried with different MR ML values.
I found a pretty good fix! We assumed I have to decrease the MR ML values but instead I have to increase the coil resistance MR only.
It measures 1.4 and is noisy - if I set the value manually to 2.0 its much much better!
Are there any doubts on your side Mike and Terro? Is there a downside in increasing the MR value? Estimated Max Torque Value is way down in Simucube software.
further testing revealed I can use 1.8 MR if I decrease ML. combined with TBW unlimited it feels good and even the grinding is much improved. I am getting there I think… I just don’t understand why it does look like other Lenze users don’t have these troubles (beano and jonpaul?).
Hi Marc,
I have only tested on my AKM servo, have indicated the same a while back during my testing of the early beta IONI fw.
Cheers,
Beano
First update for a while. It is unlikely a new “stable” beta can be released this year, but we are making progress, both on the SimuCUBE side and IONI side. We may, or may not have, found something that could explain the reports of no feeling at turn-in, but we’ll need to analyze this.
Meanwhile, I didn’t get a chance to test&optimize the new effects yet, but today there was an impressive bug fixing session:
- Motor fault codes are read in initialization phase, instead of just checking for success/failure of initialization.
- It is not possible anymore to end up in Operational mode via complex state changes when initial motor settings are not configured at least once via the wizard.
- Added reading of HV Bus Voltage and FOV values if waited for initialization for more than 30 seconds. FOV must be larger than HV Bus Voltage + 2% for the IONI to init. There is an error message explaining this now in the main window. I might add it also to the wizard.
I didn’t manage to repeat the issue where one would not be able to connect to IONI in one case. I will have to try to repeat it later.
4 Likes