Jump to content

Bjarne Joergensen

Members
  • Content Count

    122
  • Joined

  • Last visited

Community Reputation

2

About Bjarne Joergensen

  • Rank
    Very Active
  • Birthday 07/01/1961

Profile Information

  • Gender
    Not Telling

LabVIEW Information

  • Version
    LabVIEW 2015
  • Since
    1997

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi Thanks I´ll stick to 2020 for both LabVIEW and TestStand There's a lot of thinks going on at NI that I think we all are a little bit nervous to hear about /Bjarne
  2. Hi We are going to upgrade our LabVIEW 2015 to ? Should we go for the latest version 2020, one in between or wait for 2021? We will also start using TestStand and I have the same question for that. 2020 or older. Thanks in advance Bjarne
  3. Sorry for late reaction. I manage to get i to work by using "Microsoft TreeView Control 5.0 (SP2)" instead of "Microsoft TreeView Control 6.0 (SP6)" and "Microsoft Windows Common Controls 5.0 (SP2) Version 1.3" It works on my PC, but when I export the VI to another PC it's seems it fall back to "Microsoft TreeView Control 6.0 (SP6)":(
  4. I tried to download VBRT, but it didn't help. I don't know if it's a part of it?. When you have to register things in SysWOW64 , do you then use Regsvr32?
  5. Edit: I found this "mscomctl.ocx" under SysVow64. I have registered it, but LabVIEW still say it's not registered! Has it something to do with LV15 =32bit and "msconctl.ocx" is in 64bit system folder?
  6. Hi I got an old LabVIEW 8.2 VI that use ITreeView under Windows XP. It works fine. Now I have upgraded to LV15 and Windows 8.1 and I got an error "Library not registered in mxLT Open Tree Control.vi" I would like register the library, but where do I find it? I have search the WEB but didn't find anything i could use(or understand;)) Edit: I found this "mscomctl.ocx" under SysVow64. I have registered it, but LabVIEW still say it's not registered! Has it something to do with LV15 =32bit and "msconctl.ocx" is in 64bit system folder? Here is the BD of "mxLT Open Tree Cont
  7. Please don't misunderstand me ? My intention was to remind my developer group to remember the prefix on the file names and make them sure they don't want the prefix if they try to save without!
  8. HI When saving a new VI LabVIEW default name it "Untitled#x.vi". Is is possible to change that to something else like "TSVWS - #x.vi" An maybe also popup a warning if you try to rename i without "TSVWS - " as prefix. regards Bjarne
  9. Hi ShaunR - polynomium 0x755b - initial_crc 0xffff - reversering af 8-bit input data - reversering af 16-bit output crc
  10. Hi I have done that and can't find any CRC calculator that give the same result I got these data: 0x00, 0x01, 0x02, 0x80, 0xe2, 0x45, 0x00, 0x00, 0x00, 0x00, 0x07, 0xdf, 0x33, 0x00, 0x00, 0x00, 0x0f, 0xeb, 0x02, 0x80, 0xe2, 0x45, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00 and expect this CRC16: 0xcd58 regards Bjarne
  11. Hi I have this code in C(and I don't understand it ) Is there someone that can help me translate it to labview? Thanks in advance. Bjarne typedef uint16_t (*bit_order_16)(uint16_t); typedef uint8_t (*bit_order_8)(uint8_t); uint16_t straight_16(uint16_t value) { return value; } uint16_t reverse_16(uint16_t value) { uint16_t reversed = 0; for (int i = 0; i < 16; ++i) { reversed <<= 1; reversed |= value & 0x1; value >>= 1; } return reversed; } uint8_t straight_8(uint8_t value)
  12. Thanks hooovahh I'v done it with Labview Server this way I have to dive in the static VI references and Start Asynchronous calls because I also use LV2013 /Bjarne PS: How does a "wholly crap cake" look like
  13. Hi I have a challenge on a test system. I have a PCB where there is an IC to be uploaded with the code. It takes ~5 min. per. PCB. To follow takt time it must be possible to program up to 5 at a time. It should be done in the way that the operator can start a PCB independent of the other PCBs are startet! Programming is startet and monitored as follows. 1. The operator sets an SD card in the PCB and press start. 2. The test opens a serial port to the board and turn on the power to the board 3. PCB runs the programming process itself and sends information via the serial port. 4. The test
  14. Don't you hook it up to a device? /Bjarne
×
×
  • Create New...

Important Information

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