LabVIEW
error in typedef comparison
I guess you are right "don't follow the BreakPoint enough". Haven't been able to spend very much time on any of the forums lately, and as much as I like the breakpoint one, it is lower on my list that some of the others.
I hope to meet you in person in Austin. I still working on my travel details, have the hotel reserved, but no car or flight yet. Will be just getting back from a trip to California, repack the suitcase and head on down to NIWeek. The repack is due to my going to northern California, requires different clothing than Austin in August. As to the comments on the breakpoint forum regarding Austin, I was told when I went to school there that it reminded one of my classmates of Israel. It will be warm, in the 90's to possible 100 F, with the humidity probably being fairly high (it has been raining in Texas for 45 days). As Altenbach mentioned there is a tendency for a lot of businesses to air condition to excess, so it isn't a bad idea to have a light jacket to wear. A laptop will allow you to communicate with the rest of the world, check on the LAVA NIWeek blog, etc., although I had a weird problem with connecting to the WIFI at the convention center. I even took my laptop to NI's "secret" computer techs (was supposed to be for NI folks, but it was the Alliance day and they hadn't gotten busy yet). They saw the problem but weren't able to help. There is an area with computers on the main conference floor, but you are competing with everyone else. I left mine at my father's house (rather than locked in car or left in room to be stolen) for the last two days, felt nice not having to carry it, or worry about where I could leave it.
Well, will be checking out the "fix" tomorrow at my customer's. It is somewhat inconvenient there, no internet connection and it is about 50 miles from here in farm lands (all back roads).
I hope to meet you in person in Austin. I still working on my travel details, have the hotel reserved, but no car or flight yet. Will be just getting back from a trip to California, repack the suitcase and head on down to NIWeek. The repack is due to my going to northern California, requires different clothing than Austin in August. As to the comments on the breakpoint forum regarding Austin, I was told when I went to school there that it reminded one of my classmates of Israel. It will be warm, in the 90's to possible 100 F, with the humidity probably being fairly high (it has been raining in Texas for 45 days). As Altenbach mentioned there is a tendency for a lot of businesses to air condition to excess, so it isn't a bad idea to have a light jacket to wear. A laptop will allow you to communicate with the rest of the world, check on the LAVA NIWeek blog, etc., although I had a weird problem with connecting to the WIFI at the convention center. I even took my laptop to NI's "secret" computer techs (was supposed to be for NI folks, but it was the Alliance day and they hadn't gotten busy yet). They saw the problem but weren't able to help. There is an area with computers on the main conference floor, but you are competing with everyone else. I left mine at my father's house (rather than locked in car or left in room to be stolen) for the last two days, felt nice not having to carry it, or worry about where I could leave it.
Well, will be checking out the "fix" tomorrow at my customer's. It is somewhat inconvenient there, no internet connection and it is about 50 miles from here in farm lands (all back roads).
Thanks Ben,
Yes I've been a big perponent of action engines since the first time I was introduced several years ago. In this case the problem was my forgetting (overlooking?) the default value coming out of the dequeue if it timed out. Ignoring it if a time out occurs took care of that little problem. The next one is that apparently OPC, or RSLinx, or NI's datasocket implementation, or whatever, doesn't allow me to write to some PLC addresses, and read from others in the same group (i.e. N7:7 is a write address, N7:103 a read). The actual problem seems to be the reading, as I can continue to write to those that are "write addresses", but get one good read from the others, then they return zeros. The RSLinx comm log complains about bad commands, and defines them as type "READ" so I guess our fall back position (having my customer mover the three "write" addresses to a different group) will be our immediate answer.
I don't remember if you said whether you are making it to NIWeek this year? If so, great, always like to see you and the others in person. As one who works mostly in isolation I've come to realize that you folks are my "office mates".
Well, I've got an earthquake to program (another project, that hopefully will be internet live before too long), and there is a LabVIEW user group meeting this morning (morning?!) so I'll sign.
Yes I've been a big perponent of action engines since the first time I was introduced several years ago. In this case the problem was my forgetting (overlooking?) the default value coming out of the dequeue if it timed out. Ignoring it if a time out occurs took care of that little problem. The next one is that apparently OPC, or RSLinx, or NI's datasocket implementation, or whatever, doesn't allow me to write to some PLC addresses, and read from others in the same group (i.e. N7:7 is a write address, N7:103 a read). The actual problem seems to be the reading, as I can continue to write to those that are "write addresses", but get one good read from the others, then they return zeros. The RSLinx comm log complains about bad commands, and defines them as type "READ" so I guess our fall back position (having my customer mover the three "write" addresses to a different group) will be our immediate answer.
I don't remember if you said whether you are making it to NIWeek this year? If so, great, always like to see you and the others in person. As one who works mostly in isolation I've come to realize that you folks are my "office mates".
Well, I've got an earthquake to program (another project, that hopefully will be internet live before too long), and there is a LabVIEW user group meeting this morning (morning?!) so I'll sign.
