4.0.3 Wow

0 views

Skip to first unread message

Flaviano Goldammer

unread,

Aug 3, 2024, 3:49:15 PM8/3/24

to roallamrari

I was looking through the F/W versions of my various switches to make sure they are all current. My GS105Ev2 is reporting back in ProSAFE Plus Configuration Utility that is has F/W v5.4.0.3. The Netgear Support page shows the current F/W version to be v1.5.0.5.

I also bought several GS105Ev2 switches, and they all have firmware V5.4.0.3. Screenshot from the ProSAFE Plus Configuration Utility is attched. I flashed them with the latest firmware V1.5.0.5 and were successful.

This is not a big release but rather it is intended to fix spelling errors and make requirements clearer without making breaking changes such as materially changing requirements, strengthening requirements or adding requirements.

However, some requirements may have been slightly weakened where we felt appropriate and some entirely redundant requirements have been removed (but without renumbering). Nevertheless, Anyone using 4.0.1 or 4.0.2 should be able to smoothly start using 4.0.3.

First of all, we have included Elar Lang's new position as a leader of the project. Elar has spent many hours tirelessly working through issues, wording and generally trying to make the standard better. His promotion to leader is well deserved.

There were a number of requirements which were almost direct duplicates of other pre-existing requirements. We have tried to remove some of these to make it easier to consume the standard. Similarly, certain requirements appeared to not be practically actionable. We have removed some of these as well. Wherever we have removed requirements, we have deliberately left the numbering as it was and added a note in the text of the requirement starting with "[DELETED...]".

In a couple of examples we have reduced what is necessary to fulfil certain requirements where discussion concluded that this was appropriate. This allowed us to increase the accuracy of the standard without causing applications which would have previously passed a requirement to fail it.

Notably, we have not reduced the minimum length from 12. It is likely that in future versions, this will occur but only in conjunction with very explicit requirements around other password requirements as well as Multi-Factor Authentication requirements.

Copter-4.0.3 has been released as the official/stable version for multicopters and traditional helicopters and can be installed using one the GCSs (Mission Planner, QGC, etc) or can be directly downloaded from firmware.ardupilot.org/Copter/stable.

The most important fix is the first one which can lead to the autopilot rebooting (via the watchdog ) when the RC transmitter is first turned on but only if MAVLink2 signing is enabled. We are not aware of any crashes caused by this issue.

I have flown 3 vehicle with new FW4.0.3 the first time last weekend.
1 quadcopter, 1 hexacopter, 1 heli.
All modes and basic funktions I need were working fine with all 3. I could not find any problem.
Thanks a lot for all your work.

This is almost always a serial port driver issue. My fix is to uninstall the driver but making sure to check the box to delete the drivers. Most of the time there is driver on top of driver so you may need to repeat until there is no longer a checkbox to delete the driver. If you continue to have issues please email us at sup...@morobotics.io and I will happily help you 1 on 1.

ESC settings? Disable all optional ESC features, turn off voltage cutoff or set it as low as possible. Disable active braking.
Ensure all voltage and current monitoringin AC is set up correctly and working.

@andyp1per, Not sure which drivers are used by AP, however I have listed in my post what I know: CAN ESCs, CAN Here 2, SBUS for RC and serial 5 for SF11/C. I have also added my params file in my post.

GXT 4.0.3 works great with GWT 2.8.2. With GWT 2.8.2 you can use the new JsInterop libraries which allows you to write Javascript easily with Java. You will also be able to take advantage of writing your GXT application with Java 1.8 syntax. And this version supports using Java 1.9 as the default runtime. Check out all the features in GWT 2.8.2 here.

The Sencha Support team is always standing by to help you build your application. They can help you figure out unique scenarios that may not seem like there is an easy solution readily available. You can contact Sencha Support at [email protected].

GXT has an exciting future this year, with two major initiatives to come. The first is putting GXT back on course with a regular minor release cadence. And the second is providing major features to help quicken your application development.

Sorry to hear you having problems. I just checked and I was able to install both qiime2R and phyloseq into R 4.0.3. Could you share details of how you are trying to install the packages and any error messages you might be getting?

I have written/developed 4 distinct plugins that I have been using since Wireshark 2.x. When Wireshark 3.x was released, I updated my plugins to work with that. Now that Wireshark 4.x is out, I am trying to update my plugins for that version.

