# (HELP) sample-MODBUS driver deployed with Eclipse on Gataway **URL:** \ **Category:** 3rd Party Modules\ **Created:** [December 7, 2015, 7:11am UTC](https://forum.inductiveautomation.com/t/help-sample-modbus-driver-deployed-with-eclipse-on-gataway/10878 "2015-12-07T07:11:48Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![AlFaSoft](https://avatars.discourse-cdn.com/v4/letter/a/54ee81/32.png) [@AlFaSoft](https://forum.inductiveautomation.com/u/AlFaSoft)\ **Post date:** [December 7, 2015, 7:11am UTC](https://forum.inductiveautomation.com/t/help-sample-modbus-driver-deployed-with-eclipse-on-gataway/10878/1 "2015-12-07T07:11:48Z")
I’m a developer and I and my company are about to develop a new device driver for the ignition’s Gateway. At the beginning, I was inspecting some of your examples included in the SDK package, particularly the MODBUS driver. Unfortunately, as soon as I build and deploy the MODBUS Driver v2 onto Ignition Gateway, it happens that the list of the drivers still the same! That is, the gateway displays the old same items, I could see even after the ingnition’s setup. here you go the steps undertaken: - On Eclipse’s Package Explorer, at the node “ModbusDriver\_Build”, I launch Build.XML via AntBuild; - The module compilation and its deployment on the Gateway succeed! In fact, among the messages of the console, it reports “Installing Modbus driver v2 on Ignition Gateway.” and then"BUILD SUCCESSFUL. Total time: 5 seconds". - In the Eclipse’s workspace the file Modbus Drivcer v2-unsigned.modl is successfully built!!! - After logged in the Gataway through the web browser, selecting Configuratiuon tab, then, under OPC-UA, clicking Devices and finally, on the left side of the page clicking “new device”, it is possible obtaining the list of the available communication drivers; - But here the new deployed driver doesn’t appear. Any suggestion is appreciated! Alessandro. ---
**Author:** ![Amarth](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/amarth/32/3313_2.png) [@Amarth](https://forum.inductiveautomation.com/u/Amarth)\ **Post date:** [December 7, 2015, 10:22am UTC](https://forum.inductiveautomation.com/t/help-sample-modbus-driver-deployed-with-eclipse-on-gataway/10878/2 "2015-12-07T10:22:22Z")
Maybe there is a “conflict” between the version you are building and installing and the modbus driver module included with an express Igntion installation ? Have you tried to uninstall the included modbus module before installing yours ? ---
**Author:** ![AlFaSoft](https://avatars.discourse-cdn.com/v4/letter/a/54ee81/32.png) [@AlFaSoft](https://forum.inductiveautomation.com/u/AlFaSoft)\ **Post date:** [December 7, 2015, 11:32am UTC](https://forum.inductiveautomation.com/t/help-sample-modbus-driver-deployed-with-eclipse-on-gataway/10878/3 "2015-12-07T11:32:41Z")
I just have it. Now the module seems be installed with name MODBUS 2. Thank you Amarth! But now I can’t understand why the State is: - Faulted API version Mismatch intead of: - RUNNING I’m using the Module SDK version 7.7.5 and the Ignition designer version 7.8.0. Must they be of the same version number??? ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [December 7, 2015, 12:35pm UTC](https://forum.inductiveautomation.com/t/help-sample-modbus-driver-deployed-with-eclipse-on-gataway/10878/4 "2015-12-07T12:35:44Z")
[quote=“AlFaSoft”]I’m using the Module SDK version 7.7.5 and the Ignition designer version 7.8.0. Must they be of the same version number???[/quote]Yes and no. The key is the requiredframeworkversion property in module.xml. That has to match the platform. v7.8 uses framework 7. v7.7 uses framework 6. Consider using the [maven-based sdk](https://github.com/inductiveautomation/ignition-sdk-examples) hosted on github. ---
**Author:** ![AlFaSoft](https://avatars.discourse-cdn.com/v4/letter/a/54ee81/32.png) [@AlFaSoft](https://forum.inductiveautomation.com/u/AlFaSoft)\ **Post date:** [December 11, 2015, 7:41am UTC](https://forum.inductiveautomation.com/t/help-sample-modbus-driver-deployed-with-eclipse-on-gataway/10878/5 "2015-12-11T07:41:53Z")
Hi, I’ve just downgraded the Ignition platform back to the version 7.7.0 . The ModBus driver I found in the bundle SDK 7.7.5 seems be properly deployed and finally runs in the gateway. Thank you Phil!! Other questions: - Is the framework brought by Ingnition’s setup? Among the components shown at Ignition Designer -\> Help -\> About … I can’t see a component named “framework”. - Therefore, how could I get the framework version? Regards, Alex ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [December 11, 2015, 1:27pm UTC](https://forum.inductiveautomation.com/t/help-sample-modbus-driver-deployed-with-eclipse-on-gataway/10878/6 "2015-12-11T13:27:47Z")
It’s in module.xml in your project’s build folder. ---
**Author:** ![PerryAJ](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/perryaj/32/3281_2.png) [@PerryAJ](https://forum.inductiveautomation.com/u/PerryAJ)\ **Post date:** [December 11, 2015, 11:28pm UTC](https://forum.inductiveautomation.com/t/help-sample-modbus-driver-deployed-with-eclipse-on-gataway/10878/7 "2015-12-11T23:28:27Z")
SRContext contains the FRAMEWORK\_VERSION constant should you ever need to reference it programmatically. For simple reference: here are the frame versions and how they relate to Ignition API Versions. 7.0 = Framework version 1 7.1 = Framework version 1 7.2 = Framework version 2 7.3 = Framework version 3 7.4 = Framework version 4 7.5 = Framework version 4 7.6 = Framework version 5 7.7 = Framework version 6 7.8 = Framework version 7 The API is generally stable for backwards compatibility. Versions are changed only when we make additions, so if you have a 7.7 module, you should be able to rebuild it with the framework version 7 tag (or simply change the module.xml as Phil said) and be good to go.