The Unknown 2011

[Berenguer Miramontes]

Ifyou are building a wizard or macro, or perhaps just a module which other people may run and change the input data, then it may be useful to deselect the Unknown fields, this could speed up processing because you are dropping any unnecessary information.

If you know what fields you need for your module and you want the output to be consistent even when the input data changes and might include new/unknown fields then you can control this by deselecting the Unknown field in a select tool.

You will also see the Unknown field option in many other tools, wherever there is a built in select, for example the Join tool, but it also appears in the Table tool. Again you can select or deselect and also reorder its position.

It means that the real-time wildfire update wasn't able to happen at the time of the error. I'm leaning towards connection issues to the update server. (WFRTSIG stands for WildFire Real-Time Signatures).

Setting the interval to real-time allows the NGFW to "access the signatures as soon as they are generated" by the WildFire cloud. -v/wildfire-whats-new/wildfire-features-in-panos-100/wil... If you set the interval to 15 minutes, you can have up to a 15-minute window in which you are not protected from an unknown threat. Of course, before the threat was detected in the sand box, you were unprotected.

I am not doing anything too fancy with the workflow - using the Directory Tool to read two Excel .xlsx files & using the Sample Tool to read in the latest ones. Using Formula, Select, Filter, Dynamic Input, Union, Join & Output Tools in the workflow. I am also using the Run cmd.exe Tool to stagger / delay writing to the output files but I was encountering the problem before that.

Thank you for all of the comments. The issue has been resolved. The user had an old password stored in her Alteryx server profile. She recently changed her Windows password & the Alteryx server profile password was not updated.

Question for Alteryx: Is there a clearer error message than "There was an unknown error executing the application. The engine reported status Error (Toolid: -1)" for when it is simply a password issue?

There are instances when columns can take on an unknown typecast denoted by a ? Icon next to the column name. This often happens after transposes or unpivoting. I am unsure why this happens, if a column contains numbers as well as text surely it should be denoted as string typecast.

The advantage of the proposal, is that such a node would only display the "Unknown" column types in the include box in the node, and you can use the force inclusion/exclusion protocols to select what columns would change type. This way it can be set up in an automated fashion.

Additionally, the Rename node never seems to change the typecast properly. If you change a column to string for instance. If you then look at its column type description, it is not "String" but "Non-native", and this also causes problems in some nodes. Ideally, it should change it precisely to the typecast desired, not to this "non-native" type.

I see what you mean now. With dynamic column name, this is not very easy. I have gone ahead and logged this request in our tracking system. We will let you know when we have a better solution for you.

I just solved the problem by avoiding that the type is changed to UNKNOWN during transpose by creating a column i.e. with STRINGS before the transpose action. The type will be automatically taken from it during transpose. I simply remove the new row again after transposing.

yes, in my case I added a column with strings (I used the RowID node to transfer the header strings to the newly inserted column). However, I guess numbers would also work. Just that Knime can automatically assign a type to the transposed columns. The type will stay even when the table is empty after the additional row is deleted again.

Still a workaround, I know, but for me the Auto Type Cast node mentioned above did not work since I have a changing number of columns.

Yes, it will happen most after unpivoting the columns, if the columns are more than two different type ( e.g. string for column A and data for column B), after the unpivoting, the new column will show a question mark and can not manipulate for string or data operation afterwards. Especially in a loop.

@kevinchen Thanks so much. Today I encountered with this issue of unknown type columns too. In my case, the issue arises when Concatenating string rows with that of number rows. I followed your solution, but in my case I did it the other way around, which was to convert the Numbers to String. The result was that all my columns are now in String type after Concatenating.

I am trying to load firmware to a custom board with MSP430F5529 via a MSP-FET Flash Emulation Tool. My circuit design was based off SLAU278AE Fig. 2-1 and the example designs at the end of the document. Board power comes from an external USB connection, which distributes 5V to the internal 3.3V LDO in the MSP430F5529. I have tested the power distribution and it works correctly.

When I attempt to load the code, first the code builds, then I get a status bar telling me that the debugger is being configured and finally I get the error "Error connecting to the target: Unknown device" with "TI MSP430 USB1/MSP430" along the window bar.

Going over the design again I found an error connecting pin 4 of the JTAG header to 5V rather than 3.3V. I ripped up the traces, wired a fix and tested. I haven't been able to discover anything else.

The 5V was probably definitely causing an issue and I'm concerned that it may have damaged the device or the JTAG. I believe the MSP-FET has protection for this, but It was also pulling the RST pin of the MSP430 up to 5V, which is beyond the max spec and can damage the chip in unpredictable ways. You might have to swap the MSP430.

I've tried this with no luck. I then tried swapping out the MSP-FET and then the JTAG cable. Neither worked. Finally I tried connecting 3V3 VCC to JTAG pin 2 (rather than 4) by cutting the trace and removing USB power, so as to power from the tool. This also did not work.

I would check the conductivity of the JTAG lines to make sure they are connected. Measure the MSP430 VCC and RST line, and make sure they are the correct voltage. You can also measure the voltage on the Vcore cap, to make sure the CPU core is getting power.

VCC and nRST lines are 3.3V and Vcore cap is 1.94V. Connectivity doesn't seem to be an issue but I'll go over everything again. If you think of anything in the meantime please let me know. I'm out of ideas. Thanks

I don't really have any more ideas. If you're still having issues, you can scope or capture the JTAG and RST signals with an LSA. It should look kind of similar to SPI communication. I would really just look for start sequence from the JTAG, and a response on the TDO line. I imagine there isn't a response on TDO since the FET is reporting unknown target.

I figured it out and I'm ashamed. Pinout coming from the MSP-FET didn't match my header. Pin 1 from the MSP-FET was going to pin 13 of the header, pin 2 from MSP-FET was going to pin 14 (and so on). Can't believe I didn't notice sooner. Anyway thanks for your help.

I'd tried the method you detailed above without any success. I think because I was using an expired trial of rhino (which cannot save) the toolbar plug-in was unable to save the settings properly. So although it was showing the toolbar and I was able to click on it, the Rhino command line didn't recognise it.

That is unfortunate to hear of course - While we consider supporting Rhino Mac in the future as well, there really is no further news nor any potential release date I could share (yet). For now we can only reccomend upgrading your existing machine, or switching to another which is capable of running Enscape.

Hi Demian, I am having the exact same issue and tried your advice but am still having the same issue. I've uninstalled and reinstalled enscape and restarted rhino multiple times. Even when I have the toolbar added, clicking or typing any of the commands still result with the message "unknown command"

After our server was updated to 10.31 the unknown keys feature is presenting itself in a number of profiles. At first all unknown keys were "payloadenabled" which per the release notes can be safely removed.

This Apple article defines those keys:

I ended up creating a new fielvault profile after upgrading to 10.30 since they changed it where it could be separated from the other security and privacy profiles

I wasn't using many keys in the profiles I recreated because I like to keep them as individualized as possible. But I did recreate the ones enforcing filevault and key escrow, removing the old one and applying the new without any issue on my endpoints.

3a8082e126