Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Notice: Undefined offset: 84 in phpFITFileAnalysis.php on line 1228 #52

Open
LudoWeb opened this issue Jun 19, 2019 · 4 comments
Open

Comments

@LudoWeb
Copy link

LudoWeb commented Jun 19, 2019

Hi,

I have an issue with the parser.

( ! ) Notice: Undefined offset: 84 in \vendor\php-fit-file-analysis\phpFITFileAnalysis.php on line 1228

Do you have any idea about this issue ?
Many thanks

@adriangibbons
Copy link
Owner

adriangibbons commented Jun 20, 2019

Can you confirm the offending line 1228 is:
$this->types = $this->endianness[$architecture];

It would seem that $architecture has a value of 84, which won't work as it should only be 0 or 1 depending on whether little or big-endianness should be observed.

What device was the FIT file created with? E.g. a Garmin Forerunner XX or whatever.

Do you only have the issue with one FIT file or many?

I can have a deeper look if you share a FIT file with the issue.

@LudoWeb
Copy link
Author

LudoWeb commented Jun 20, 2019

It's a Suunto device. I have the issue with one FIT only.

See the file in attachment.

Many thanks :)

@LudoWeb
Copy link
Author

LudoWeb commented Jun 25, 2019

Hey @adriangibbons,

Were you be able to check the issue ?

Edit : the device was "Forerunner 735XT" with "Ceinture Cardio Garmin HRM Swim" and none a suunto device.

@adriangibbons
Copy link
Owner

Hi @LudoWeb I have looked into this issue for the past 3 hours and not got very far.

I don't understand why the architecture is coming up as something other than 0 or 1.

Only thing I can think of is that this Forerunner combined with the HRM belt is using compressed HR fields, which I don't think the class currently supports. I read the FIT documentation and unfortunately, it is not obvious to me how to implement this (assuming that it is the issue in the first place)!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants