Jump to content

Phillip Brooks

Members
  • Posts

    899
  • Joined

  • Last visited

  • Days Won

    50

Posts posted by Phillip Brooks

  1. On 2/7/2024 at 3:24 PM, Antoine Chalons said:

    Emerson's catch phrase seems to be 'be bold', NI's was 'engineer ambitiously'

    Maybe someone misunderstandood and NI went to 'be bald'

    Is it just me or today's webcast was desperately empty?

    Mickey-Mouses-Hairline.jpeg.e812c8ede217ba3a1d2b59eed12b7587.jpeg

    • Haha 2
  2. 17 hours ago, X___ said:

    So it is the new way to not release any info whatsoever ("NI did not create this content for this release") on new releases?

    I did not see any beta forum either during that all time. This is important to me, as I need to find funding for migrating my code base to a new environment, and any official evidence that NI/Emerson has dropped the ball to a new low (if I can forge this hybrid expression for the occasion) is useful.

    So a Google search shows this phrase on numerous pages at the top and bottom of the body text.

    Is this maybe some sort of tag or something to indicate that a third party is creating the new content (outsourcing of site maintenance?)

    Maybe some sort of a disclaimer that the data may not be accurate or complete; or maybe based on AI generated pages using pull request comments or requirements docs?

    I'm thinking AI because there is so much talk in general about identifying anything created by it.

  3. I've generally stayed at employers for 5-10 years.

    I don't chase the money or aspire to a management position; I look for positions where I can be a problem solver and be close to the product.

    I've now scrapped the third project where I'm working now where business an design plans (or failure to) have tossed my efforts in the trash bin.  I'm now relegated to creating documentation for other people's unfinished work to send outside for manufacture.

    I can limp along, but I'm unhappy arriving at work every day and I'm not sure how long I can continue.

    Maybe I should open up a bicycle shop in the islands and drink from a coconut...

  4. I'm looking at 7-10 years before optimal retirement, barring any health issues.

    I currently support/maintain LabVIEW / TestStand solutions created by Contract Manufacturers. These are being slowly replaced by ODMs developing their own test solutions.

    Is there enough demand out in the world for someone like me to make it to retirement, or do I need to learn to test inside the world of Python / GRPC / Go?

    I don't mind learning new things, but the sheer size and complexity of the systems I see are depressing. Everyone seems to have thier specific editor, build envoronment, source control, format checker and Jira implementation that creates Docker containers that need signing to install on the product to run. WTF? 

    A senior software engineer who doesn't understand LV/TS asked me to document how to deploy my solution and dismissed it because It doesn't create WHLs or get tested with approved checkers like black or flake8.

    Do I learn to work in their world, or follow in the footsteps of Cobol and Fortran programmers and ride LV/TS into the sunset?

  5. I'm guessing that you are new to LabVIEW. It appears that you found your driver on the NI site (http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=E962513CF06C2315E0440021287E6E02) and followed this link:

    image.png.1ff5c969a094c4bcc027ff4cd5625a25.png

    You probably installed the driver, but then skipped down to the bottom and followed the link on how to use Ethernet to control your instrument. Those instructions are for the case where the instrument driver doesn't exist or failed to download.

    image.png.bcde308dbeebc8fc3f961b59c783a913.png

     

    You missed the part in the middle (step 7) to look for and USE the driver.

    The driver I found looks very clean and should work as a starting point for you.

    You will need to learn the basics of LabVIEW.  I would suggest that you start on the NI site for new user help. NI has dedicated resources to support new users. 

    LAVA is a LabVIEW related site, but the name stands for LabVIEW Advanced Virtual Architects. Beginning questions are not likely to receive much help...

  6. 15 hours ago, infinitenothing said:

    Localhost is a little faster: 3.4gbps

    Seeing 80% CPU use single logical processor and 35% averaged over all the processors

    iperf on local host with default options isn't doing great: ~900Mbps but very little cpu use

    I suspect there's a better tool for Windows.

    Are you using the parallel streams option in iperf3? This will help saturate the link.

    https://documentation.meraki.com/General_Administration/Tools_and_Troubleshooting/Troubleshooting_Client_Speed_using_iPerf#Parallel_Streams_2

  7. 5 hours ago, Rolf Kalbermatter said:

    Leaves Reddit, Stackoverflow and YouTube, which I almost never follow. But from what I have seen there, the quality is often very limited both for questions and the answers that are given.

    I tried a few years ago to participate on Stackoverflow re: LabVIEW questions, but there was little or no ability to include graphics/images. Whenever I did (using off-site links etc...) moderators who knew nothing about LabVIEW would delete links or downvote my answer to oblivion stating I wasn't following the guidelines. I called them out and told them that they needed to understand the language and I got emails and messages threatening to delete or limit my account. I just stopped participating. Not a friendly environment; but I do find lots of solutions to my Python problems there :)

  8. The creator of the class had provided an example code module that included functions with a return value tuple of (bool, str) representing function call success and optional string.

    I was conflating this return value in the example with an error. We modified the wrapper code module functions to raise an exception. 

    I learned that the LabVIEW Python Node 'error out' connector handles a Python raise exception by returning an error with a code of 1671 and source string that contains the exception message ( is this documented somewhere? )

    This is very nice! Now if we call a function where the Python object is in the wrong state, we get a LabVIEW error 1671 and the class exception string within the error out source (.e.g. "Failure to add measurement; test_run_state = [IDLE]").

     

  9. Has anyone ever had to receive calibration / parametric data from a vendor using EDI?

    I personally will get the data from our internal systems but it seems that no one I've spoken to inside my company has ever had to receive serial number specific calibration data before.

    Right now, we get PDFs with data that we have to transcribe manually into our tests.

    I want to point the business / IT folks to some sort of specification but have no experience with EDI.  Some spelunking returned "EDI Specification 863" which might be right by the description...

     

  10. On 1/28/2022 at 6:48 PM, X___ said:

    Personally, Colonel Kodosky's vision scares the bejesus out of me. I imagine an application whose diagram contains a single icon of itself, which when you click into it, sucks you into the matrix and shreds you to bits... I mean wires.

     

    Just watched the video 

    2022-02-02_9-03-47.jpg.a657807932ea9ad156e23131c4399ed5.jpg

     

     

    • Haha 1
  11. 1 hour ago, ShaunR said:

    That doesn't make much sense. Only one of these parties can have culpability and culpability cannot be transferred.

    NI is in Texas, and nothing makes sense in Texas - 

    https://www.texasmonthly.com/news-politics/texas-abortion-law-explained/

         "SB 8 allows any private citizen in Texas, or elsewhere, to sue anyone who performs an abortion in the state after an embryo’s cardiac activity can be detected.

           It also allows any private citizen to sue anyone (in Texas or elsewhere) who “aids or abets” anyone in getting an abortion in Texas after that period or anyone who intends to aid or abet that process."

     

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.