1. Home
    1. Dashboard
    2. Search
  2. Forum
    1. Unresolved Threads
    2. Members
      1. Recent Activities
      2. Users Online
      3. Team Members
      4. Search Members
      5. Trophys
  3. Articles
  4. Blog
  5. Videos
  6. Jobs
  7. Shop
    1. Orders
  • Login or register
  • Search
This Thread
  • Everywhere
  • This Thread
  • This Forum
  • Articles
  • Pages
  • Forum
  • Blog Articles
  • Products
  • More Options
  1. Robotforum - Support and discussion community for industrial robots and cobots
  2. Forum
  3. Industrial Robot Support and Discussion Center
  4. Yaskawa Motoman Robot Forum
Your browser does not support videos RoboDK Software for simulation and programming
Visit our Mainsponsor
IRBCAM
Robotics Channel
Robotics Training
Advertise in robotics
Sponsored Ads

Motoman Robot job security

  • Stanley1012
  • May 24, 2020 at 9:46 AM
  • Thread is Unresolved
  • Stanley1012
    Trophies
    3
    Posts
    7
    • May 24, 2020 at 9:46 AM
    • #1

    Hey guys, I'm currently programming a DX200 for a client:smiling_face_with_horns: that i have recently come to realize doesn't like to pay up:loudly_crying_face::loudly_crying_face:. The project is almost completed with over 120hrs of work time invested. My question is what are creative ways i could ensure payment? via yaskawa robot, whilst remaining professional.

  • Robodoc
    Reactions Received
    56
    Trophies
    7
    Posts
    1,059
    • May 24, 2020 at 1:57 PM
    • #2

    Start the proceedings to put a lean against the company that owes you money.

    Do not do "something" to the robot. Any malicious software or settings, or if you go back and remove the main processor when everyone is on lunch, can be considered industrial espionage. A charge like this on your record may prevent you from getting new contracts or traveling over an international boarder.

    Robodoc

  • 95devils
    Reactions Received
    234
    Trophies
    8
    Posts
    1,947
    • May 25, 2020 at 2:03 PM
    • #3

    What I have seen is the programmer makes a full backup (cmos and individual files). They load the cmos that was saved before they started. The system is in the as installed state and hardware is fully functional, just not programmed to do anything.

    This was done in a very rare cases where the customers had no issues just did not want to sign off. They wanted the equipment to run and make them money but did not want to sign off for ownership and final milestone payment.

    I know a thing or two, because I’ve seen a thing or two. Don't even ask about a third thing. I won't know it.

  • Stanley1012
    Trophies
    3
    Posts
    7
    • May 26, 2020 at 10:41 AM
    • #4

    Guys thanks for the advice. The problem here is not the final customer but the contractor however, here is my plan to ensure i get paid.

    -- Change the Management mode password.

    -- Disable job edit function while enabling the modification of position data.

    --Hand over factory delivered CMOS and setting files as back on job completion.

    As i know for a fact the final customer could like to add another variant to their production line, this mild changes brings no one in harms way but ensures the project stops and questions asked when big changes are needed.

  • msklorz
    Trophies
    3
    Posts
    11
    • May 28, 2020 at 10:48 AM
    • #5

    Stanley1012

    If you do so, please remember, it is quite easy to find current management mode password in actual CMOS file.

    You should try to use all legal means first before You decide to remove/block programs you wrote.

  • WhyDoesMyRobotHateMe
    Reactions Received
    9
    Trophies
    3
    Posts
    50
    • May 29, 2020 at 3:59 PM
    • #6
    Quote from Stanley1012

    Guys thanks for the advice. The problem here is not the final customer but the contractor however, here is my plan to ensure i get paid.

    -- Change the Management mode password.

    -- Disable job edit function while enabling the modification of position data.

    --Hand over factory delivered CMOS and setting files as back on job completion.

    As i know for a fact the final customer could like to add another variant to their production line, this mild changes brings no one in harms way but ensures the project stops and questions asked when big changes are needed.

    I don't know what country you live in so obviously business/corporate/industry/criminal codes vary wildly, but there are few common (albeit sometimes named or worded differently) laws and statutes you should probably be aware of:

    - You do not own the robot, you own your intellectual property: that is, your program. And that too, is dependent on what your contract looked like when you signed it. What this means is anything you do to their equipment or existing IP assets (their programs, their CMOS, etc etc) is considered very much the same as you tampering with their pipes, wiring or roof. Property damage, sabotage, extortion, anti-trust; these are all terms you could see on a subpoena with your name on it.

    -Your property, as a digital asset, is only yours as much as you can prove it is. If you aren't already, you should be having the people who hire you sign a document drafted by a legal professional outlining the scope of what services and products are yours, the limited liability of said products, and conditions for default or renege. if the contract you signed hasn't been met by the contractor, but you have no way of proving you wrote what you did, they could very easily just claim it as their own. And they will have no trouble proving that you did anything to their existing infrastructure, trust me.

    - The best vengeance you can take is being honest with your industry peers and clients. If these people don't pay, make sure everyone knows they don't pay. It doesn't take long for a crap company to sink with a bad reputation.

    Even if your plan goes full best case scenario; it's rife with opportunity for a company like that to trap you and even pin worse charges on you. Don't do it.

