yyh2

Nobody asked for a magic wand... just a well written book about programming techniques. its basic in every other field. for example, you can find many books like it for the leading microcontroller platforms (Arduino,PI, etc...)

I asked a pretty similar question here - And found zero resources on the subject. PLC programming is a top secret subject, apparently.

in Israel the stock is ridiculously low as well, for many many months now.

the last posts ??? any way, any news about thr original question ?

OK Alex, thank you. I'm currently getting 44C at SI15 at max power. the cabinet is vented by a fan blowing near the controller. I think that's reasonable. I will get in touch with unitronics support about the temp ranges.

Well, you're right kratmel. Thank you. I've set analog input 2 as TC-K and gave it an MI. SI15 started to show temp with a decimal point. the MI shows just max range reading since nothing is attached to it. Still waiting for the max temp data, if anyone knows it.

Ok, I get it now. I will be able to try it later at the site as a temporary solution. Currently I'm using a pt100 so no TC are switched on, I suppose it doesn’t work with the pt100 setting since there is no need for temp compensation. Another related question – what would be considered an "OK" PCB temp for this model ? The spec state an environment of up to 50 C (122F), which means a max pcb temp of ? it is installed in a ventilated industrial oven electric cabinet and I suspect 50c is definitely an option. better safe than sorry. Thanks Yam

Kratmel, your method can only work on the thermocouple dedicated ports ? if yes, then it won't work for me, I want it to be available for future use. in that case, I'm better off using a simple temp sensor that can work on any analog input. This should be added to the docs of Visilogic, since it says that only V120/130/350 doesn’t support it.

SM43-J-RA22. i will read the posts and try.

Hey, I tried to get the controller temp on Samba 43. it seems that it cannot set SB14 as HIGH, and therefore can't get any result on SI14. looks like the model doesn't support it, but no info on it in the Docs. Any special ways to make it work ? Regards Yam

on each and every screen ? if so, seems like more than enough.

Fernando, Thank you for you detailed answer. I'm referring to it as a "bug" because it loses the instruction/command. in your situation you called it twice, it’s a different thing (frustrating non the less). in my case, if I called the screen twice, no big deal, but the troublesome part is that it loses the neighboring net. if it's only the double call, it's not an urgent fix anyway, just knowing that here and on the help files is OK (i still suspect though that the "call screen from the L&J menu + multiple P contacts" even without double call, is a scenario the system dislikes). Your ladder suggestion - your solution for a more predictable sequence is a good idea to keep in mind. in an absence of a solution I would definitely use it, but if we can learn how to avoid it, its better. First of all since I wrote the entire program this way 😁 And second, because simpler logic with less set/reset coils as can be, is always my preferred way (a programming sixed sense that was reinforced by Joe Tauser's "Bit Banging" speech way back in the forum), if I can only work with the P contacts and trust them, it's the simplest solution. DW as a timer - I have 4 program times and ML 1,2,3,4 were already used, so I assigned them DW 1,2,3,4 for clarity, no special cause, no other DW were used in the program. Multiple commands in a rung - the argument against it was that it can compile not exactly the way you planned. there is a saying here that "Visilogic don’t charge you by the number of rungs", so split long rungs into simpler ones. I do have some of them with 6 commands in a row, but they are "simpler" commands. parts of the idea for separating them was to diagnose whether "messy" compiling was the reason for missing the net. It didn’t even occur to me to try parallel stuff.

Hey Flex, As I said, maybe it's just the links&jumps menu with the ladder call combined, we'll have to see in the future. It happened to me like 8 times in the last software im working on, and i managed to work around it by changing the ladder order ( mixing nets 10-11-12 in the example). The Visilogic version is 9.8.86 if it matters. P.S As you can observe I'm being very strict about separating command into numerous rungs instead of one huge rung( it will work most of the time, but not all). its mainly due to your comments on the forum's history, emphasizing the importance every time. Thanks 👍

Fernando, thank you for your replay. you posted yours while my replay was pending. Read it and you will see that i complay with your advice.

I think I figured at least some of it out. I was calling the jump from the ladder and the "links & jumps" tab in the same time, by the same operand. its seems that this tab takes precedence over the ladder execution (Bug ?). it fixed the current problem. but this thing happened to me so many times lately, that i suspect maybe its not the only reason (I doubt I did this double call every time , I mean…I do have a long rap sheet of stupid programming , but come on…) Joe, The project is a commercial product so I will get in trouble posting it here, I can give the relevant screenshots. I've attached an example of it. the P contact "MB83" is linked to an HMI button that is changing the screen to the next step. when you press it I want the program to: 1. Load time to a timer (net 10). 2. Read the parameters for the next step (net 11). 3. Copy a vector (program name to main display, net 12). 4. And only then load the next screen (net 13). Dan T, no I don’t use conditional subroutine calls, I was listening very carefully to the forum experts. its mentioned here like every 10 threads, and for good reason. All the sub's are called every scan. Thank you all for your help.