1
Technical support / Re:Writemodbus
« on: February 15, 2012, 09:04:21 AM »
SETSYSTEM 6,6 Worked like a charm! Thank you
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
2
Technical support / Writemodbus
« on: February 14, 2012, 05:03:41 PM »
Greetings,
I have an F2424 that I'm setting up to control 5 VFDs via rs485. There are 3 Powerflex 400 drives and 2 Powerflex 4 drives. I can read the drives status easily using READMODBUS. However, when I use WRITEMODBUS or WRITEMB2, STATUS(2) returns 0. This is only the case with the PF400, the PF4 works fine.
I set up a serial monitor, to read what the plc was sending, then using the terminal, sent the commands manually to see what the response from the drive was, as follows:
PLC command: WRITEMODBUS 13, 102, 8192, 13586
"start command" 66 10 20 00 00 01 02 35 12 9E FD
response from PF400: 66 90 01 3C 1F
Function Code 16 sent Exception Code 1 returned
So I created the same command and sent manually from my pc only using Function Code 06 and repeated the experiment:
"start command" 66 06 20 00 35 12 1d 40
response from PF400: 66 06 20 00 35 12 1d 40
In the end I was able to manually start and stop the PF400
using Function Code 06, but always got Exception Code 1 when using Function Code 16. So my inital conclusion is that the PF400 drives only accept write function 06.
Question:
Will TBasic WRITEMODBUS and WRITEMB2 only use Function code 16? Is there an easy way to send Function Code 06 instead of 16?
Regards,
Derek
I have an F2424 that I'm setting up to control 5 VFDs via rs485. There are 3 Powerflex 400 drives and 2 Powerflex 4 drives. I can read the drives status easily using READMODBUS. However, when I use WRITEMODBUS or WRITEMB2, STATUS(2) returns 0. This is only the case with the PF400, the PF4 works fine.
I set up a serial monitor, to read what the plc was sending, then using the terminal, sent the commands manually to see what the response from the drive was, as follows:
PLC command: WRITEMODBUS 13, 102, 8192, 13586
"start command" 66 10 20 00 00 01 02 35 12 9E FD
response from PF400: 66 90 01 3C 1F
Function Code 16 sent Exception Code 1 returned
So I created the same command and sent manually from my pc only using Function Code 06 and repeated the experiment:
"start command" 66 06 20 00 35 12 1d 40
response from PF400: 66 06 20 00 35 12 1d 40
In the end I was able to manually start and stop the PF400
using Function Code 06, but always got Exception Code 1 when using Function Code 16. So my inital conclusion is that the PF400 drives only accept write function 06.
Question:
Will TBasic WRITEMODBUS and WRITEMB2 only use Function code 16? Is there an easy way to send Function Code 06 instead of 16?
Regards,
Derek
3
Technical support / Re:F1616BA Run Error
« on: October 11, 2011, 05:52:26 PM »
Yes, I tried powering down and back up, the run error light comes back on. The first time it happened a few weeks ago, I just re-loaded the same program again, and the error went away. This week though, re-loading several times, had no effect, error every time. The fix was loading in a blank program, which ran with no error, then re-loading my program.
I'll be sure to use "reset" from now on, will report any further problems.
Thanks for your help.
I'll be sure to use "reset" from now on, will report any further problems.
Thanks for your help.
4
Technical support / Re:F1616BA Run Error
« on: October 11, 2011, 04:59:14 PM »
The Java folder on my computer does contain a folder "j2re1.4.2_19" that was modified the same date I upgraded iTrilogi on 8/19/11 so I suspect that is what's being used when I run iTrilogi and Tlserver.
5
Technical support / Re:F1616BA Run Error
« on: October 11, 2011, 04:44:13 PM »
1.) The transfer went smoothly, and aways has, however the first time I had the run error a few weeks ago, I thought maybe I clicked on "reboot" too quickly when it was finished.
2.) Transfered via the rs232 serial port. Kep mmi and a thermocouple module are connected to rs485 ports.
3.)i-Trilogi version 6.43 build 01. JRE 6.0.230, I read the posts about problems with JRE, but I never experienced problems opening TLServer so I haven't been concerned until now. I'm running windows 7 Professional 6.1 32bit.
4.)I did run the upgrade not too long ago.
2.) Transfered via the rs232 serial port. Kep mmi and a thermocouple module are connected to rs485 ports.
3.)i-Trilogi version 6.43 build 01. JRE 6.0.230, I read the posts about problems with JRE, but I never experienced problems opening TLServer so I haven't been concerned until now. I'm running windows 7 Professional 6.1 32bit.
4.)I did run the upgrade not too long ago.
6
Technical support / Re:F1616BA Run Error
« on: October 10, 2011, 12:17:49 PM »
Gary,
As far as I can tell so far, I don't see a problem with the program. The run error went away without making any changes, other than re-loading it.
Also, in trying to diagnose what the problem was, I loaded the program "Analog-Timer.PC6" from the samples folder. The PLC indicated a run error in CF10 which contains only this:
SETLCD 2,3, "Timer #1 PV=" + str$(timerPV[1],4)
It all seemed a bit odd, like there's a glitch somewhere. It only happens right after loading a program,only twice after maybe 30 times of loading up programs, and the fix so far has not included any change in code, only re-loading.
Thanks for your input, I've learned a lot from your other posts.
Derek
As far as I can tell so far, I don't see a problem with the program. The run error went away without making any changes, other than re-loading it.
Also, in trying to diagnose what the problem was, I loaded the program "Analog-Timer.PC6" from the samples folder. The PLC indicated a run error in CF10 which contains only this:
SETLCD 2,3, "Timer #1 PV=" + str$(timerPV[1],4)
It all seemed a bit odd, like there's a glitch somewhere. It only happens right after loading a program,only twice after maybe 30 times of loading up programs, and the fix so far has not included any change in code, only re-loading.
Thanks for your input, I've learned a lot from your other posts.
Derek
7
Technical support / F1616BA Run Error
« on: October 10, 2011, 10:59:48 AM »
I have an f1616BA with a Kep MMI6050 touch screen running a vertical form/Fill/Seal packaging machine and a net weigh filler for filling 2lb bags of coffee. It's been online now for a few weeks. I love the PLC, it's my first full scale PLC project. I worked through the entire programming process with need for tech support, the manuals are excellent.
I've been making adjustmets to the program. This morning I tried to load my program, with the only change being in a CusF, the counter number in a setcsv statement. After loading, I clicked on re-boot as I always have before, and the run error light came on. The PLC put on the lcd display Undef Inter. cf12. Being sure the program was ok. I tried to re-load with the same result. I then tried to load an older version of the same program, run error. Next I tried to load the "blank" program from the samples folder. This time no run error. So I tried loading my program again, run error. I also tried power off/on in between loading programs, no effect. Next I loaded "Analog-Timer" from the sampes folder, run error undef inter. CF10. CF10 only has a setlcd command.
Next I loaded the blank program again, then my program and no run error, everything is now working normally.
What could be causing this? It happened to me once a few weeks ago, I re-loaded the the program, and it worked fine after that. It didn't happen again until today. I'm concerned now about loading the program for minor changes, and rendering my machine useless. This is a machine we depend on daily, it can't be down for long. Any ideas?
Best Regards,
Derek
I've been making adjustmets to the program. This morning I tried to load my program, with the only change being in a CusF, the counter number in a setcsv statement. After loading, I clicked on re-boot as I always have before, and the run error light came on. The PLC put on the lcd display Undef Inter. cf12. Being sure the program was ok. I tried to re-load with the same result. I then tried to load an older version of the same program, run error. Next I tried to load the "blank" program from the samples folder. This time no run error. So I tried loading my program again, run error. I also tried power off/on in between loading programs, no effect. Next I loaded "Analog-Timer" from the sampes folder, run error undef inter. CF10. CF10 only has a setlcd command.
Next I loaded the blank program again, then my program and no run error, everything is now working normally.
What could be causing this? It happened to me once a few weeks ago, I re-loaded the the program, and it worked fine after that. It didn't happen again until today. I'm concerned now about loading the program for minor changes, and rendering my machine useless. This is a machine we depend on daily, it can't be down for long. Any ideas?
Best Regards,
Derek
Pages: [1]