I develop in Windows environment and I follow the instructions in the Developer's guide in the Windows section. I download all of the tools that are necessary and set up my Wireshark build environment and build Wireshark along with my four plugins. Then I install the latest cooresponding Wireshark version (in this case version 4.0.3) and then copy my plugin dlls and all of my supporting dlls to the Wireshark install location. This has been working for me for the last several years.

This time, when I finished building Wireshark and my four plugins, I am able to successfully run my data with the Wireshark version I built and with my new plugins. I have a test case I run through to make sure it all works correctly. And it does. Then I installed Wireshark 4.0.3 and copied all of my plugins and supporting dlls to the Wireshark 4.0.3 install location. At this point, when I run this version of Wireshark, I get an error stating that "Couldn't load plugin 'foo.dll':" followed by the location of my plugin dll, and finally, "The specified procedure could not be found." The other three plugins I wrote work as designed.

More background about the plugin that does not load: It is actually based on the SMTP dissector that comes with Wireshark. I start with the SMTP dissector code and modify it to work with my data. I changed the names of the important methods and variables to have new names and I register these methods to be used instead of the original SMTP dissector. Again, this has worked for all of the 2.x and 3.x versions of Wireshark and it works with the new Wireshark that I built with the lasest source from Wireshark.

Can someone tell me how to figure out which "specified procedure" is not being found and how I can fix this issue? Again, it works just fine with the Wireshark that I built. But we don't distribute our own Wireshark. We only distribute our plugin dlls and let our users install the latest version from Wireshark.

Unless that version of Wireshark was built from the source code to a 4.0.x version of Wireshark, it is not guaranteed to result in a plugin that will work with a 4.0.x version of Wireshark, as we do not guarantee binary compatibility between major releases of Wireshark - including, for example, 4.0.x and a future 4.2.x; we only guarantee binary compatibility between dot-dot releases.

If you follow the instructions in section 2.2.10 "Install and Prepare Sources" of the Developer's Guide, you will be building a Wireshark from a snapshot of the current under-development next major release of Wireshark, which is not guaranteed to be binary compatible with 4.0.x, or even with that future major release.

So you'll need to get the 4.0.3 source code for Wireshark, and build your plugins in that directory hierarchy. The "Source Code" link in the "Download Wireshark" section of our shiny new main web page will provide the source to 4.0.3. It's in the form of an XZ-compressed tarball, so you might need WinZip to unpack it.

If you build it with the 4.0.3 source code, it will probably either 1) result in a binary that doesn't call that procedure or 2) fail to build, with a linker error giving the name of the procedure. The error might be of the form

(I'm doing some tests to see what information error messages that Windows displays for this situation provide, and whether there's anything we can do to get more information, such as the name of the procedure. If not, that's ultimately on Microsoft, not us; the equivalent mechanism in UN*Xes has a call to get an error message string, which, at leas on macOS, is extremely technical, but does mention the name of the procedure.)

This means that users not running Windows won't be able to use your plugin. If you make the source code to your plugin available, that would allow users not running Windows to build it (again, using the source to the version of Wireshark that they're using) and use it.

Thank you for your response. You were correct. I was using the snapshot of the current under-development source and I needed to be using the 4.0.3 source. All of my plugins now work with Wireshark 4.0.3.

I was wondering whether anyone here has experience with using Zephyr along with the combination of CLM 4.0.3 and JIRA? I am able to connect JIRA and CLM through the OSLC adapter to create issues, etc, but I am trying to see whether RQM could be 'replaced' with Zephyr, so you basically connect WorkItems to Zephyr test plans and tests.

I'm having the same issue as a few other people on the forum. It seems the SDK is not yet available for S32DS 3.5, as 3.5 only supports up to RTM 4.0.1. I'd like to use the newest SDK (4.0.3) in S32DS 3.5 - Update 4, since it includes improvements to the lin-stack middleware.

Sorry if this is a dumb question, but if 3.5 is the latest version of S32DS and 3.0.3 is the latest SDK, why will DS 3.5 not support SDK 3.0 3? I'm pretty new to the forums and don't have a good understanding of all the different versions and dependencies. I've been using S32DS 2.2 with an S32K148 for a number of years and just now looking to upgrade to latest DS. I understand that DS 2.2 is the last to support Processor Expert and that DS 3.x uses the Configuration Tools. What currently is the stable latest and greatest?