Advertising from our partners

IRBCAM
Robotics Channel
Robotics Training
Advertise in robotics
Advertise in Robotics
Advertise in Robotics

Job Postings

  • Anyware Robotics is hiring!

    yzhou377 February 23, 2025 at 4:54 AM
  • How to see your Job Posting (search or recruit) here in Robot-Forum.com

    Werner Hampel November 18, 2021 at 3:44 PM
Your browser does not support videos RoboDK Software for simulation and programming

Tag Cloud

  • abb
  • Backup
  • calibration
  • Communication
  • CRX
  • DCS
  • dx100
  • dx200
  • error
  • Ethernet
  • Ethernet IP
  • external axis
  • Fanuc
  • help
  • hmi
  • I/O
  • irc5
  • IRVIsion
  • karel
  • kawasaki
  • KRC2
  • KRC4
  • KRC 4
  • KRL
  • KUKA
  • motoman
  • Offset
  • PLC
  • PROFINET
  • Program
  • Programming
  • RAPID
  • robodk
  • roboguide
  • robot
  • robotstudio
  • RSI
  • safety
  • Siemens
  • simulation
  • SPEED
  • staubli
  • tcp
  • TCP/IP
  • teach pendant
  • vision
  • Welding
  • workvisual
  • yaskawa
  • YRC1000

Thread Tag Cloud

  • abb
  • Backup
  • calibration
  • Communication
  • CRX
  • DCS
  • dx100
  • dx200
  • error
  • Ethernet
  • Ethernet IP
  • external axis
  • Fanuc
  • help
  • hmi
  • I/O
  • irc5
  • IRVIsion
  • karel
  • kawasaki
  • KRC2
  • KRC4
  • KRC 4
  • KRL
  • KUKA
  • motoman
  • Offset
  • PLC
  • PROFINET
  • Program
  • Programming
  • RAPID
  • robodk
  • roboguide
  • robot
  • robotstudio
  • RSI
  • safety
  • Siemens
  • simulation
  • SPEED
  • staubli
  • tcp
  • TCP/IP
  • teach pendant
  • vision
  • Welding
  • workvisual
  • yaskawa
  • YRC1000

Similar Threads

  • How do Fanuc Robots compare to others such as Denso, Motoman, Nachi, etc...

    • gdemark
    • April 28, 2015 at 2:15 PM
    • Fanuc Robot Forum
  • Does the SV3X have hard limits (other than metal on metal)?

    • RoboDad
    • June 4, 2018 at 6:08 AM
    • Yaskawa Motoman Robot Forum
  • Alarm 200 robot conform parameter in yasnac mrc

    • 092103
    • May 10, 2017 at 1:55 PM
    • Yaskawa Motoman Robot Forum
  • MOTOMAN YR-ES165N-A00 Robot with NX100 Control, Alarm 0020 cpu com error 51

    • Ratfink
    • September 8, 2016 at 9:04 AM
    • Yaskawa Motoman Robot Forum
  • Newby

    • CTJohnB
    • August 22, 2016 at 2:08 PM
    • KUKA Robot Forum

Tags

  • robot
  • motoman
  1. Privacy Policy
  2. Legal Notice
Powered by WoltLab Suite™
As a registered Member:
* You will see no Google advertising
* You can translate posts into your local language
* You can ask questions or help the community with your knowledge
* You can thank the authors for their help
* You can receive notifications of replies or new topics on request
* We do not sell your data - we promise

JOIN OUR GREAT ROBOTICS COMMUNITY.
Don’t have an account yet? Register yourself now and be a part of our community!
Register Yourself Lost Password
Robotforum - Support and discussion community for industrial robots and cobots in the WSC-Connect App on Google Play
Robotforum - Support and discussion community for industrial robots and cobots in the WSC-Connect App on the App Store
Download