Is Galileo HAS possible with the LG290p?

LG290p and Galileo has

Hello, do you have any news about Galileo has with the LG290P?
Thanks

This thread covers most of it Unicore Galileo HAS bug? - #27 by Sparkfunny (use PPPNAVA)

I think that’s for a different chip.
My question is about the LG290p.
Thanks.

Edited, see below!

To my knowledge, the LG290P is capable of receiving E6 signals but the RTK engine does not yet take these signals into account. A firmware update to support HAS/E6 has been promised but I don’t have any ETA from Quectel right now.

2 Likes

Quectel support informed me that they will release an update for the LG290p in mid-May to receive Galileo HAS fixes.
Does Sparkfun need to modify the firmware to take advantage of these improvements?
Or is this already planned?

We’re not sure what changes will need to be made to the firmware until we can test out the Quectel changes. Once they release, we’ll be sure to follow shortly.

The v05 firmware has been released. You can get the zip here. There is no HAS fix yet, but you can output the raw HASE6 message.

image

Comments received.
I’m amazed that Quectel reports one thing and does another. The information was that the new firmware with the Galileo HAS corrections would be released in mid-May. Not only the ability to use raw messages on the E6 frequency, but also the native use of those corrections.
I don’t know why it took so long.

1 Like

what they refer to in the pdf as
“Optimized and compatible with more RTK differential services”?

I like what you’re thinking.

Wouldn’t it be neat if they (Quectel) mistakenly referred to HAS as RTK instead of PPP, since we do use it in “real-time” ?
Doubtful, but it doesn’t hurt to hope… LoL.

It left me wondering what they mean by “more RTK differential services.”
They don’t clarify what they’re referring to in the PDF.

1 Like

Hi, Quectel tells me on the Forum that the update will be after June.
Do we believe them?
Regards

I wouldn’t bet the farm on it but June isn’t far off, so at least we’ll know soon!

3 Likes

As I have already stated I fear that the limit is the hardware configuration of the module; however only your Team can shake them to deal with this feature (HAS_E6).
It is rare to find a company providing technical and commercial support like Yours.
Thank you for what you are doing for all this time …
Marco

1 Like

Hello, colleagues.
On the Quectel Forum, June informed me, as usual, that they’re behind on the new LG290p firmware.
We’ll continue waiting for the Galileo HAS fixes for a few more days.
Be patient.

Another month has passed and already is the fourth Fae eng. who says to wait…
If there is no stimulus from many, it does not become a priority feature.
Who does not want to wait fold on Unicorecomm chip.

Hello @Sparky.
We need your help as a company to get Galileo HA fixes for the LG290p.
A week ago, Quectel support informed us that they would have the new firmware almost soon, and we were very excited.
After a few days without a response from Quectel, they informed us that they were BACK ONCE AGAIN, and now it’s worse, with no delivery date for the new firmware.
Can Sparkfun, as a company, pressure or try to get Quectel to deliver firmware with fixes for Galileo HA?
When the LG290p was launched a year ago, they said it was a feature in development and boasted about receiving an E6 signal.
We hope for your support as a company to pressure Quectel.
I know several forum members are in the same wait, and we have insisted on the Quectel Forum and have only received unfulfilled promises.

Thanks, Sparkfun, and thanks, Sparky.

Best regards.
Angel

1 Like

Quectel ran into an unexpected issue and they are actively working the problem.

I can “almost” guarantee you that @sparky is communicating with Quectel, but there’s nothing really that SFE can do :wink:

I’m in the same boat as everyone, and eagerly awaiting the FW update.

Hi rftop.
Your words give me some peace of mind.
I don’t understand why Quectel support doesn’t inform us of the reality and just tells us they had a problem.
They only make us speculate about the issue.
How did you find out about the unexpected problem?
So, we’ll wait.
Thanks.