All of a sudden I cannot open any sonar log files on Cerulean’s SonarView, I’m getting the error “Could not load file, TypeError: failed to fetch”. This even happens with the demo files. I opened an issue with Cerulean but was wondering if anybody here knew anything about this issue.
Hi @amostafiz
What version of SonarView are you using? Are you using standalone or as a BlueOS extension? I the extension, are you sure you’re connected to the vehicle ok?
It seems to be a new problem with my Windows laptop only, on all versions of SonarView, both standalone and BlueOS extension. I’m able to open the log files on a different computer though.
I am having a similar problem with SonarView Extension on BlueOs. When I hit the Record Button it kick back the error message "Could not toggle recording. Request completed with error status 500 (Internal Server Error):ZodError: ["
It works fine as a standalone on the same laptop running windows.
Hi @antcrook -
What version of the Sonarview extension? What version of BlueOS are you using? What sonar are you using it with?
Blueos: v1.4.3
SonarView: v1.14.68
Sonar: Cerulean Surveyor 240-16
Thanks for the report, we’ll take a look and get it fixed. I’ll let you know if we need any more info.
@antcrook If I’m looking at the right support ticket, you managed to fix the problem by clearing out recently added configurations. If there’s still an issue, please let me know!
@amostafiz Thanks for the report. It would very much help to have a diagnostics file (life raft icon → Download Diagnostics). Could you please send that? What version of BlueOS are you using and what version of SonarView? What is showing up in the address bar when you open SonarView in the browser?
For the issue I am having, which is different than @amostafiz, if I remove the GPS device the issue is resolved. For the GPS I have an Emlid RS2+ streaming NMEA to TCP 9001 using the “Generic GPS device”. It does work on the standalone version of SonarView.
@antcrook Are you using the SonarView 1.14.68 version of the BlueOS extension and the 1.14.68 standalone version of SonarView? I suspect a version mismatch would cause these problems. If you’re still having issues, please send the same diagnostics file I suggested above so I can take a deeper look.
@amostafiz Is this still an issue? If so, I need that diagnostics file to look deeper.
it is working now, must’ve been a temporary issue with my computer
Here are the files
client.json (289 Bytes)
summary.txt (78 Bytes)
sonarlink-diagnostics.json (9.1 KB)
sonarlink.json (91 Bytes)
errlog.jsonl (1021.1 KB)
@antcrook
Thank you so much — that was incredibly helpful!
It turns out there was an issue where older versions of SonarView would emit an invalid config file for SonarLink. Newer versions of SonarLink would see this and reject the config file entirely, rather than defaulting in the missing data.
A fix will be released soon. In the meantime, if you have this issue, you can “Clear Configurations” on the session configurations page and set up the devices and configuration again via the GUI. Note that re-importing an old sonarlink config file will cause the problem to surface again (until the real fix in the next SonarView release).
Clearing the configuration worked. It records data now - Thanks Dan.