46
Technical support / Re:Modbus Master able to change Timers
« on: September 09, 2008, 04:25:23 PM »
Hi, Just read the manual again! and both of my questions are answered. Thanks.
Marcus
Marcus
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.
47
Technical support / Re:Modbus Master able to change Timers
« on: September 09, 2008, 04:17:27 PM »
Hi
I have two questions,
Q1. Do I need to do anything to the TMD to make it respond to polls from a modbus master (my HMI) on either serial port RS232 or RS485 or will it respond as per the memory mapping in chapter 5 of the TMD manual automatically?
Q2. How do I map the DM value to a modbus address i.e. if I store the ADC or DAC value in DM[1], how does this become a modbus address i.e. 40200
Many Thanks Marcus.
I have two questions,
Q1. Do I need to do anything to the TMD to make it respond to polls from a modbus master (my HMI) on either serial port RS232 or RS485 or will it respond as per the memory mapping in chapter 5 of the TMD manual automatically?
Q2. How do I map the DM value to a modbus address i.e. if I store the ADC or DAC value in DM[1], how does this become a modbus address i.e. 40200
Many Thanks Marcus.
48
Technical support / Re:Modbus Master able to change Timers
« on: June 03, 2008, 12:28:30 PM »
OK,
so if I read the ADC and store the value in DM (RAM) then map the modbus to the DM, the HMI will read the values from the DM location. This process doesn't write to the EEPROM, Correct?
Going back to the original question, to change a timer value, the HMI can write a new value to a specific DM location, then use a TBASIC function to monitor if the DM value has changed, and if so, the run a SETTIMERSV to write the new set value to the Timers. As I only intend to change the timers manually once in a while I don't think EEPROM writes are an issue.
As you stated previously to keep the DM Value (timer settings, ADC channel values etc) after power down I would need the MX-RTC.
So now we've cleared that little lot up! is there an existing example of the two main functions needed above i.e.
1. Tbasic program that monitors the DM value and if it has changed use the SETTIMERSV to write the new setting.
2. Map the DM value to a modbus address i.e. read timer 1 setting DM[1] in Modbus address 401001
Kind regards
Marcus
so if I read the ADC and store the value in DM (RAM) then map the modbus to the DM, the HMI will read the values from the DM location. This process doesn't write to the EEPROM, Correct?
Going back to the original question, to change a timer value, the HMI can write a new value to a specific DM location, then use a TBASIC function to monitor if the DM value has changed, and if so, the run a SETTIMERSV to write the new set value to the Timers. As I only intend to change the timers manually once in a while I don't think EEPROM writes are an issue.
As you stated previously to keep the DM Value (timer settings, ADC channel values etc) after power down I would need the MX-RTC.
So now we've cleared that little lot up! is there an existing example of the two main functions needed above i.e.
1. Tbasic program that monitors the DM value and if it has changed use the SETTIMERSV to write the new setting.
2. Map the DM value to a modbus address i.e. read timer 1 setting DM[1] in Modbus address 401001
Kind regards
Marcus
49
Technical support / Re:Modbus Master able to change Timers
« on: June 03, 2008, 09:08:28 AM »
Hi, so are all DM values stored in the EEPROM?
When you read an ADC or a DAC are these values being taking from the EEPROM?
Is there another way to read the values & create alarm setpoints via TBASIC without writing to the EEPROM?
When you read an ADC or a DAC are these values being taking from the EEPROM?
Is there another way to read the values & create alarm setpoints via TBASIC without writing to the EEPROM?
50
Technical support / Re:Modbus Master able to change Timers
« on: June 02, 2008, 12:18:54 PM »
Ok Thanks, I'll give that a go.
Regarding the EEPROM and HMI communication issues, what other functions if not all should I avoid using to much?
I was going to use the ADAM I-7000 units to add around 40 analogue I/O's to the TMD, store the data items in DM then have the HMI read these direct from there. I need to store the value's so I can set alarm points around the values etc.
I'm sure I read on the forum you can write to the EEPROM 1000000 times, if I read 40 analogue values and store them in the DM every second or so, will I kill the EEPROM in next to no time? are the DM and EEPROM the same thing?
is it possible to replace after failure or upgrade the EEPROM to a bigger size?
I'm fairly new to the programing side of things so I appreciate the help.
Regarding the EEPROM and HMI communication issues, what other functions if not all should I avoid using to much?
I was going to use the ADAM I-7000 units to add around 40 analogue I/O's to the TMD, store the data items in DM then have the HMI read these direct from there. I need to store the value's so I can set alarm points around the values etc.
I'm sure I read on the forum you can write to the EEPROM 1000000 times, if I read 40 analogue values and store them in the DM every second or so, will I kill the EEPROM in next to no time? are the DM and EEPROM the same thing?
is it possible to replace after failure or upgrade the EEPROM to a bigger size?
I'm fairly new to the programing side of things so I appreciate the help.
51
Technical support / Modbus Master able to change Timers
« on: June 02, 2008, 09:13:38 AM »
Hi,
Can you tell me if its possible for a modbus master to change the timer settings, read I/O condition within the ladder program?
i.e. change timer "t1" from 100 to 1000 and read or write inputs / outputs from a touch screen HMI as the configured as the modbus master.
Many Thanks
Marcus
Can you tell me if its possible for a modbus master to change the timer settings, read I/O condition within the ladder program?
i.e. change timer "t1" from 100 to 1000 and read or write inputs / outputs from a touch screen HMI as the configured as the modbus master.
Many Thanks
Marcus
53
Technical support / 24 Hour Clock
« on: May 12, 2008, 02:54:41 AM »
Hi, I would like to add a 24H six digit clock to my project, I have looked at the example in the usr directory but when the time is using single numbers i.e 7:9:4 it doesn't look very professional.
Ideally I would like a 24H clock that uses six digits to represent the time in the above example i.e. 07:09:04., or 19:09:04. I have tried adding some code to the above example by adding a "0" in front of the time[1] number if it is lower than 10 but I'm pulling my hair out trying to get it to work.....
Any assistance appreciated.
Ideally I would like a 24H clock that uses six digits to represent the time in the above example i.e. 07:09:04., or 19:09:04. I have tried adding some code to the above example by adding a "0" in front of the time[1] number if it is lower than 10 but I'm pulling my hair out trying to get it to work.....
Any assistance appreciated.