tony
New Member
Posts: 23
|
Post by tony on Aug 24, 2018 8:32:40 GMT
We are on AMC1280USB Firmware Version V2.4 rev3
|
|
tony
New Member
Posts: 23
|
Post by tony on Aug 24, 2018 8:33:28 GMT
We are on AMC1280USB Firmware Version V2.4 rev3 Sensorless Vector
|
|
|
Post by riton39 on Aug 24, 2018 8:36:29 GMT
the latest version seems to solve its PID problems
|
|
|
Post by riton39 on Aug 24, 2018 8:39:04 GMT
and there is no possible setting to improve the low frequency torque?
|
|
|
Post by riton39 on Aug 24, 2018 8:42:51 GMT
if it's a torque problem, there's a simple way to check: get on your simulator at the front end and give him some shots down to get him off the hook. if he drops, I think it's the torque.
|
|
|
Post by hexpod on Aug 24, 2018 9:39:13 GMT
the latest version seems to solve its PID problems Which version are talking about?
|
|
|
Post by vicpopo on Aug 24, 2018 15:46:15 GMT
Tested fw 2.4 the last revision and fw 3.0 last beta test release on the same game , same car , same track .
No problem with 2.4 ( no kicks ) and kicks on 3.0 .I think these kicks are not coming from a torque problem .I don't know the origin of the problem ( data transfert , communication ? Etc ..) , but it's like during a very small time ( < 1 s ) no setpoint sent . I think that is not a wrong setpoint but like a blank ( no setpoint ) and a few milli seconds after again new setpoints .
I feel more like this as a torque problem
|
|
tony
New Member
Posts: 23
|
Post by tony on Aug 25, 2018 18:14:50 GMT
Vic, I think you are really on to something with the blank setpoint...the big kick, it is like every channel is going full out, for a millisecond. If the blank setpoint could default to present setpoint or something not so harsh... .. .. this could maybe solve; the "kick" that happens during maneuvers, like Trip talks about.... that you know should not be there.
|
|
|
Post by riton39 on Aug 27, 2018 15:17:50 GMT
the latest version seems to solve its PID problems Which version are talking about? AMC1280USB Firmware v3.0 rev1c:
|
|
|
Post by riton39 on Aug 27, 2018 15:20:07 GMT
Tested fw 2.4 the last revision and fw 3.0 last beta test release on the same game , same car , same track . No problem with 2.4 ( no kicks ) and kicks on 3.0 .I think these kicks are not coming from a torque problem .I don't know the origin of the problem ( data transfert , communication ? Etc ..) , but it's like during a very small time ( < 1 s ) no setpoint sent . I think that is not a wrong setpoint but like a blank ( no setpoint ) and a few milli seconds after again new setpoints . I feel more like this as a torque problem you have readjusted your PID after the update 3.0 ?
|
|
|
Post by vicpopo on Aug 27, 2018 16:04:35 GMT
No
|
|
tony
New Member
Posts: 23
|
Post by tony on Aug 29, 2018 14:24:52 GMT
It seems somehow (not sure yesterday or today) USO data somehow accidentally got set to 8bit. Could that be the cause? Can't test because rolled back to older firmware for some other stuff testing. Trip, In the 2,4 rev.3, after selecting 16bit, you have an "under menu" where you should select "ser feedback off" Please do so and report if it eradicate you "kicks" Thanks Trip, Did you try the USO 16-Bit "Ser Feedback Off"? Our random kick in maneuvers is still there with a heavy load. Take the load off and they go away....So I am back thinking it is a torque limiting or software/firmware problem. Also, what kind of filter did you put on your potentiometers?
|
|
|
Post by vicpopo on Aug 29, 2018 17:49:20 GMT
Hi , Just a report with my last test : -used the Thanos fw 3.0 rev2a link www.dropbox.com/s/m6lptunco0nl1v3/enc_6dof_AMC1280USB_v3.0_rev2a.hex?dl=0-used with xsim the 6dof plugin of hexpod working with Thanos amc fw 3.0 SETUP AMC : - ser. Feedback OFF INSTEAD Motion Data only . - serial ID FF FF (new ) With this setup all works perfectlly as best as fw 2.2 or 2.4 NO KICKS !! Thanks
|
|
|
Post by hexpod on Aug 29, 2018 19:00:58 GMT
Trip, In the 2,4 rev.3, after selecting 16bit, you have an "under menu" where you should select "ser feedback off" Please do so and report if it eradicate you "kicks" Thanks Trip, Did you try the USO 16-Bit "Ser Feedback Off"? Our random kick in maneuvers is still there with a heavy load. Take the load off and they go away....So I am back thinking it is a torque limiting or software/firmware problem. Also, what kind of filter did you put on your potentiometers? Please update to the 3.0 rev.2a The new ID should help to eradicate some data transmission issues. Don't forget to Update SimTools/X-Sim heXpod IK plugin: heXpod.xyzWhile using BFF follow this update: Here’s a modified version of the fast curve fitting app which runs automatically when BIN2TH is set as the output mode. www.dropbox.com/s/658282394jh4i9a/BFF_6DOF_Background_v100.zip?dl=0 In this version however the two qualifier bytes can be set in the BINTH.ini file. Copy the exe and the ini file to your 6 DOF motion software folder – can be applied to any of the sim versions so is available for all now. So the procedure would be.. 1. Keep BIN2TH as the output mode in the .bff config file – this ensures the curve fitting app runs. 2. In the BINTH.ini file set the parameters Qualifier1 & 2 =255 to set 255 as the new qualifier bytes. 3. Set the other parameters as required (eg Delay to set packet output frequency, Use_Raw to switch the curve fitting on or off etc) 4. Run the software as normal. The new exe will run as before but now convert the old AB data to 255 255 (or any two bytes you set it to)
|
|
|
Post by riton39 on Aug 29, 2018 21:05:36 GMT
|
|