Joe Tauser

I am able to connect to a remote V350 on a cellular modem with the PC version of Remote Operator. I put the same settings on the Android version and I get a connection error. I am also able to see the remote PLC in Visilogic. What is the network ID field for on the Android version? Joe T.

I think one of these placed over the I/O expansion port when the unit is shipped would work just fine: Joe T.

Yesterday I had a customer plug his Ethernet cable into the I/O expansion port on a V700 and try to figure out why he couldn't talk to it for two days. I think he's still kicking himself, and I'm personally worried about his self-esteem level. The really sad thing is I did the same thing last week, only I figured it out in less than an hour. To the Creators - Please put a big red sticker around the expansion port on all PLC models that says "Ethernet not go here! I/O Cable!" or something. Make sure you use caveman language, as that is what I think it will take for my brain to actually understand. I know the molded-in legend is too hard to see for us folks over 40. Joe T.

I've never tried it, but did you look at the value in SI 274? Joe T.

Unfortunately that is not an option with the current revision of Visilogic. Creator input? Joe T.

Your program has a good beginning. Is the problem in sending or receiving? Have you connected a terminal? Let us know a specific problem. Do you know about the serial buffer monitor in the Info Mode? Joe T.

Did you go to Mexico to take this picture?

+1 Keeping track of which MIs and MBs were in the exported routine is next to impossible, and it has stomped on code I've already written. Joe T.

I'm working on a program that tests 32 motors with one of eight tests. All eight tests can run at the same time, and any of the motors can be assigned to any test. I've already developed the code to edit the tests in one data table and assign test numbers to each motor in another data table, along with leaving space for each motors test data. These tests are not fast - the motor is on for several hours and then off for hours (pool and spa pumps) for several thousand cycles. I'm just monitoring high and low amp levels. Response time is not critical. Here is my monster-brain idea - I can make a program with pointers that will step through the test table, determine the test members, check the current levels, and write the time accumulators and error codes back to the test table and the motor table. This way I only need to write one test routine, loopy and convoluted as it may be. The question I have is whether extensive data table reads and writes are any harder on the memory and scan time than regular operations on MIs and MBs. I figured if I run the loop every second I will have ample control over the test. Or I can write eight nearly identical test routines, which will be simpler but can be a pain in the butt to edit when I figure out that my initial genius programming ideas don't work. (Yes, that does happen). Thoughts and comments? Joe T.

I have a customer who does it with a converter box that simplifies the codes. The box he uses takes RS232 commands; he writes his lighting shows in Unitronics and then send basic commands to the converter. DMX512 is based on the RS485 hardware layer, so it can theoretically be done with only the PLC. You'll have to get a copy of the DMX protocol and use the Protocol block to handle everything. Joe T.

You will need to become very familiar with the Protocol block, which will allow you to output whatever you want out of the RS232 port. Do you have the protocol guide for the device you're trying to talk to? I'd recommend determining the strings you'll need for the device and then practicing with a terminal program connected to the PLC instead of the device so you can get your code right. Joe T.

Did you try 115.2K baud? There's a little nuance in the O/S updater where it doesn't try all possible baud rates before giving up. Joe T.

Post your code. Joe T.

Maybe. What do you know about this signal? Do you have a command set? Joe T.

Do you have "Run as Administrator" set in the U90 shortcut properties? Joe T.

Attach and upload! Joe T.

Can you post your code? Joe T.

End of what track? Do you have a picture or mechanical drawing? Joe T.

Nildo- So it looks like A70 is some kind of scaling module configured by which input pins are tied to +24V. Thanks for the clarification on K1. You have to tell your doctor these things. I'll check my email tomorrow, but for purposes of the forum which I/O module are you using? To get a HSC on a V1210 you'll need a snap IO module (one of the V200s). Joe T.

https://www.linkinstruments.com/oscilloscope.html These guys are in New Jersey and have been good to work with. They actually design these things. I blew mine up once by connecting the probe ground lead to what I thought was a grounded heat sink (actual voltage - 60V). The thing I didn't realize was the ground on the probe is not isolated from the ground on the USB plug, which is grounded through the computer when you have your battery charger plugged in. I blew up that USB port, too. Anyway, I called them and they had me send it in for repair - the bill was $75. I have the older brother of the MSO-9201. Not cheap, but I love my tools and I've spent more money on more useless stuff (like Allen Bradley Tech Connect contracts). It does spectrum analysis, too, which is really good for looking at drive harmonics and then showing the customer how they match up to noise on DC PLC inputs because they were either stupid or too cheap and ran their motor wires in the same conduit as their signal wires. Invest in a 100:1 probe if you want to go there. The maximum input of the included 10:1 probes is 500V peak. I can tell you that my street cred with the customer increases by an order of magnitude when I get this thing out and show detailed pictures of their signals. Once again - the inductive flyback pulse is the most dramatic. I've seen it induce spikes across traces on a V200-19-E1B and cause a PLC's watchdog timer to kick out. Joe T.

Label your diagram better. Where are the liquid and gross counter pulses coming from? Joe T.

That solution brings to mind a story - years ago I had a bottle counting problem with a polarized retro-reflective photoeye and the customer swore there was something wrong with my program. I bought one of those little USB oscilloscopes (wanted one anyway; just needed an excuse) and it pointed out that the neck of the bottle was occasionally causing a tiny double pulse. In that case we had to re-position the eye, but the problem was uncovered. I still keep it in my car and get it out to help solve mystery input problems caused by drive noise or inductive flyback pulses coming off contactors. It is a great troubleshooting tool. Joe T.

Use a positive transition contact tied to the bit assigned to the button in your logic. Joe T.

I think we missed your window. I've been busy and the Unitronics office is getting a new computer system, which is why they haven't been answering posts. You'll need to set up one of the serial ports and make a cable to talk to this meter. Configure another Modbus port as an RTU master. I looked at the documentation. They did the usual silliness and imply that the user somehow has to generate his own hex codes to implement Modbus. No, you do not have to do this. Page 10 shows the Modbus Register Address Table (in hex- convert these to decimal). Note that these are Long registers - I'm a little rusty on getting these into Unitronics but it can be done. I think you set ML's as the register type in the Read Holding Registers block. Hook it up and start beating on it. Joe T.

That should have worked. Post your code. Joe T.