wRasp Error Message

[MartyAMC]

Hi All,

Can someone tell me what the error message "Floating point: invalid" means. When I add new motor data to my existing (working) motor data text file I get the error and wRasp program shuts down during startup.

Thanks

 

[Larry Curcio]

Hi All,

Can someone tell me what the error message "Floating point: invalid" means. When I add new motor data to my existing (working) motor data text file I get the error and wRasp program shuts down during startup.

Thanks

It seems to be expecting something numeric but reading something non-numeric. Either you have a problem like o/0 or perhaps it's reading two fields and they got out of sync, or you have a comment that isn't commented out.

Something along those lines. It looks more like a system message than wRasp message per se.

 

[JDcluster]

It might be the delay values... if the spacing isn't right it can sometime happen.
Something in one of the motor files, but can also be if you don't
Enter a diameter that is greater than or equal to the motor diameter..


Just a few ideas


JD

 

[Handeman]

I usually split the new thrust curves in half and copy halves into the motor file and test it until I can near down which thrust curve has the bad data that causes the error. Once it's narrowed down, it's usually pretty easy to spot.

BTW, not sure about WRasp, but WRasp32 will only accept 8 delay values. I think it's eight, could be 10, but I know I loaded the CTI files and they faulted out because they listed every second from 4 to 16 and that was too many. Once I took it down to only the even values, it worked fine.

BTW, don't bother to try to send an email to [email protected], the address is invalid and kicks the message back to you. At least it did a month or so ago.

 

[JDcluster]

I found that a couple of the Pro XX motors did this & had to go in & tweak them to work correctly. Allot of it had to do with number of data points. WRASP is a 16 bit program & can't handle as many as the WRASP 32 program.

Here's my master file I use with WRASP -2.1
It has allot of the older motors not available today & are still fun to play with. I did delete most if not all of the hybrid motors. It appears that the files size is limited as well.



JD

View attachment ALL3.zip

 

[Menkar]

BTW, not sure about WRasp, but WRasp32 will only accept 8 delay values. I think it's eight, could be 10, but I know I loaded the CTI files and they faulted out because they listed every second from 4 to 16 and that was too many. Once I took it down to only the even values, it worked fine.

Handeman,

I just saw in another post, that some people do have problem with the CTI engine files. I know that at least for last 3 or 4 updates I did produce those files, but didn't know about wRASP having problem with them.

If you can tell me the format wRASP expecting the delays, assuming that most of the problems are delays format, I'll correct the files.

The engines having every seconds listed are usually engines on which you can effectively adjust the delay by 1 sec. steps. What is the maximum number or delays wRASP can handle ?

PS: I don't work for CTI, but I do like their products...

André

 

[Handeman]

Handeman,

I just saw in another post, that some people do have problem with the CTI engine files. I know that at least for last 3 or 4 updates I did produce those files, but didn't know about wRASP having problem with them.

If you can tell me the format wRASP expecting the delays, assuming that most of the problems are delays format, I'll correct the files.

The engines having every seconds listed are usually engines on which you can effectively adjust the delay by 1 sec. steps. What is the maximum number or delays wRASP can handle ?

PS: I don't work for CTI, but I do like their products...

André

The problem isn't with the format of the files, it's with the number of delays listed. The WRasp32 will only accept 8 or 10 values. When there is a value listed for each second within the adjustable range, it is too many and caused the program to error.

 

[Menkar]

The problem isn't with the format of the files, it's with the number of delays listed. The WRasp32 will only accept 8 or 10 values. When there is a value listed for each second within the adjustable range, it is too many and caused the program to error.

Sorry I should say, with the delay instead of delay format. I'm now fixing the files.

For the engine with 1sec. step, I'm trying to do something like:

8,10,12,14,16,18 or
7,9,11,13,15,17

That should be ok for wRASP.

Can I PM you the eng file to see if it's ok when I'm done ?

André

 

[JDcluster]

I gone over the CTI files & have found that they do some crazy delay formatting. They start with the high delays then go back to 1 & go up to where the first one left off. You want them to look something like this: 3-5-7-9.

I just wish I could get rid of the default Alpha rocket on start up. I had some trouble with the latest motor file from CTI as well & had to pull it all apart to find the errors.

Here's my latest copy that works with WRASP v2.1-


JD

View attachment 1ALL.eng

 

[Handeman]

Sorry I should say, with the delay instead of delay format. I'm now fixing the files.

For the engine with 1sec. step, I'm trying to do something like:

8,10,12,14,16,18 or
7,9,11,13,15,17

That should be ok for wRASP.

Can I PM you the eng file to see if it's ok when I'm done ?

André

Send away.